My Oracle Support Banner

Data Model Upload Utility Connecting To Source Schema After Cloning (Doc ID 2489830.1)

Last updated on DECEMBER 03, 2019

Applies to:

Oracle Financial Services Asset Liability Management - Version 8.0.4 and later
Information in this document applies to any platform.
Oracle Financial Services Analytical Applications (OFSAA)

Symptoms

On : 8.0.4 version

When attempting to perform Model Upload on the Regression Environment, found the model upload seems to connect to the source schema (UAT) not the new environment schema.

Expected Behavior:
Model upload to use

Regression (Cloned) Atomic Schema: OFSAAATREG
Regression (Cloned) Config Schema: OFSAACFREG

instead of

Source Atomic Schema: OFSAAATM
Source Config Schema: OFSAACONF


ERROR
-----------------------
OFSIFRSINFO_LOG_32_12.18.2018-04.49.49.log
FTPing the index script file
MODEL ALTERED SUCCESSFULLY
Modelupload status..0upDateCacheForOlap cargo..[SC:20][ST:0][SST:8][Oper:0][Version:0][EF:false][D:OFSIFRSINFO][S:null][U:null][PT:0][P:null0]
MODEL UPLOAD COMPLETED AT Tue Dec 18 17:32:23 GST 2018
----------------------------------------------
----------------------------------------------
OBJECT REGISTRATION STARTED AS PART OF MODEL UPLOAD AT Tue Dec 18 17:32:23 GST 2018
----------------------------------------------
Error while executing the query Failed Executing Batch: error occurred during batching: ORA-02431: cannot disable constraint (PK_REV_COLUMN_PROPERTIES) - no such constraint
Error- Error while executing the query Failed Executing Batch: error occurred during batching: ORA-02431: cannot disable constraint (PK_REV_COLUMN_PROPERTIES) - no such constraint
Object Registration Failed.
----------------------------------------------
OBJECT REGISTRATION COMPLETED AT Tue Dec 18 17:37:59 GST 2018



Step to Replicate:
1. Performed cloning from UAT to Regression environment using OFSAA Environment Cloning document.
2. Regression Env is up and running.
3. Performed model upload and it failed.
4. It seems like the uploade utility is connecting with source schema(UAT) not the new environment atomic schema.

Changes

 

Cause

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
Symptoms
Changes
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.