Model Upload Fails with 'ORA-02264: Name Already Used by an Existing Constraint'
(Doc ID 1680354.1)
Last updated on FEBRUARY 03, 2019
Applies to:Oracle Financial Services Analytical Applications Infrastructure - Version 7.3 and later
Information in this document applies to any platform.
Oracle Financial Services Analytical Applications (OFSAA)
In Oracle Financial Services Analytical Applications (OFSAA) infrastructure, your model upload process fails. An ORA-02264 error similar to the following error exists in the model upload log in /<ftpshare>/<infodom>/logs:
Creating the table stg_potential_rainbow_accounts.sql
stg_potential_rainbow_accounts.sql---------Error while executing Update :Failed Executing Query. Reason: ORA-02264: name already used by an existing constraint
Inside the Rollback Segment
Number of Exec Statements = 48
When you check the script stg_potential_rainbow_accounts.sql in /<ftpshare>/<infodom>/erwin/scripts/table, the following SQL is listed for the constraint:
CONSTRAINT PK__potential_rainbow_accounts PRIMARY KEY (v_data_origin,v_branch_code,v_rbs_account_number,v_rbs_sub_account_number,d_acctg_period_end_date)
This is the same name as the constraint created for a similarly named table called DIM_POTENTIAL_RAINBOW_ACCOUNTS:
CONSTRAINT PK__potential_rainbow_accounts PRIMARY KEY (N_ACCT_SKEY)
The Model Upload process is creating the same constraint name for both tables.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document