After Full Migration WS_SRC_ID Is Mapped To Different Value For Same LOV In Target Environment
(Doc ID 2616190.1)
Last updated on DECEMBER 02, 2019
Applies to:Siebel CRM - Version 19.7 and later
Information in this document applies to any platform.
When attempting to run a Full Migration of MAIN from DEV to UAT, 17K+ rows don't belong to the Workspace that got migrated.
The environment has the "Seed Migration Priority" set as Target (default).
It seems there is an unexpected behavior around the merge of the prior repository with the migrated repository as part of the conflict resolution.
Laten on, when an incremental migration is executed with modified LOV data for those unmatching WS_SRC_ID it creates duplicate rows.
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