My Oracle Support Banner

Conflict resolution failed with SQL error 2,291 on original conflict with SQL error 1,403 (Doc ID 2777059.1)

Last updated on MAY 26, 2021

Applies to:

Oracle GoldenGate - Version 11.1.1.0.0 and later
Information in this document applies to any platform.

Symptoms

Customer has below setting in .prm file for their mapping.
.

<replicat name>.prm --> indicates mapping for the table in the target
-------------

MAP <SCHEMA>.<SRC_TABLE>. TARGET <SCHEMA>.<DEST_TABLE>  &
COMPARECOLS (ON UPDATE ALL, ON DELETE ALLEXCLUDING (COL3)), &
RESOLVECONFLICT (INSERTROWEXISTS, (DEFAULT, USEMAX (COL3)) ), &
RESOLVECONFLICT (DELETEROWMISSING, (DEFAULT, DISCARD)), &
RESOLVECONFLICT (DELETEROWEXISTS, (DEFAULT, OVERWRITE)), &
RESOLVECONFLICT (UPDATEROWMISSING, (DEFAULT, OVERWRITE)), &
RESOLVECONFLICT (UPDATEROWEXISTS, (DEFAULT, USEMAX (COL3)));

.

However, after updating a  row in source table.

update <SCHEMA>.<SRC_TABLE> set col1=<val> where <prim_col_name>=<value>;  --> one particular row
commit;

.

This row or change did not get replicated in the target table. This particular row is missing in target table, <SCHEMA>.<DEST_TABLE>

 

But, since RESOLVECONFLICT (UPDATEROWMISSING, (DEFAULT, OVERWRITE)) is configured, we expect the row to be replicated to target table

Changes

 No 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


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