Configuring HP Serviceguard Toolkit for Oracle Data Guard

2. In case of a Metrocluster environment where only the primary database is configured within the

Metrocluster and the standby database is configured on a third site that is not part of the

Metrocluster, the data replication can happen only from the site where the primary is running.

Even if the proximity of the other site is better, data replication cannot happen from that site. This

is a restriction put by Data Guard, and not the ODG Toolkit.

3. The Data Guard broker should not be configured for automatic role transitions. In case of

Continentalclusters scenarios, the role management is handled by the ODG Toolkit and in other

cases, if the role of any database is changed, then the ODG Toolkit package will fail.

4. There are use-cases in which only the primary database is configured in a SG cluster and the

standby is not part of any cluster. This is similar to configuring ECMT Toolkit, which can be run

directly by the user. Legacy-type support is required to support this feature. ODG Toolkit does not

support legacy-style configuration.

5. Multiple standby database instances cannot be supported in the Continentalclusters setup since

there can be only one Recovery package and only one Data Receiver package within the

Recovery group. Other standby instances can be configured outside the CC environment.

For more information

To learn more, see:

• HP Serviceguard Solutions:

http://www.hp.com/go/serviceguardsolutions

• Technical Documentation:

www.hp.com/go/hpux-serviceguard-docs

Appendix A

Configuring ODG example

ODG is included with the Enterprise Edition and Personal Edition of the Oracle database software.

The standby database can be created in two ways:

• Physical standby database

• Logical standby database

Configuring the physical standby database in a single-instance Oracle database is described in this

section. Details about creating a logical standby database can be found at the Oracle Web site

(

http://download.oracle.com/docs/cd/E11882_01/server.112/e10700/create_ls.htm).

If customer already has a database and wants to make use of Data Guard for replication to another

standby site, it is the customer’s responsibility to set up the standby in the same state as the primary.

Customers have to use third party or Oracle-supplied tools to back up and copy the existing database

to the standby site. Data Guard replicates only updates to the database.

The following steps describe how to configure the Data Guard. Note that these are generic steps to

configure the Data Guard. Detailed information about configuring Data Guard can be obtained from

the Oracle Web site (

http://www.oracle.com).

Preparing the primary database

Before creating the standby database, the primary database must be configured first. The following

steps should be followed to create the primary database:

1. Enable force logging:

Place the primary database in FORCE LOGGING mode after the database creation using the