HP Serviceguard Toolkits for Database Replication Solutions User Guide (August 2011)

Figure 6 Continentalclusters environment
In Oracle single-instance environment, Figure 6 (page 13), 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 is down,
the administrator must run the cmrecovercl command on the recovery cluster to bring up the
recovery package. This command halts the Data Receiver package, which in turn halts the standby
database. It then runs the recovery package, which brings up the database as a primary database
by performing a role failover. In this case, ODG toolkit handles role management. The start up
time of a recovery package is usually double than the start up time for an ordinary database
package. This is because the recovery package runs role transition commands which involves
shutting down the database after the role is changed and restarting the database. Hence,
start_script_timeout parameter in the package configuration should be specified
appropriately.
Restoring the cluster in a Continentalclusters to its original state is a manual process. The following
steps must be performed to restore the clusters to their original state:
1. Halt the recovery package — stops the database and the recovery package
2. Resync primary database from the standby database.
3. Start the primary package— brings up the database on primary cluster as a primary database
4. Start the Data Receiver package— brings up the database on the recovery cluster as a standby
database
RAC Environment
Supported configuration 13