HP Serviceguard Oracle DataGuard Toolkit User Guide, April 2011

Initially, this package will be in a halted state. When the primary cluster fails, cmrecovercl
command has to be run on the recovery cluster to bring up the recovery package.
NOTE: Note that the package attribute "START_STANDBY_AS_PRIMARY" has to be set to "yes"
in case of a recovery package.
In a Continentalclusters environment, the AUTO_RUN attribute of these packages must be disabled
at the time of bringing up the packages in the Recovery group. This is because Continentalclusters
does not want the packages to be brought up when the cluster is brought up. But if this attribute
is not enabled, the local failover of the package within the cluster at the time of package failure
will not happen. In such a case, package switching can be manually enabled using the cmmodpkg
command after the packages in the Recovery group are started. Please note that this is not a
restriction from ODG toolkit.
Initially, the Primary package and the Data Receiver package will be up and running and the
Recovery package will be in a halted state. The Primary package will bring up the Oracle database
on the Primary Cluster in Primary mode and the Data Receiver package will bring up the Oracle
database on the Recovery Cluster in Standby mode. Thus, a typical Data Guard environment is
set up with data replication done from the primary database on the Primary Cluster to the standby
database on the Recovery Cluster.
Multiple standby databases for the same primary database cannot be supported in a single
Continentalclusters setup. This is because there can be only one Data Receiver package and only
one Recovery package in a given Recovery group. However, the ODG toolkit in Continentalclusters
will not prevent users from configuring other standby databases that are placed outside the
Continentalclusters setup.
NOTE: The Bi-directional and 3-1 configurations are possible in Continentalclusters environment
Single instance environment
Figure 6 Continentalclusters environment
In Oracle single-instance environment, all the three packages (Primary, Data receiver, and Recovery
packages) are configured as failover packages. When the primary database fails, the Serviceguard
configured on the Primary Cluster fails over the database to another node within the Primary Cluster,
thus providing high availability to the primary database. Similarly, if the standby database fails,
then the Serviceguard configured on the Recovery Cluster allows the database to failover to another
node within the Recovery Cluster. When the Primary Cluster goes down, the administrator must
run the cmrecovercl command on the Recovery Cluster to bring up the Recovery package. This
command will first halt the Data Receiver package, which will halt the standby database. It will
12 Serviceguard support for Oracle Data Guard