CDR Behave Differently for Exception between Classic and Integrated Replicat

(Doc ID 1903602.1)

Last updated on APRIL 01, 2016

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 ggsuser.tcustmer, target ggs.tcustmer, RESOLVECONFLICT (DELETEROWMISSING,
(DEFAULT, DISCARD));
map ggsuser.tcustmer, target ggs.tcustmex, EXCEPTIONSONLY,INSERTALLRECORDS;



Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms