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

the toolkit scripts that were previously used in legacy packages will
be
installed in the /opt/cmcluster/toolkit/oracle directory. This
directory is
called the Installation directory. The user can copy these scripts to a
configuration directory and define this location in the parameter
"TKIT_DIR" in
the modular package configuration file. Serviceguard uses the toolkit
scripts in
the configuration directory by default. If the scripts are not found in
the
configuration directory, Serviceguard takes them from the installation
directory.
This feature is useful for customers wanting to use modified versions
of the
toolkit.
1. ASM Multi-Node Package Setup and Configuration
- Create the modular package configuration file "asmpkg.conf" in any
location,
(e.g. /etc/cmcluster/asm_package_mnp). This includes all the
toolkit attributes
which need to be configured later by the user.
#cmmakepkg -m ecmt/oracle/oracle asmpkg.conf
- Configure the Serviceguard parameters as mentioned below.
package_name - Set to any name desired.
package_type - Set to "multi_node".
Edit the service parameters if necessary. The service parameters
are preset
to
service_name oracle_service
service_cmd "$SGCONF/scripts/ecmt/oracle/tkit_module.sh
oracle_monitor"
service_restart none
service_fail_fast_enabled no
service_halt_timeout 300
service_name oracle_listener_service
service_cmd "$SGCONF/scripts/ecmt/oracle/tkit_module.sh
oracle_monitor_listener"
service_restart none
service_fail_fast_enabled no
service_halt_timeout 300
Uncomment the second set of service parameters in the package
configuration
file which are used to monitor the listener.