HP Serviceguard Oracle DataGuard Toolkit User Guide, April 2011

cluster. We have taken two nodes in the above example, for better understanding. The standby
database is not a part of a Serviceguard cluster. It is present outside SG cluster 1. Data Guard
replication takes place between the primary RAC and the standalone standby. Each instance
of the primary database transmits its redo data to an instance of the standby database. The
role of the standby is to receive the redo logs from the RAC primary and apply them to the
database. In this case, high availability is not provided for the standby.
The RAC primary is configured as a combinational package of the ODG toolkit with the
SGeRAC toolkit. The RAC primary package fails only when all the primary database instances
fail.
2. Data Guard replication between RAC primary package and single-instance standby package.
Figure 4 Data Guard replication between RAC primary package and single-instance standby
package
Figure 4 (page 10), 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 once again, a combinational package of the ODG toolkit with the SGeRAC
toolkit. It is configured on nodes 1 and 2 in the SG cluster 1. The standby database is
configured as a single-instance Serviceguard failover package on nodes 1 and 2 of SG cluster
2. The standby database is a combinational package of ODG toolkit and the Oracle ECMT
toolkit. Data Guard replication takes place from RAC primary to the single-instance standby
database. Note that these two clusters are independent and packages cannot failover across
the clusters.
3. Data Guard replication between RAC primary and RAC standby.
10 Serviceguard support for Oracle Data Guard