HP Serviceguard Enterprise Cluster Master Toolkit User Guide, June 2014

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 use a CFS mounted file system for the Oracle package, you must 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 runs as long as the dependee package is running. If the dependee package fails,
the dependent Oracle package also fails.
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
NOTE: If the Oracle database is running in a cluster where SGeRAC packages are also
running, the ECMT Oracle single-instance database package must be made dependent on
the SGeRAC Oracle clusterware multi-node package (OC MNP). The dependency type should
be 'SAME_NODE=up'. This is because, when the Oracle clusterware is halted, it halts the
Oracle single-instance database. By putting this dependency, we ensure that the database
package is always halted first and then the SGeRAC OC MNP is halted. Also, the Oracle
database must be disabled from being started automatically by the Oracle Clusterware. To
disable the Oracle database:
Log in as the Oracle administrator and run the following command to set the database
management policy to manual:
For Oracle 10g:
# $ORACLE_HOME/bin/srvctl modify database -d <dbname> y manual
For Oracle 11g:
# $ORACLE_HOME/bin/srvctl modify database -d <dbname> y MANUAL
The Oracle toolkit user configuration file.
In the package directory, modify the haoracle.conf configuration file for this Oracle
instance.
NOTE: In case of a modular package, the user need not specify the parameter values in the
haoracle.conf file. The toolkit populates haoracle.conf on its own.
For example:
Edit the haoracle.conf script as indicated by the comments in that script. You must set the
variables as shown in the following example:
Support for Oracle Database Without ASM 27