ORA-00001 on Insert into REV_TABLES_B During OFSAA Model Upload (Doc ID 1303377.1)

Last updated on AUGUST 01, 2016

Applies to:

Oracle Financial Services Analytical Applications Infrastructure - Version 7.2 and later
Information in this document applies to any platform.
Oracle Financial Services Analytical Applications (OFSAA)

Symptoms

In Oracle Financial Services Analytical Applications (OFSAA), when you run the Model Upload process to import your Data Model, the process fails with an error.  The model upload log located in /<FTP directory>/<Infodom>/logs contains the following error:

----------------------------------------------
OBJECT REGISTRATION STARTED AS PART OF MODEL UPLOAD AT Mon Jan 31 21:30:20 CET 2011
----------------------------------------------
objectRegReqFlag..trueError while executing the query : [INSERT INTO REV_TABLES_B (TABLE_NAME,OWNER,DISPLAY_FLG) VALUES ('<table name>','<owner>','1')] Failed Executing Batch: error occurred during batching: ORA-00001: unique constraint (<atomic>.PK_REV_TABLES_B) violated

Object Registration Failed.
----------------------------------------------
OBJECT REGISTRATION COMPLETED AT Mon Jan 31 21:32:47 CET 2011
----------------------------------------------

Note: In the error above, <table name> is a table in the Data Model like DIM_ACCOUNT or SETUP_MASTER.

As a result of the error, the new tables you are uploading into the OFSAA database do not get added or registered.

Note: In version 8.0 and higher, the table triggering the error is not listed in the model upload log.  You must do the following to get the table name:

Go to $FIC_HOME/conf and edit the DynamicServices.xml

Find the following section:

<SERVICE CODE="10" CLASS="com.iflex.fic.ficserver.services.sms.SMSServiceProvider" NAME="SMS" SERVERID="DEFAULT" PATH=" " LOGGERNAME="SMSLOGGER" LOGGERLEVEL="xx">

Set the LOGGERLEVEL value to "0":

<SERVICE CODE="10" CLASS="com.iflex.fic.ficserver.services.sms.SMSServiceProvider" NAME="SMS" SERVERID="DEFAULT" PATH=" " LOGGERNAME="SMSLOGGER" LOGGERLEVEL="0">

Then, re-run the model upload and search the SMSService.log in $FIC_APP_HOME/common/FICServer/logs for the ORA-00001 error.  The insert statement triggering the error should be listed in the SMSService.log.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms