CMT Error: Unique Constraint I_UNIQUENESS__ID Violated
(Doc ID 1516455.1)
Last updated on MARCH 23, 2019
Applies to:Oracle Communications Billing and Revenue Management - Version 184.108.40.206.0 to 220.127.116.11.0 [Release 7.4.0 to 7.5.0]
Information in this document applies to any platform.
During account creation (rather, migration using CMT), the following error is obtained in the scenario explained later :
unique constraint I_UNIQUENESS__ID on uniqueness_t.poid_id0 is violated
Steps to Reproduce
1. create accounts in bulk in the environment (2 schema environment , example; <pinuser1> and <pinuser2>) with CMT (migration)
2. create accounts in bulk (at the same time) in the (same) environment (for example, using AIA)
3. At some point, some collision happens for the poid_id0 for the uniqueness_t and account creation fails with the error:
=ORA-00001: unique constraint (<pinuser2>.I_UNIQUENESS__ID) violated
account created without constraint violation on uniqueness_t.poid_id0
poid_id0 on uniqueness_t is duplicated
=ORA-00001: unique constraint (PIN02.I_UNIQUENESS__ID) violated "insert into pin02.uniqueness_t ( poid_DB, poid_ID0, poid_TYPE, poid_REV, account_obj_DB, account_obj_ID0, account_obj_TYPE, account_obj_REV, service_obj_DB, service_obj_ID0, service_obj_TYPE, service_obj_REV, status, login, account_no, type, effective_t, created_t, mod_t, read_access, write_access, object_cache_type ) values ( :poid_DB, :poid_ID0, :poid_TYPE, :poid_REV, :account_obj_DB, :account_obj_ID0, :account_obj_TYPE, :account_obj_REV, :service_obj_DB, :service_obj_ID0, :service_obj_TYPE, :service_obj_REV, :status, :login, :account_no, :type, :effective_t, :created_t, :mod_t, :read_access, :write_access, :object_cache_type )"
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