|
|

楼主 |
发表于 2013/1/16 15:07:20
|
显示全部楼层
Hi Mish,
http://www.dba-oracle.com/sf_ora_00001_uni...nt_violated.htm
MetaLink offers information regarding trace files and ORA-00001applying to version 11.5.9 on all platforms. Here, it is commonly found that ORA-0001will be thrown when an item is being imported. Though ORA-00001 does not appear in the log file, neither is ORA-0001 appearing in MTL_INTERFACES_ERRORS, when the import complete the table is shown as failing upon enable INCOIN. ORA-0001 is shown in MTL_INTERFACES_ERRORS as err=1 ie unique constraint violated.
This signifies ORA-00001 because of an orphan record in the MTL_REVISIONS_INTERFACE table, perhaps because of an import program that has been run in the past. ORA-0001 is an issue here because upon inserting a new record in MTL_SYSTEM_ITEMS_INTERFACE the import inserts the record in MTL_REVISIONS_INTERFACE before to attempts passing the record to MTL_ITEM_REVISIONS_B via the MTL_REVISIONS_INTERFACE. Because SELECT via MTL_REVISIONS_INTERFACE fetch one or more records, due to orphan records, the INSERT fails, and ORA-0001 is thrown.
MetaLink advises that upon truncating MTL_REVISIONS_INTERFACE will take care of ORA-00001by using the instructions below:
Create table backup_<tarno> as select * from MTL_REVISIONS_INTERFACE
Truncate table MTL_REVISIONS_INTERFACE
Resubmit item for item import |
|