UNIQUE CONSTRAINT For PS_EOEN_REGISTRY
Last updated on OCTOBER 16, 2017
Applies to:PeopleSoft Enterprise HCM Human Resources - Version 9.2 and later
Information in this document applies to any platform.
Error at the step 'Importing Application System Data' with unique constraint error for PS_EOEN_REGISTRY (dlupsysi_n.log). In the Exporting Application System Data step, it exported out all the rows for EOEN_REGISTRY where SYSTEM_DATA_FLG='Y'. In the import script, it didn't have any import options. The import script did delete all the rows for EOEN_REGISTRY where SYSTEM_DATA_FLG='Y' before doing the import * command. The issue is that in the target FP database, there is one row data that have the same keys as the database to be imported in except that the SYSTEM_DATA_FLG is set to 'N'. Thus, causing the unique constraint error.
SQL Error. Error Position: 0 Return: 805 - ORA-00001: unique constraint (SHRADM.PS_EOEN_REGISTRY) violated
INSERT INTO PS_EOEN_REGISTRY (EOEN_EVENT_NAME, SEQNUM, PACKAGEROOT, APPCLASS_PATH, EOEN_APP_CLASS, DESCR, EOEN_HANDLR_MODE, EOEN_HANDLR_LOG, EOEN_SOURCE_IND, EOEN_EVENT_STAT, SYSTEM_DATA_FLG, EOEN_TRACE_FLG) VALUES (:1, :2, :3, :4, :5, :6, :7, :8, :9, :10, :11, :12)
SQL Error. Error Position: 0 Return: 0 -
Error: SQL unable to commit transaction for EOEN_REGISTRY
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms