User's Manual

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>
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.
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
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 Serviceguard CFS package(for example,.
SG-CFS-MP-1, CFS mount point package).
If the Oracle package is configured to depend on a Serviceguard CFS package, the Oracle
package will run as long as the dependee package is running. If the dependee package fails,
then the dependent Oracle package will also fail.
To configure dependency of the Oracle package, you must set the following configurable
parameters in the package configuration file:
DEPENDENCY_NAME
DEPENDENCY_CONDITION
DEPENDENCY_LOCATION
For example:
DEPENDENCY_NAME Oracle_dependency
DEPENDENCY_CONDITION SG-CFS-MP-1 = up
DEPENDENCY_LOCATION SAME_NODE
Support For Oracle Database without ASM 23