HP Serviceguard Enterprise Cluster Master Toolkit User Guide (5900-2145, April 2013)
Table Of Contents
- HP Serviceguard Enterprise Cluster Master Toolkit User Guide
- Contents
- 1 Introduction
- 2 Using the Oracle Toolkit in an HP Serviceguard Cluster
- Overview
- Supported Versions
- Support for Oracle Database Without ASM
- Supporting Oracle ASM Instance and Oracle Database with ASM
- What is Automatic Storage Management (ASM)?
- Why ASM over LVM?
- Configuring LVM Volume Groups for ASM Disk Groups
- Sample command sequence for configuring LVM Volume Groups
- Serviceguard support for ASM on HP-UX 11i v3 onwards
- Framework for ASM support with Serviceguard
- Installing, Configuring, and Troubleshooting
- Setting up DB instance and ASM instance
- Setting up the Toolkit
- ASM Package Configuration Example
- Modifying a Legacy Database Package Using an Older Version of Oracle ECMT Scripts to use the Scripts Provided for ASM Support
- Adding the Package to the Cluster
- Node-specific Configuration
- Error Handling
- Network Configuration
- Database Maintenance
- Configuring and packaging Oracle single-instance database to co-exist with SGeRAC packages
- Configuring Oracle single-instance database that uses ASM in a Coexistence Environment
- Attributes newly added to ECMT Oracle toolkit
- Configuring a modular failover package for an Oracle database using ASM in a coexistence environment
- Configuring a legacy failover package for an Oracle database using ASM in a Coexistence Environment
- ECMT Oracle Toolkit Maintenance Mode
- Supporting EBS database Tier
- Oracle ASM Support for EBS DB Tier
- 3 Using the Sybase ASE Toolkit in a Serviceguard Cluster on HP-UX
- Overview
- Sybase Information
- Setting up the Application
- Setting up the Toolkit
- Sybase Package Configuration Example
- Creating the Serviceguard package using Modular method
- Adding the Package to the Cluster
- Node-specific Configuration
- Error-Handling
- Network configuration
- Database Maintenance
- Cluster Verification for Sybase ASE Toolkit
- 4 Using the DB2 Database Toolkit in a Serviceguard Cluster in HP-UX
- 5 Using MySQL Toolkit in a HP Serviceguard Cluster
- MySQL Package Configuration Overview
- Setting Up the Database Server Application
- Setting up MySQL with the Toolkit
- Package Configuration File and Control Script
- Creating Serviceguard Package Using Modular Method
- Applying the Configuration and Running the Package
- Database Maintenance
- Guidelines to Start Using MySQL Toolkit
- 6 Using an Apache Toolkit in a HP Serviceguard Cluster
- 7 Using Tomcat Toolkit in a HP Serviceguard Cluster
- Tomcat Package Configuration Overview
- Multiple Tomcat Instances Configuration
- Configuring the Tomcat Server with Serviceguard
- Setting up the Package
- Creating Serviceguard Package Using Modular Method
- Setting up the Toolkit
- Error Handling
- Tomcat Server Maintenance
- Configuring Apache Web Server with Tomcat in a Single Package
- 8 Using SAMBA Toolkit in a Serviceguard Cluster
- 9 Using HP Serviceguard Toolkit for EnterpriseDB PPAS in an HP Serviceguard Cluster
- 10 Support and Other resources
- 11 Acronyms and Abbreviations
- Index
VXVM_DG[0]=/dev/vx/dsk/DG00_ORACLE_TEST0
Define the file systems which are used by the Oracle instance.
NOTE: One of these file systems must be the shared file system or logical volume containing
the Oracle Home configuration information ($ORACLE_HOME). The name of the instance is
used to name the disk groups, logical volumes, and file systems.
LV[0]=/dev/vx/dsk/DG00_${SID_NAME}
FS[0]=/${SID_NAME}
For example:
LV[0]=/dev/vx/dsk/DG00_ORACLE_TEST0/lvol1
FS[0]=/ORACLE_TEST0
NOTE: If you are using CFS mounted file systems, you must not configure volume groups,
logical volumes, and file systems in the package control script, but configure dependency on
Serviceguard CFS packages.
The service name must be the same as defined in the package configuration file. Always call
the Oracle executable script with start for the SERVICE_CMD definitions.
SERVICE_NAME[0]=ORACLE_${SID_NAME}
SERVICE_CMD[0]="/etc/cmcluster/pkg/${SID_NAME}/tookit.sh monitor"
SERVICE_RESTART[0]="-r 2"
For example:
SERVICE_NAME[0]=ORACLE_TEST0
SERVICE_CMD[0]="/etc/cmcluster/pkg/ORACLE_TEST0/toolkit.sh monitor"
SERVICE_RESTART[0]="-r 2"
If you must monitor a Listener, add another service for the listener, as follows:
SERVICE_NAME[1]=LSNR_0
SERVICE_CMD[1]="/etc/cmcluster/pkg/ORACLE_TEST0/toolkit.sh monitor_listener"
SERVICE_RESTART[1]="-r 2"
To monitor the hang condition of a data base, add another service, as follows:
SERVICE_NAME[2]=DB_HANG_0
SERVICE_CMD[2]="/etc/cmcluster/pkg/ORACLE_TEST0/toolkit.sh hang_monitor 30 failover"
SERVICE_RESTART[2]="-r 2"
You can set the service reset counter to zero for this service by using the Serviceguard command
cmmodpkg. The service restart counter is incremented each time the service fails. It can
determine when a package has exceeded its restart limit as defined by the SERVICE_RESTART
parameter in the package control script.
To reset the restart counter run the following command:
cmmodpkg [-v] [-n node_name] -R -s service_name package_name
NOTE: If listener monitoring is not required, do not configure a new service for listener.
Edit the customer_defined_run_cmds function to run the toolkit.sh script with the start option.
In the following example, the line /etc/cmcluster/pkg/ORACLE_TEST0/toolkit.sh
start is added, and the ":" null command line deleted.
For example:
function customer_defined_run_cmds
{
# Start the Oracle database.
Support for Oracle Database Without ASM 25