Upgrade fails during DB Load with ORA-02270 no matching unique or primary key

Document ID : KB000087588
Last Modified Date : 14/04/2018
Show Technical Document Details
Issue:
Error Message :
U00003592 UCUDB - Status: '' Native error: '2270' Msg: 'ORA-02270: no matching unique or primary key for this column-list'

During an upgrade from a previous versions (such as V9) to a later release (V11, V12), the above error is displayed in the DB Load log file when using an Oracle Database.

Investigation

When loading the initialdata (uc_upd.txt) file via DB Load for an upgrade, the Load will fail.  Looking at the end of the log file, similar messages to the ones shown below will be displayed.

U00038089 Error: Problem during execution of SQL command: 
'
ALTER TABLE EV ADD CONSTRAINT FK_EV_EH FOREIGN KEY 
        ( EV_AH_Idnr ) REFERENCES EH ( EH_AH_Idnr )'
U00003590 UCUDB - DB error: 'OCIStmtExecute', 'ERROR   ', '', 'ORA-02270: no matching unique or primary key for this column-list'
U00003590 UCUDB - DB error: 'OCIStmtExecute', 'ERROR   ', '', 'ORA-02270: no matching unique or primary key for this column-list'
U00038077 Do you want to ignore this error?

Please note: Do not continue without contacting Automic Support!
U00038245 If you cancel the Database will probably be in an inconsistent state. Please contact Automic Support to evaluate the best approach. Do you really want to cancel?
U00038068 ABORTING due to error. 

The loading process was terminated abnormally. The Database might be in an inconsistent condition. Please contact Automic Support.

 
This ORA-02270 error is generated from Oracle, and is captured within our log file.  This error is not the result of either a defect or a faulty design in Automic's products.

ORA-02270 is caused by situations which are completely contained within the scope and perimeter of Oracle's products and outside of Automic's responsiblity.


The only course of action when faced with this error is to contact your Oracle Database Administrator or the Oracle Customer Support team and have them analyze the issue.  They should be able to find the correct column names using the ALL_CONS_COLUMNS catalog view.
 
Environment:
OS Version: N/A
Cause:
Cause type:
Configuration
Root Cause: A REFERENCES clause in a CREATE/ALTER TABLE statement gives a column-list for which there is no matching unique or primary key constraint in the referenced table.
Resolution:
This field was added on 30/03/2017. This article has not been updated yet. Refer to the "Description" or "Workaround" sections for solution information.

Fix Status: No Fix

Fix Version(s):
N/A
Additional Information:
Workaround :
N/A