Figure 4 Data Guard replication between RAC primary package and single-instance standby package
Figure 4 (page 11), shows a Data Guard configuration where the primary database is configured as an RAC and the standby database is a single-instance database. Both primary and standby databases are configured in separate Serviceguard clusters for high availability. The RAC primary is combined with the ODG toolkit and the SGeRAC toolkit in a single package. It is configured on Node 1 and Node 2 in the SG Cluster 1. The standby database is configured as a single-instance Serviceguard failover package on Node 1 and Node 2 in the SG Cluster 2. The standby database is combined with the ODG toolkit and the ECMT Oracle toolkit in a single package. Data Guard replication takes place from RAC primary to the single-instance standby database. These two clusters are independent, and packages cannot failover across clusters.
3.Data Guard replication between RAC primary and RAC standby.
Figure 5 Data Guard replication between RAC primary and RAC standby
Figure 5 (page 11), shows a Data Guard configuration where both primary and standby databases are configured in two different RAC setups. The RAC primary is configured on nodes 1 and 2 of SG Cluster 1 and the RAC standby is configured on nodes 1 and 2 of SG Cluster 2. These two clusters are not a part of a Continentalclusters. Data Guard replication takes place between the RAC primary and the RAC standby.
NOTE: Configure these two clusters using the ODG toolkit in a Continentalclusters environment to achieve automatic role management. For more information on how to configure clusters in a Continentalclusters environment, see “Continentalclusters environment” (page 12).
Supported configuration | 11 |
