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
Setting up the Toolkit
Toolkit Overview
Use swinstall to properly install both Serviceguard and the Enterprise Cluster Master Toolkit (referred
to as the ECMT), which includes the scripts for Oracle.
After installing the toolkit, six scripts and a README file is created in the/opt/cmcluster/
toolkit/oracle directory. Two more scripts and one file is installed that is used only for modular
packages. The two scripts are in the /etc/cmcluster/scripts/ecmt/Oracle directory and
the third file is installed in the /etc/cmcluster/modules/ecmt/Oracle directory.
For legacy packages, there is one toolkit configuration script (haOracle.conf ) and nine functional
scripts that is described in the Table 2 (page 14)(toolkit.sh , haoracle.sh,
haoracle_sql.sh, haoracle.mon, halistener.mon, hadbhang.mon,
hagetdbstatus.sh, hatimeoutdbhang.sh, and SGAlert.sh) that coordinates with each
other to integrate Oracle database with the Serviceguard package control script.
Table 2 Legacy Package Scripts
DescriptionScript Name
This script contains a list of pre-defined variables that you must customize for
use with a particular database instance. This is a configuration file that is read
haoracle.conf (toolkit configuration file)
by the toolkit script, haoracle.sh. Table 3 (page 15) shows a list of variables
in haoracle.conf which must be set for the database package.
This script contains a list of internally used variables and functions that support
the starting and stopping of an Oracle database or ASM instance. This script
is called by toolkit.sh to perform the following:
Main Script (haoracle.sh )
• On package startup, it starts the database or ASM instance, a listener
process in case of a database instance and launches monitor processes.
• On package halt, it stops the database or ASM instance, the listener process
in case of a database instance, and monitor process.
• Oracle instance start/stop script (haoracle_sql.sh) This script contains
functions for starting and stopping Oracle instances and the listeners. This
script is invoked by the main script (haoracle.sh) to start up and shut
down Oracle.
This script contains a list of internally used variables and functions for
monitoring an Oracle server instance. This script is called by haoracle.sh.
Monitor Script (haoracle.mon)
By default, the following processes are monitored: ora_pmon_$SID_NAME,
ora_smon__$SID_NAME, ora_lgwr_$SID_NAME, ora_dbwr_$SID_NAME,
ora_ckpt_$SID_NAME, and ora_reco_$SID_NAME ($SID_NAME is the session
id name of the Oracle instance). These process names are contained in the
variable MONITOR_PROCESSES.
To include other processes to be monitored, you must add the names of the
processes to MONITOR_PROCESSES array in the toolkit configuration file
(haoracle.conf). For example, if Oracle archiver is enabled, archiver
process name can be added to theMONITOR_PROCESSES array
(ora_arc0_${SID_NAME}).
This script is called by haoracle.sh to monitor the configured listeners. The
script makes use of a command supplied by Oracle to check the status of the
listener.
Listener Monitor Script (halistener.mon)
The hadbhang.mon script is called by haoracle.sh to monitor the Oracle
instance for possible 'hung' state. hadbhang.mon script inturn uses
hagetdbstatus.sh and hatimeoutdb hang.sh to check the database status.
Database Hang Monitor Scripts
(hadbhang.mon, hagetdbstatus.sh,
hatimeoutdbhang.sh)
14 Using the Oracle Toolkit in an HP Serviceguard Cluster