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

include the listener name.
For example:
service_name oracle_listener_monitor_1
service_cmd "$SGCONF/scripts/ecmt/oracle/tkit_module.sh
oracle_monitor_listener <listener_name1>"
service_restart none
service_fail_fast_enabled no
service_halt_timeout 300
The above lines have to be repeated for each listener. The user
should
ensure that the listener name passed to this service_cmd must match
to one
of those specified in the LISTENER_NAME array.
NOTE: It is not recommended to combine these two configurations
together,
i.e., it is not allowed to configure some listeners in a single
service
and the others in a separate service. The user should either
configure
all the listeners in a single service or in a separate service
for each of them but not both together.
NOTE: The user should ensure that the elements in LISTENER_RESTART
array and LISTENER_PASS array correspond to those in LISTENER_NAME
array in the package configuration file. When some listeners do not
require a restart value and some do not require a password, ordering
the elements in the arrays becomes difficult. In such cases, to avoid
confusion, it is recommended that LISTENER_RESTART is set to '0' and
LISTENER_PASS to 'empty quotes'(""), if they are not required.
Support for database hang detection
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
This feature enables the user to configure a separate service which
will detect the database hang and then take appropriate action if a
hang is detected. Database hang is detected by connecting to the
database and checking its status. If this process takes an unusually
long time or if toolkit is unable to retrieve the database status,
then it is assumed that the database is hung. The user has the option
to configure two attributes when configuring this service:
1. TIMEOUT: This attribute defines how long the script should wait
for the database hang check to return success. If the database
health cannot be determined within this time after connecting to the
database, then it is assumed that the database is hung. It can
have any positive integer as value. The default value for TIMEOUT
is 30 (seconds). This should not be confused with the TIME_OUT
package
attribute or the service_halt_timeout attribute.
2. ACTION: This attribute defines the action that must be taken if
a database hang is detected. Currently, this attribute can take one
of the following values.