My Oracle Support Banner

DataPump Import (IMPDP) Returns Error ORA-31684 Object Type INDEX Already Exists for Primary Key Constraints (Doc ID 1433123.1)

Last updated on JANUARY 16, 2020

Applies to:

Oracle Database - Enterprise Edition - Version 11.1.0.6 to 11.2.0.3 [Release 11.1 to 11.2]
Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Information in this document applies to any platform.
***Checked for relevance on 12-Aug-2013***

Symptoms

You started a DataPump import (IMPDP) and received errors like:

...
Processing object type TABLE_EXPORT/TABLE/TABLE_DATA
. . imported "TEST"."A_TAB":"P001" 0 KB 0 rows
. . imported "TEST"."A_TAB":"P002" 0 KB 0 rows
Processing object type TABLE_EXPORT/TABLE/INDEX/INDEX
ORA-31684: Object type INDEX:"TEST"."A_TAB_PK" already exists
...


You checked the DDL statements in SQLFILE extracted from dump file and observed, the primary key constraint is already present inline in column list (what implicitly creates the unique index with same name). Additionally a unique index is created:


During the execution (import), the additional CREATE UNIQUE INDEX statement generates the error ORA-31684.

Changes

 

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

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.