HP Enterprise Cluster Master Toolkit User Guide (5900-2131, December 2011)

If a listener service is configured in the package configuration file, set the following parameters:

SERVICE_NAME[1]="ORACLE_LSNR_SRV"

SERVICE_CMD[1]="/etc/cmcluster/db1_package/toolkit.sh monitor_listener"

SERVICE_RESTART[1]="-r 2"

Configure the Package IP and the SUBNET.

Add in the customer_defined_run_cmds function:

/etc/cmcluster/db1_package/toolkit.sh start

Add in the customer_defined_halt_cmds function:

if [ $SG_HALT_REASON = "user_halt" ]; then

reason="user"

else

reason="auto"

/etc/cmcluster/db1_package/toolkit.sh stop $reason

"user" indicates that the package halt is a user initiated halt and "auto" indicates that the

package is being failed over automatically due to package dependencies, failure of a service

or due to dependent package failures.

Distribute the package configuration file, package control script and the framework scripts to

all nodes, and then apply the package configuration:

# cmapplyconf -P db1pkg.conf

Run the database package:

# cmrunpkg dbpkg_name

Check the package status using cmviewcl. Verify that the database instance is running.

Repeat the above steps for each database instance:

Oracle Modular Package Configuration Example

Install and Configuration directory operations:

With modular packages, there are two modes of operation available. By default, the toolkit

scripts that were previously used in legacy packages will be installed in the /opt/cmcluster/

toolkit/oracle directory. This directory is called the Installation directory. The user can

copy these scripts to a configuration directory and define this location in the parameter

"TKIT_DIR" in the modular package configuration file. Serviceguard uses the toolkit scripts in

the configuration directory by default. If the scripts are not found in the configuration directory,

Serviceguard takes them from the installation directory.

This feature is useful for customers wanting to use modified versions of the toolkit.

1. ASM Multi-Node Package Setup and Configuration

NOTE: This package must not be created if SGeRAC packages are created in the same

cluster.

Create the modular package configuration file asmpkg.conf in any location, (for example,

/etc/cmcluster/asm_package_mnp). This includes all the toolkit attributes which need

to be configured later by the user.

# cmmakepkg -m ecmt/oracle/oracle asmpkg.conf

Configure the Serviceguard parameters as mentioned below:

package_name - Set to any name desired.

package_type - Set to "multi_node".

Edit the service parameters if necessary. The service parameters are preset to:

44 Using the Oracle Toolkit in an HP Serviceguard Cluster