ORA-1 Unique Constraint SYS.I_DEPENDOBJ Violated Error Messages In DataPump Client Trace

(Doc ID 1362224.1)

Last updated on OCTOBER 23, 2013

Applies to:

Oracle Database - Enterprise Edition - Version and later
Information in this document applies to any platform.
***Checked for relevance on 23-Oct-2013***


Whenever a DataPump export job is executed, a client trace file is generated containing:

----- Error Stack Dump -----
ORA-00001: unique constraint (SYS.I_DEPENDOBJ) violated

----- Current SQL Statement for this session (sql_id=gqyv857q7s97q) -----
insert into sys.expdepobj$(d_obj#, p_obj#) values(:1, :2)

----- PL/SQL Stack -----
----- PL/SQL Call Stack -----
object line object
handle number name
ae7bf5f28 382 package body SYS.DBMS_AQADM_SYSCALLS
ae7bf5f28 520 package body SYS.DBMS_AQADM_SYSCALLS
aefb82848 1018 package body SYS.DBMS_PRVTAQIS
afbd3cec0 6174 package body SYS.DBMS_AQADM_SYS
ae2b71de8 230 package body SYS.KUPC$QUE_INT
ae2b71de8 1306 package body SYS.KUPC$QUE_INT
ae2b51670 1 anonymous block
af3ad9418 65 package body SYS.KUPC$QUEUE_INT
aebd7f708 395 package body SYS.KUPV$FT_INT
aebb5b190 1486 package body SYS.KUPV$FT
aebb5b190 962 package body SYS.KUPV$FT
af3d8ffe0 5176 package body SYS.DBMS_DATAPUMP
af3ae9ea8 1 anonymous block

There are no errors in the DataPump log or in alert log files.


The errorstack event 1 was set at instance level in order to investigate ORA-00001: unique constraint violated errors.


Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms