Object Migration for SQL Rules Gives New System IDs Corrupting Migrated Batches
(Doc ID 2675912.1)
Last updated on MAY 17, 2023
Applies to:
Oracle Financial Services Analytical Applications Infrastructure - Version 8.0.5 and laterInformation in this document applies to any platform.
Oracle Financial Services Analytical Applications Infrastructure (OFSAAI)
Oracle Financial Services Analytical Applications (OFSAA)
Oracle Financial Services Profitability Management (PFT)
Oracle Financial Services Funds Transfer Pricing (FTP)
Oracle Financial Services Asset Liability Management (ALM)
Oracle Financial Services Enterprise Performance Management (EPM)
Symptoms
On OFSAAI 8.0.5.3, when using Online Object Migration for SQL Rules, the SYS_ID_NUM is changed from source to target after import.
EXPECTED BEHAVIOR
Migration of sql rules with same SYS_ID numbers in DEV to UAT and ultimately to production.
Have also tried using command line migration, however it fails with "Migration API is Not Available for ObjectType...10" errors.
The issue can be reproduced at will with the following steps:
1. Run User Interface (UI) object migration for SQL Rules from source to target
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 |
| References |