This content has been marked as final. Show 4 replies
Why do you want or need supplemental logging on the target?
Just in case if we switch the connection and use target database as primary, now if we issue the update from the target side it does not capture the changes from target side as supplemental logging is not enabled.
So we need to enable supplemental logging on target manually.
So please suggest the approach in case of setup where the source (primary) and target (secondary) side switches and source become secondary and vice-versa.
Do all of the setup for bidirectional replication, but do not start the processes from B to A. Keep everything in startup/learn files so you can run various commands, GGSCI and otherwise, via one script.
_Just a Note from GoldenGate Reference Guide:_
Look a note to DDLOPTIONS -> ADD TRANDATA item
+"By default, the ALTER TABLE that adds the supplemental logging is not replicated to the target unless the GETREPLICATES option is in use."+
Hope, this helps
Edited by: iago on Nov 14, 2012 4:54 AM