Goldengate MYSQL Replication : NOFILTERDUPTRANSACTIONS Doesn't Work As Expected
(Doc ID 2784892.1)
Last updated on AUGUST 18, 2022
Applies to:Oracle GoldenGate - Version 220.127.116.11.4 and later
Information in this document applies to any platform.
Replicat started with NOFILTERDUPTRANSACTIONS in MYSQL to MYSQL replication but after extract restarted (Restart Abend), Replicat started filtering transactions even when it's started with option NOFILTERDUPTRANSACTIONS.
Below are two scenarios
1. Replicat started with NOFILTERDUPTRANSACTIONS, it applied transactions as it is. After it found the logno change in trail files, it started filtering duplicate transactions
2. Replicat started with NOFILTERDUPTRANSACTIONS, it applied as expected. After the extract abended at source then replicat started filtering duplicate transactions.
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