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

not specified, Oracle picks this up from
the Oracle configuration directory
$ORACLE_HOME/dbs.
This parameter when configured overrides
the default file/location. If both pfile
and spfile are present and this parameter
left unspecified, then ECM Oracle Toolkit
will make use of pfile as the parameter
file. To make use of spfile in the toolkit
do not configure this parameter and remove
the default pfile from its default
location.
MONITOR_PROCESSES: The names of all processes that should be
executing.
MAINTENANCE_FLAG This variable will enable or disable
maintenance mode for the Oracle package.
By default this is set to "yes". In
order to disable this feature
MAINTENANCE_FLAG should be set to "no".
When Oracle Database or ASM needs to be
maintained then a file "<package
directory>/oracle.debug" needs to be
touched. During this maintenance period
Oracle database or ASM instance's process
monitoring is paused. Even if an Oracle
instance is brought down, its package
will not be failed over to the standby
node. To continue monitoring and come
back from the maintenance mode, you
should remove the "oracle.debug" file.
It is the user's responsibility to ensure
that Oracle instance is properly running
after the maintenance phase.
NOTE: Setting MAINTENANCE_FLAG to "yes" and touching the
oracle.debug
file in the package directory will put the package in toolkit
maintenance
mode. Serviceguard A.11.19 release has a new feature which allows
individual
components of the package to be maintained while the package is
still up.
This feature is called Package Maintenance mode and is available
only for
modular packages. For more information using Package Maintenance
mode,
refer the whitepaper "Modular package support in Serviceguard for
Linux
and ECM Toolkits" located at
http://www.hp.com/go/hpux-serviceguard-docs -> HP Enterprise
Cluster Master Toolkit