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 7.5.0.0.0 and later
Information in this document applies to any platform.

Goal

1. The KM <Note 1516455.1> is referring to poid being mangled. is it related to CMT(Conversion Manager) ? if yes why POIDs being mangled?

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 ?

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

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

CMT : Unique Constraint Error During Migration of Accounts into Multiple Schemas with CMT (Doc ID 2110908.1)

Applies to:

Goal

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!