My Oracle Support Banner

ORMBA GG I1CM2 Replicat Abended With Error - Unique Constraint Violated RMB1REP.CI_PER_NAME (Doc ID 2651897.1)

Last updated on MARCH 27, 2020

Applies to:

Oracle Financial Services Revenue Management and Billing Analytics - Version 2.8.0.0.0 and later
Information in this document applies to any platform.

Symptoms

On : 2.8.0.0.0 version, ORMBA - Extractors and Schemas

Below GoldenGate error can be seen while trying the below steps:

Scenario: For an existing Customer in ORMB, from Person UI, do the following:
a) Deleted existing Person Name row
b) Added new Person Name row
c) Saved the changes.

In single commit, Delete and Insert records are passed to GoldenGate. Unique constraint in RMB1REP.CI_PER_NAME (columns – PER_ID, SEQ_NUM, JRN_EFF_START_DTTM) got violated.


ORMBA GG I1CM2 Replicat Abended with error - unique constraint violated RMB1REP.CI_PER_NAME

GG Replicat Process of I1CM2 got Abended with below error:

GGS Error :
-------------
2020-02-12T19:28:13.152-0800 WARNING OGG-01004 Oracle GoldenGate Delivery for Oracle, I1CM2.prm: Aborted grouped transaction on xxxxxx.RMB1REP.CI_PER_NAME, Database error 1 (OCI Error ORA-00001: unique constraint (RMB1REP.X$XM171S1) violated (status = 1), SQL ).
2020-02-12T19:28:13.152-0800 WARNING OGG-01003 Oracle GoldenGate Delivery for Oracle, I1CM2.prm: Repositioning to rba 6207433 in seqno 0.
2020-02-12T19:28:13.152-0800 ERROR OGG-01296 Oracle GoldenGate Delivery for Oracle, I1CM2.prm: Error mapping from xxxxx1.CISADM.CI_PER_NAME to xxxxxx.RMB1REP.CI_PER_NAME.
2020-02-12T19:28:13.160-0800 ERROR OGG-01668 Oracle GoldenGate Delivery for Oracle, I1CM2.prm: PROCESS ABENDING.
 


Changes

 

Cause

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
Symptoms
Changes
Cause
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.