Configuring HP Serviceguard Toolkit for Oracle Data Guard

brought up properly. Delete the file “dataguard.debug” from the package directory. This will enable

the toolkit to continue monitoring the database server application.

NOTE: If the maintenance flag is set to “no,” then the above feature will not be available and the

toolkit cannot be brought into maintenance mode.

MONITOR_INTERVAL: The time interval, in seconds, this script will wait between checks to make

sure that the Oracle instance is running. The default value is 30 seconds.

TIME_OUT: The time for which the toolkit waits for a completion of a normal shutdown before

initiating forceful halt of the application. The TIME_OUT variable is used to protect against a

worst-case scenario where a hung database or ASM instance prevents the halt script from completing,

therefore preventing the standby node from starting the instance. The TIME_OUT variable has no

effect on package failover times. The default value is 30 seconds.

ACTIVE_STANDBY: This parameter determines whether the database instance is an active standby

or not. The Active Data Guard Option available with Oracle Database 11g Enterprise Edition enables

you to open a physical standby database for read-only access. This parameter can be set to “yes” or

“no.” The default value is “no.”

DG_BROKER: Specifies whether the ODG broker is to be used or not. ODG Broker management is

not supported in this release hence this parameter must be set to “no.” This can take values “yes” or

“no.” The default value is “no.”

START_STANDBY_AS_PRIMARY: Specifies whether the standby database has to be started as the

primary database by failing over the primary database. This parameter can be used in a

Continentalcluster environment; the value of this parameter has to be “yes” in the package

configuration file of the recovery package.

ALERT_MAIL_ID: This parameter is used to specify the email address for sending alerts.

Main Script (hadg.sh)

This script contains a list of internally used variables and functions that support the starting and

stopping of an ODG instance. This script will be called by tkit_module.sh to perform the following:

- On package startup, it starts the Data Guard instance (primary/standby) and launches monitor

processes.

- On package halt, it stops the Data Guard instance and monitor process.

NOTE: The following three scripts are used only during the modular method of packaging.

- Attribute Definition File (Data Guard)

The ADF is used to generate a package ASCII template file.

- Module Script (tkit_module.sh)

This script is called by the Master Control Script and acts as an interface between the Master Control

Script and the Toolkit interface script (hadg.sh). It is also responsible for calling the Toolkit

Configuration File Generator Script (described below).

- Toolkit Configuration File Generator Script (tkit_gen.sh)

This script is called by the Module Script when the package configuration is applied using

“cmapplyconf” to generate the user configuration file (hadg.conf) in the package directory

(TKIT_DIR).