My Oracle Support Banner

CDR Behave Differently for Exception between Classic and Integrated Replicat (Doc ID 1903602.1)

Last updated on FEBRUARY 26, 2019

Applies to:

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

Symptoms

When using RESOLVECONFLICT in the replicat MAP statement and when a conflict occurs such as DELETEROWMISSING, the classic replicat writes to an exception table when one is specified. In Integrated replicat the exception does not occur.

Example of MAP with resolve conflicts followed by MAP with exceptionsonly:

map <OWNER>.<TABLE>, target <OWNER>.<TABLE>, RESOLVECONFLICT (DELETEROWMISSING, (DEFAULT, DISCARD));
map <OWNER>.<TABLE>, target <OWNER>.<TABLE>, EXCEPTIONSONLY,INSERTALLRECORDS;



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.