GoldenGate High Availability Master/Slave Feature Not Working Upon Relocate or Failover
(Doc ID 2849227.1)
Last updated on APRIL 17, 2023
Applies to:
Management Pack for Oracle GoldenGate - Version 12.2.1.2.0 and laterInformation in this document applies to any platform.
Symptoms
Goldengate instance is installed for High Availability. When GoldenGate instance/targets are discovered and promoted in OEM console
the first EM Agent is automatically set to MASTER node. The second and all other subsequent EM Agents (if applicable) are set to SLAVE node.
When GoldenGate instance/targets are relocated to another node the instance/targets show DOWN in OEM console.
What is supposed to happen (automatically) is that node2/SLAVE EM Agent starts monitoring the instance/targets in the new (node2) node.
Changes
Cause
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
Symptoms |
Changes |
Cause |
Solution |
References |