Base Migration Batches Do Not Convert Foreign Key Ids Into Production Values
(Doc ID 2883265.1)
Last updated on SEPTEMBER 23, 2022
Applies to:
Oracle Utilities Framework - Version 4.5.0.0.0 and laterOracle Utilities Customer Cloud Service - Version 22A and later
Oracle Utilities Customer to Meter Base - Version 2.9.0.0.0 and later
Information in this document applies to any platform.
Goal
On: 22A version, Environment Related
Base Migration Batches do not Convert Foreign Key Ids into Production Values
The base migration batches that migrate data from STGADM to CISADM do not convert the foreign key Ids into production values.
The following migration batches were tested. These batches have the issue reported above.
- W1ASTIDI (Insert W1_ASSET_IDENTIFIER)
- W1NODIDI (Insert W1_NODE_IDENTIFIER)
- D1DVCIDI (Insert D1_DVC_IDENTIFIER)
- D1SPIDTI (Insert D1_SP_IDENTIFIER)
The primary key of the tables above will be migrated with the updated primary keys from the CK/DK/WK tables that were generated by batch job F1-CVASG, but the foreign keys that contain Id references such as Asset Id, Device Id, SP Id, Node Id, etc. were not updated. Instead, they were migrated with the staging values.
With the identifier values not being updated, the entities will not be displayed correctly on the page since their references are required to resolve the issue.
Solution
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
| Goal |
| Solution |
| References |