Configuring HP Serviceguard Toolkit for Oracle Data Guard

The standby database is configured as a Data Receiver package in the Recovery Cluster. It will

receive the archived redo logs sent by the primary database instance irrespective of the node on

which the primary database is running. Cross subnet failover is allowed across the sites.

When the Primary Cluster fails, the user must run the “cmrecovercl” command to halt the Data

Receiver package and start the Recovery package. Once this command is run, the Recovery package

starts and brings up the Oracle database as a primary database. Thus there will be no instance of

standby database running once the role of the standby database is changed to primary. Multiple

standby configurations are not supported within a Continentalclusters setup. However, the ODG

Toolkit in Continentalclusters will not prevent customers from configuring standby databases that are

placed outside the Continentalclusters environment.

Supporting multiple instances of single-instance ODG configuration

Figure 6: Multiple Data Guard instances in one Serviceguard cluster

To support multiple Data Guard instances in one Serviceguard cluster, all the instances must be

configured in such a way that they function independently. This means that they should have different

volume groups for storing the database and redo logs. They should use different Oracle database

listeners and IP addresses or ports.

Figure 6 shows a supported configuration where two two-node Serviceguard clusters are configured

to provide HA to the Data Guard configurations. Two single-instance Data Guard primary databases

are configured in Cluster 1 and one standby database is configured for each of the primary

databases in Cluster 2. Note that both these clusters are independent of each other and there cannot

be package failover between the two clusters. Both the primary database in Cluster 1 and the standby

database in Cluster 2 and their corresponding redo logs are located on shared disks such that each

can be accessed from any nodes in their respective clusters. This will enable failover of the primary

and standby packages within the cluster, thus providing HA for both of them.

HA for Data Guard Broker

HA for Data Guard Broker is not supported on a single-instance database.

Node 1

Node 2

SG Cluster 1

SG Cluster 2

Package 1

Package 4

Standby

Primary

Primary DB

Standby DB