Configuring HP Serviceguard Toolkit for Oracle Data Guard

Installation and configuration of the toolkit

Setting up the application

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

Oracle must be installed on all the nodes of the cluster, by the user “oracle” and shared storage has

to be configured. For information on configuring ODG, please refer to Appendix A.

NOTE: In the event of package failover to the adoptive node, make sure that the database instance

on the adoptive node will be able to communicate in the Data Guard configuration. This requires

appropriate configuration of the listener and network services.

Setting up the toolkit

This toolkit has to be used in combination with the ECMT Oracle module for a single-instance Oracle

database. In this case, ensure that the ECMT B.06.00 has been installed.

After installing the ODG Toolkit, two scripts (hadg.sh and hadg.conf) and a README file will be

installed in the /opt/cmcluster/toolkit/dataguard directory. Two more scripts (tkit_module.sh and

tkit_gen.sh) and one file (dataguard.1), which are used for modular packaging, will be installed in

the /etc/cmcluster/scripts/tkit/dataguard directory and /etc/cmcluster/modules/tkit/dataguard

respectively.

These scripts are:

- hadg.conf (user configuration file)

This script contains a list of predefined variables that the user must customize for use with a particular

database instance. This is a configuration file that is read by the toolkit script, hadg.sh. The following

variables are contained in hadg.conf:

TKIT_DIR: This directory is synonymous with the package directory and holds the toolkit

configuration file. This parameter directs “cmapplyconf” to generate the hadg.conf file under this

directory. To put the toolkit into maintenance mode, create the dataguard.debug file under this

directory.

ORACLE_HOME: The base directory of Oracle where it is installed.

ORACLE_ADMIN: User name of the Oracle database administrator. This will be used for starting

and stopping the database.

For example:

ORACLE_ADMIN=oracle

SID_NAME: The Oracle session name. This uniquely identifies an Oracle database instance.

START_MODE: This parameter determines the startup mode for Oracle database. The default value

is “open.” It can take the options “nomount,” “mount,” or “open.”

NOTE: For the ODG Toolkit, always specify the value of this parameter as “mount.”

MAINTENANCE_FLAG: The maintenance flag is used to bring this toolkit into maintenance mode. If

set to “yes,” this will enable the maintenance feature in the toolkit. The Serviceguard Toolkit for ODG

will look out for a file “dataguard.debug” in the package directory. If the file exists and if the

maintenance feature is enabled, monitoring is paused, and database instance may be brought down

for maintenance. The package will not be failed over to the adoptive node even though the instance

has been brought down for maintenance. After the maintenance work, make sure that the instance is

Listener and network services can be configured by using Oracle’s netmgr utility.