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

DEPENDENCY_NAME asm_dependency

DEPENDENDY_CONDITION <SGeRAC OC MNP PACKAGE_NAME>=up

DEPENDENCY_LOCATION same_node

Since LVM logical volumes are used in disk groups, specify the name(s) of the volume groups

on which the ASM diskgroups reside on, for the attribute "vg".

Configure the ip_subnet and ip_address parameters.

Configure the toolkit parameterTKIT_DIR. This parameter is synonymous to the legacy

package directory (for example, /etc/cmcluster/dg1_package). On a cmapplyconf,

TKIT_DIR will contain the toolkit configuration file haoracle.conf on all configured nodes.

Note that the TKIT_DIR for this package should be different from the TKIT_DIR configured

for the ASM MNP.

Configure the other toolkit parameters for the database package as mentioned in “Support

For Oracle Database without ASM” (page 9) for the database failover legacy package.

Apply the package configuration using:

# cmapplyconf -P db1pkg.conf

This command "applies" the package configuration to the CDB (Serviceguard Configuration

Database). It also creates toolkit configuration directory defined by TKIT_DIR on all target

nodes, if not already present and then creates the toolkit configuration file in it with the values

specified in the db1pkg.conf file.

For more information on modular packages, see whitepaper Modular package support in

Serviceguard for Linux and ECM Toolkits available at http://www.hp.com/go/

hpux-serviceguard-docs —>HP Serviceguard Enterprise Cluster Master Toolkit.

Also refer the whitepaper Migrating Packages from Legacy to Modular Style, October 2007

for more information. You can find this whitepaper at http://www.hp.com/go/

hpux-serviceguard-docs —>HP Serviceguard Enterprise Cluster Master Toolkit

3. To configure a ECMT modular failover package for an Oracle database using ASM in a

Serviceguard cluster where SGeRAC packages are also running.

NOTE: When configuring a Oracle package in a SGeRAC cluster, command line interface

should be used to create the package and the Serviceguard Manager interface should not be

used.

a. Disable the Oracle database instance from being managed automatically by the Oracle

Clusterware.

management policy to manual:

For Oracle 10g:

# $ORACLE_HOME/bin/srvctl modify database -d <dbname> -y manual

For Oracle 11g:

# $ORACLE_HOME/bin/srvctl modify database -d <dbname> -y MANUAL

b. Log in as root and create the database package directory:

# mkdir /etc/cmcluster/db1_package

c. Create the modular package configuration file db1pkg.conf by including the toolkit

attributes that need to be configured later by the user.

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

Edit the package configuration file pkg.conf, and configure the Serviceguard parameters

as mentioned below:

package_name - Set to any name desired.

46 Using the Oracle Toolkit in an HP Serviceguard Cluster