Peer-to-Peer Changes Are Missing From Cascading Replication
Issue
Changes applied to location B by Integrate in a peer-to-peer channel aren't replicated to location D through a cascading channel.
Environment
- HVR 6
- A peer-to-peer channel with bidirectional replication between locations A, B, and C: A ↔ B, B ↔ C, and A ↔ C.
- The same HVR username and default session name,
hvr_integrate, at all three locations. - A second channel that replicates from B to D.
Resolution
To capture peer-to-peer changes in the cascading channel:
- Configure the second channel to use a separate HVR source location that connects to database B. Don't reuse location B from the peer-to-peer channel.
- In the second channel, add an Environment action to the source location with the parameter HVR_SCAN_NO_SESSION_IGNORE=1. This allows Capture to process changes applied by Integrate in the peer-to-peer channel.
Do not set HVR_SCAN_NO_SESSION_IGNORE=1 in the peer to peer channel otherwise it will cause looping.
Cause
By default, Capture skips DML operations performed by hvr_integrate to prevent replication loops. As a result, when Integrate applies changes to B, the cascading channel doesn't capture them for replication to D.