Professional Documents
Culture Documents
- Use multiple GoldenGate instance groups spread across different nodes of the RAC cluster.
This provides redundancy if a node fails.
- Configure GoldenGate processes like Extract, Data Pump, Replicat to run on different nodes.
Use the GROUP parameter to assign processes to instance groups.
- Use GoldenGate's integrate capture mode to capture changes directly from the RAC database
redo logs. This is more efficient than classic capture mode.
- Configure multiple TRAIL files on shared storage across nodes to avoid a single point of
failure.
- Enable FAILOVER on Extract and Data Pump processes to automatically restart on another
node in case of outages.
- Use virtual IP addresses for Manager and instance groups that can fail over between nodes.
- Setup GoldenGate heartbeat on all nodes to enable coordinated failover between processes.
- Use NFS or ASM for storage replication of TRAIL files across nodes for high availability.
- Test failover scenarios by shutting down database and GoldenGate processes on individual
nodes.
The key is to distribute GoldenGate across multiple nodes and leverage RAC shared storage for
trails. This provides continuous replication availability even if a node or process goes down.
On Node1:
- Extract and Data Pump group using virtual IP 10.1.1.101
- Extract EXT1
- Data Pump DPUMP1
- Manager process MGR1
On Node2:
- Extract and Replicat group using virtual IP 10.1.1.102
- Extract EXT2
- Replicat REP1
- Manager process MGR2
Extract setup:
- EXT1 and EXT2 read from TRAIL files on shared storage
- Integrated capture mode from RAC database
- Parameter FILE trail1.prm:
GROUP EXT1
TRAIL ./dirdat/tb*
Replicat setup:
- REP1 applies changes to target database
- Parameter FILE rep1.prm:
GROUP REP1
ASSUMETARGETDEFS
DISCARDFILE ./dirrpt/discard.txt
This config allows continuous replication using GoldenGate even if a single node fails. The
virtual IPs can move between nodes and processes can failover as needed.