CMT : Unique Constraint Error During Migration of Accounts into Multiple Schemas with CMT
(Doc ID 2110908.1)
Last updated on JUNE 29, 2022
Applies to:Oracle Communications Billing and Revenue Management - Version 188.8.131.52.0 and later
Information in this document applies to any platform.
2. When populated the uniqueness_t table in Database1(db1) with data of secondary databases ( db2 db3), the poid_id0 is always populated with value of sequence of db1.poid_ids2 or can it be sometimes populated with value of sequence of secondary db ?
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