Exception in Bi-Directional Replication is not working
(Doc ID 2273506.1)
Last updated on JUNE 05, 2019
Applies to:Oracle GoldenGate - Version 220.127.116.11.28 and later
Information in this document applies to any platform.
NOTE: In the images and/or the document content below, the user information and data used represents fictitious data from the Oracle sample schema(s) or Public Documentation delivered with an Oracle database product. Any similarity to actual persons, living or dead, is purely coincidental and not intended in any manner
Bi-Directional replication without CDR. So, only exception table will be used on both the sides to handle the collisions.
RDBMS - 18.104.22.168
OGG - 22.214.171.124.0
The below is the test scenario explained.
1. Do an insert first on the table on both source and target (same record).
2. Do an Insert on any one side, say target. You will see that the table exception on source side gets loaded with 1 record (previous record) and this
second insert will be lost which should ideally have got replicated successfully to the source (because you did it only on target).
3. Now do an insert on source. lets call it the 3rd insert (this insert should have values different than the first 2 inserts). You will now see that
the exception on target gets loaded for the first record. This third insert will also be lost which should ideally have got replicated successfully to
the target (because you did it only on source).
4. Now do some more inserts on target but you will never see the exception table loaded for that second insert which simply got eaten up.
5. Similarly, now do some more inserts on source but you will never see the exception table loaded for that third insert which simply got eaten up.
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