HP Serviceguard Enterprise Cluster Master Toolkit User Guide (5900-2145, April 2013)

/etc/cmcluster/pkg/ORACLE_TEST0/toolkit.sh start
test_return 51
}
Edit the customer_defined_halt_cmds function as described in the following example, to include
the check to get the reason for package halt, that is, whether the package halt is due to a
failure of a service or a user initiated shutdown. Also, run the toolkit.sh script with the stop
option.
For example:
function customer_defined_halt_cmds
{
# Stops the database with a "shutdown abort" or a
# "shutdown immediate" command.
if [ $SG_HALT_REASON = "user_halt" ]; then
reason="user"
else
reason="auto"
fi
/etc/cmcluster/pkg/ORACLE_TEST0/toolkit.sh stop $reason
test_return 52
}
• The Serviceguard package configuration file (ORACLE_TEST0.conf).
The package configuration file is created with "cmmakepkg -p", and must be placed in the
following location:
'/etc/cmcluster/pkg/${SID_NAME}/${SID_NAME}.conf'
For example:
/etc/cmcluster/pkg/ORACLE_TEST0/ORACLE_TEST0.conf
The configuration file should be edited according to the comments provided 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>
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, the ${SID_NAME} (that is, ORACLE_TEST0) is assigned to the
SERVICE_NAMEparameter because, there is only one service for this package.
For 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
26 Using the Oracle Toolkit in an HP Serviceguard Cluster