HP Serviceguard Enterprise Cluster Master Toolkit User Guide, June 2014
dependency_name asm_dependency
dependency_condition <ASM MNP package_name>=up
dependency_location same_node
e. If SGeRAC packages are configured in the same cluster, the ASM MNP package should
not be created and the Oracle database package should depend on the SGeRAC
Clusterware package instead of the ASM MNP. Use the following definition
DEPENDENCY_NAME asm_dependency
DEPENDENDY_CONDITION <SGeRAC OC MNP PACKAGE_NAME>=up
DEPENDENCY_LOCATION same_node
LVM logical volumes are used in disk groups, therefore, specify the names of the volume
groups on which the ASM diskgroups reside on, for the attribute "vg".
f. Configure the ip_subnet and ip_address parameters.
g. 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 contains the toolkit configuration file haoracle.conf on all configured
nodes. Note that the TKIT_DIR for this package must be different from the TKIT_DIR
configured for the ASM MNP.
To Configure the other toolkit parameters for the database package, see“Support for
Oracle Database Without ASM” (page 10)
h. Apply the package configuration using:
# cmapplyconf -P db1pkg.conf
This command "applies" the package configuration to the CDB. It also creates toolkit
configuration directory defined by TKIT_DIRon 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, see the whitepaper Migrating Packages from Legacy to Modular Style, October
2007
available athttp://www.hp.com/go/hpux-serviceguard-docs —>HP Serviceguard
Enterprise Cluster Master Toolkit
To configure an ECMT modular failover package for an Oracle database using ASM in a
Serviceguard cluster where SGeRAC packages are also running.
NOTE: When you configure an Oracle package in an SGeRAC cluster, you must use the
command line interface and not the Serviceguard manager interface to create the package.
a. Disable the Oracle database instance from being managed automatically by the Oracle
Clusterware.
To set the database management policy to manual, log in as the Oracle administrator,
and then run the following command:
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 then create the database package directory:
# mkdir /etc/cmcluster/db1_package
50 Using the Oracle Toolkit in an HP Serviceguard Cluster