ORA-00001: unique constraint violated error during impdp TABLE_EXISTS_ACTION=truncate content =data_ [message #527264] |
Mon, 17 October 2011 05:10 |
prejib
Messages: 126 Registered: March 2009 Location: India
|
Senior Member |
|
|
Hi,
I am trying to import the dump using the impdp utility and followed the below steps .
I have disabled all the constraints and executed the below command
impdp DIRECTORY=EXPDP_DAILY_BACKUP_DIR DUMPFILE=expdp_QA_full_11102011_214501.dmp
logfile=imp_EXPDP_QA_full_12102011_203254.log remap_schema=prod:prod remap_tablespace=prod:prod
schemas=prod TABLE_EXISTS_ACTION=truncate content=data_only.
but I am getting the below error like this for 1 or 2 tables . and If I import those tables seperately its getting imported successfully. i am not getting the below error always .
ORA-31693: Table data object "PROD"."DAS_ID_GENERATOR" failed to load/unload and is being skipped due to error:
ORA-00001: unique constraint (PROD.DAS_ID_GENERATOR_P) violated
ORA-31693: Table data object "PROD"."TKT_DIST_SRV_STAT" failed to load/unload and is being skipped due to error:
ORA-00001: unique constraint (PROD.SERVER_STATS_P) violated
Please help
[Updated on: Mon, 17 October 2011 05:22] by Moderator Report message to a moderator
|
|
|
|
Re: ORA-00001: unique constraint violated error during impdp TABLE_EXISTS_ACTION=truncate content =d [message #527296 is a reply to message #527270] |
Mon, 17 October 2011 06:56 |
prejib
Messages: 126 Registered: March 2009 Location: India
|
Senior Member |
|
|
Actually the above tables are having only primary key and 'NOT NULL' columns . If I add EXCLUDE=CONSTRAINT in the impdp command , my understanding is that,the PK will be disabled and the rows will be imported into the table without any errors and while enabling the constraint it will give the error due to duplicate rows(If the truncate didn't happened on the tables even after TABLE_EXISTS_ACTION=truncate). please correct me if Im wrong.
|
|
|
|
|
|
|
|
|