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

'/etc/cmcluster/pkg/${SID_NAME}/${SID_NAME}.conf'
EXAMPLE:
/etc/cmcluster/pkg/ORACLE_TEST0/ORACLE_TEST0.conf
The configuration file should be edited as indicated by the
comments in that file. The package name must be unique within
the cluster. For clarity, use the $SID_NAME to name the package
"PACKAGE_NAME <SID_NAME>"
EXAMPLE:
PACKAGE_NAME ORACLE_TEST0
List the names of the clustered nodes to be configured to run the
package, using the NODE_NAME parameter:
NODE_NAME node1
NODE_NAME node2
The service name must match the service name used in the package
control script. The service name should include the Oracle
instance name (that is, ${SID_NAME}). In the following example,
since there is only one service for this package, the ${SID_NAME}
(that is, ORACLE_TEST0) is assigned to the SERVICE_NAME parameter.
EXAMPLE:
SERVICE_NAME ORACLE_TEST0
SERVICE_FAIL_FAST_ENABLED NO
SERVICE_HALT_TIMEOUT 300
If the listener should also be monitored, another service must
be
added.
SERVICE_NAME LSNR_0
SERVICE_FAIL_FAST_ENABLED NO
SERVICE_HALT_TIMEOUT 300
NOTE:- If listener monitoring is not intended do not create a new
service.
The run and halt scripts are (typically) identified as the control
script, as follows:
RUN_SCRIPT /etc/cmcluster/pkg/ORACLE_TEST0/ORACLE_TEST0.cntl
HALT_SCRIPT /etc/cmcluster/pkg/ORACLE_TEST0/ORACLE_TEST0.cntl
If you are using a CFS mounted file system for the Oracle package,
you need to configure dependency of the Oracle package on a