My Oracle Support Banner

System IDs of SQL Rules Change After Migration and Corrupt Production Batch (Doc ID 2602281.1)

Last updated on NOVEMBER 08, 2019

Applies to:

Oracle Financial Services Asset Liability Management - Version 8.0.0 and later
Oracle Financial Services Analytical Applications Infrastructure - Version 8.0.0 and later
Oracle Financial Services Profitability Management - Version 8.0.0 and later
Oracle Financial Services Funds Transfer Pricing - Version 8.0.0 and later
Information in this document applies to any platform.
Oracle Financial Services Analytical Applications (OFSAA)

Symptoms

After updating existing SQL Rules in a Dev environment and migrating them to the production environment, the SQL Rule is given a new System ID in the target production environment.  As a result, the SQL Rule is disconnected from the production batch and the batch generates the wrong results.

For example, the Production Batch contained a SQL Rule with System ID = 202037.  A SQL Rule with System ID = 202037 also exists in Dev.  When this SQL Rule is migrated, it is assigned to a new System ID of 202457, invalidating the batch.

You expect the updated SQL Rule to retain the same System ID existing in the production environment when it is migrated.

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
Cause
Solution


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