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

LISTENER_RESTART=
PFILE=${ORACLE_HOME}/dbs/init${SID_NAME}.ora
MONITOR_PROCESSES[0]=ora_pmon_${SID_NAME}
MONITOR_PROCESSES[1]=ora_dbw0_${SID_NAME}
MONITOR_PROCESSES[2]=ora_ckpt_${SID_NAME}
MONITOR_PROCESSES[3]=ora_smon_${SID_NAME}
MONITOR_PROCESSES[4]=ora_lgwr_${SID_NAME}
MONITOR_PROCESSES[5]=ora_reco_${SID_NAME}
MAINTENANCE_FLAG=yes
MONITOR_INTERVAL=30
TIME_OUT=30
PARENT_ENVIRONMENT=no
CLEANUP_BEFORE_STARTUP=no
USER_SHUTDOWN_MODE=abort
ALERT_MAIL_ID=
The parameters ASM_DISKGROUP, ASM_VOLUME_GROUP, ASM_HOME, ASM_USER,
ASM_SID and KILL_ASM_FOREGROUNDS need to be set only for a database
package using ASM.
After setting up the Serviceguard environment, each clustered Oracle
instance should have the following files in the related package
directory. example, the ORACLE_TEST0 package, located at
/etc/cmcluster/pkg/ORACLE_TEST0, would contain the following files:
${SID_NAME}.conf (Serviceguard package configuration file)
${SID_NAME}.cntl (Serviceguard package control script)
toolkit.sh (Toolkit Interface Script)
haoracle.conf (Toolkit user configuration file)
haoracle.sh (Toolkit main script)
haoracle_sql.sh (Oracle start/stop script)
haoracle.mon (Toolkit Monitor Script)
halistener.mon (Listener Monitor Script)
Here's another example to create the Serviceguard package using
modular method
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~~~~~
i. Create the modular package configuration file "pkg.conf" by
including the
ECMT Oraclt toolkit module.