IMPDP Fails With ORA-39083, ORA-02270 Where Source Table Has A Disabled Primary Key Constraint
(Doc ID 455311.1)
Last updated on OCTOBER 08, 2020
Applies to:
Oracle Database - Enterprise Edition - Version 10.1.0.2 to 11.1.0.6 [Release 10.1 to 11.1]Oracle Database Cloud Schema Service - Version N/A and later
Gen 1 Exadata Cloud at Customer (Oracle Exadata Database Cloud Machine) - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Cloud Exadata Service - Version N/A and later
Information in this document applies to any platform.
Symptoms
EXPDP does not export disabled primary key constraints. This causes IMPDP to fail with the following errors:
ORA-39083: Object type REF_CONSTRAINT failed to create with error:
ORA-02270: no matching unique or primary key for this column-list
Failing sql is:
ALTER TABLE "<SCHEMA_NAME>"."<TABLE_NAME2>" ADD CONSTRAINT "<FK_CONSTRAINST_NAME>" FOREIGN KEY ("<COL_NAME1>") REFERENCES "<SCHEMA_NAME>"."<TABLE_NAME2>" ("<COL_NAME2>") DISABLE
ORA-02270: no matching unique or primary key for this column-list
Failing sql is:
ALTER TABLE "<SCHEMA_NAME>"."<TABLE_NAME2>" ADD CONSTRAINT "<FK_CONSTRAINST_NAME>" FOREIGN KEY ("<COL_NAME1>") REFERENCES "<SCHEMA_NAME>"."<TABLE_NAME2>" ("<COL_NAME2>") DISABLE
Changes
Disabled the primary key constraint on the exported table prior to running EXPDP.
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Changes |
| Cause |
| Solution |
| References |