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

is stored on the ASM diskgroup. This is true only for the ASM
instance and not for the database instance that uses the ASM
diskgroup.
For an ASM instance, the ECM Toolkit cannot verify the existence
of the spfile on the ASM diskgroup. So, it is mandatory that a
pfile is created from the spfile on the local disk, at a location
that ECMT can access.
For 11gR2 ASM instance, the value of the PFILE attribute
must point to the pfile that is created on the local disk.
LISTENER: Set to "yes" if you want the scripts to start
and stop the Oracle Listener. This parameter
must be set only in the database instance
package.
LISTENER_NAME: The name of the listener process. This
parameter must be set only in the
database instance package.
LISTENER_PASS: The password of the listener process. This
parameter must be set only in the database
instance package.
MONITOR_PROCESSES: The names of all processes that should be
executing. This parameter must be set for
the ASM and the database instance packages.
The description of this attribute in the
package
configuration file has a sample of processes
that must be monitored for ASM and database
instances.
MAINTENANCE_FLAG: This variable will enable or disable
maintenance
mode for the Oracle package and ASM MNP. By
default
this is set to "yes". To disable this
feature, MAINTENANCE_FLAG must be set to "no".
When
Oracle Database/ASM must be maintained, then a
file "<package directory>/oracle.debug" must be
created. During this maintenance period, the
Database/ASM instance's process monitoring is
paused. Even if the instance is brought down,
its
package will not be failed over to the standby
node.
To continue monitoring and to exit from the
maintenance mode, you must remove the
"oracle.debug" file. It is the user's
responsibility to ensure that the instance is
properly running after the maintenance phase.
This
parameter can be set in the ASM and database