Using the Oracle Toolkit in a HP Serviceguard Cluster README Revision: B.06.00, August 2010

service_halt_timeout 300
If the listener is not configured, comment the second set of
service parameters which are used to monitor the listener.
Edit the dependency parameters as shown:
dependency_name asm_dependency
dependency_condition <ASM 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 parameter TKIT_DIR. This parameter is
synonymous to
the legacy package directory (e.g. /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 section C 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, please refer the Whitepaper
"Modular package support in Serviceguard for Linux and ECM Toolkits" at
http://www.hp.com/go/hpux-serviceguard-docs -> HP 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 Enterprise Cluster
Master Toolkit