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

In the package control script asmpkg.cntl, edit the following
parameters.
Configure the package service:
SERVICE_NAME[0]="ORACLE_ASM_SRV"
SERVICE_CMD[0]="/etc/cmcluster/asm_package_mnp/toolkit.sh monitor"
SERVICE_RESTART[0]="-r 2"
Add in the customer_defined_run_cmds function:
/etc/cmcluster/asm_package_mnp/toolkit.sh start
Add in the customer_defined_halt_cmds function:
if [ $SG_HALT_REASON = "user_halt" ]; then
reason="user"
else
reason="auto"
fi
/etc/cmcluster/asm_package_mnp/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 asmpkg.conf
- Run the ASM package.
# cmrunpkg asmpkg_name
Check the package status using cmviewcl. Verify that the ASM
instance is
running on all the nodes.
2. Database Failover Package Setup and Configuration
- Create your own database package directory under /etc/cmcluster and
copy
over the files shipped in the bundle.
Login as root:
# mkdir /etc/cmcluster/db1_package
# cd /etc/cmcluster/db1_package