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

If 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"
fi
/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 these 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