Scribd
Upload
59 views1 page

Error Hanlding

This document discusses common issues encountered during Oracle database table redefinition and their solutions. It covers errors such as invalid interim tables, tables that cannot be redefined due to data type restrictions, tables that do not match those specified for redefinition, and interim tables created with incorrect constraints. The solutions involve dropping constraints, manually adjusting interim table definitions, and retrying parts of the redefinition process.

Uploaded by

ramkumar
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as TXT, PDF, TXT or read online on Scribd
59 views1 page

Error Hanlding

This document discusses common issues encountered during Oracle database table redefinition and their solutions. It covers errors such as invalid interim tables, tables that cannot be redefined due to data type restrictions, tables that do not match those specified for redefinition, and interim tables created with incorrect constraints. The solutions involve dropping constraints, manually adjusting interim table definitions, and retrying parts of the redefinition process.

Uploaded by

ramkumar
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as TXT, PDF, TXT or read online on Scribd
You are on page 1/ 1

dbms_redefinition�common issues

1) ORA-12093: invalid interim table "OWNER"."TABLE"


Intermediate table named in the �redef_table� is not created yet

2) ORA-12089: cannot online redefine table "OWNER"."TABLE" with no primary key


A table with no PK was tried to be redefined without using the ROWID option

3) ORA-23539: table "OWNER"."NAME" currently being redefined


Table redefinition finished with errors and a new �redef_table� was run
If data was already copied and failure was during copy dependents steps, we don�t
need to drop the table and start again -we can keep the already copied data,
resolve errors, sync and repeat copy dependants.

4) ORA-00997: illegal use of LONG datatype


Columns LONG, LONG RAW and BFILE cannot be redefined.
https://docs.oracle.com/cd/B28359_01/server.111/b28310/tables007.htm#ADMIN11674

5) ORA-23541: tables do not match tables used while defining the redefinition
When COPY_TABLE_DEPENDENTS is used for a single partition, it tries to copy
partitioned table objects when target is not partitioned and only an exchange
partition will be executed
Solution:
copying dependents should not be used when moving single partitions

7) ORA-14024: number of partitions of LOCAL index must equal that of the underlying
table
Interim table was created using dbms_metadata, but it got table and index creation
with less partitions than the existing one (not updated with new partitions added)
Solution:
Manually adjust interim table creation SQL adding missing partitions from existing
index

8) ORA-01442: column to be modified to NOT NULL is already NOT NULL


Intermediate tablewas created with not null columns
Solution:
Remove not null constraint from interim table and retry
descwill show table not having not null constraints, but the check constraint is
there and enabled
1) drop check constraints on interim tables
2) resync, retry copy dependent and finish redefinition
3) enable validate check constraints
Caused by a known bug:4396234 ET10.2OREDEF: NULLABLE COL OF *_TAB_COLUMNS TABLE NOT
UPDATED AFTER ONLINE REDEF

You might also like