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
The attribute, DB_SERVICE is used to start and stop the DB service through the DB package. This
attribute is commented by default. You can either set the attribute DB_SERVICE to all or specify
the DB service names that needs to be started and stopped by the DB package.
To start and stop all DB services configured in the DB, managed by this package, set this attribute
to all.
For example: ecmt/oracle/oracle/DB_SERVICE all
To start and stop one or more specific DB services through this DB package, you must specify the
service names using multiple instances of this attribute, as shown in the following example:
Example:
• ecmt/oracle/oracle/DB_SERVICE <service1>
• ecmt/oracle/oracle/DB_SERVICE <service2>
• ecmt/oracle/oracle/DB_SERVICE <service3>
Support for database hang detection
This feature enables you to configure a separate service which will detect the database hang and
then takes 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, it is considered that the database is in a hang state. While
configuring this service, you can also configure the following two options:
1. TIMEOUT: This attribute defines the wait time of the script for the database hang check to
return success. If the database health cannot be determined within this time after connecting
to the database, it is assumed that the database is in a hang state. 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 you must take, if you detect a database hang.
Currently, this attribute can take one of the following values:
• log - Log a message. A message is logged to the package log every time a hang is
detected. If the MONITOR_INTERVAL attribute is set to 30 seconds, a message is logged
to the package log file every 30 seconds.
• alert - Send an alert mail. An alert mail is sent to the email address specified with the
ALERT_MAIL_ID attribute. The mail is sent only the first time a database hang is detected.
• failover - Failover the package to adoptive node.
The default value for ACTION is 'failover'.
The syntax of the service command is as follows: service_cmd
"$SGCONF/scripts/ecmt/oracle/tkit_module.sh oracle_hang_monitor <TIMEOUT> <ACTION>"
The following is an example in which the TIMEOUT is set to 40 seconds and the ACTION is set
to 'alert':
service_name db_hang_check
service_cmd "$SGCONF/scripts/ecmt/oracle/tkit_module.sh oracle_hang_monitor 40 alert"
service_restart none
service_fail_fast_enabled no
service_halt_timeout 300
Support for Oracle database backup mode
During the Oracle database instance package start or package failover on the other cluster node,
if the database is in the online backup mode (based on your input for the package attribute
DISABLE_BACKUP_MODE), the toolkit gets the database out of the backup mode. The valid values
for this parameter are yes and no. By default, the value is set to no.
nl
For example: tkit/oracle/oracle/DISABLE_BACKUP_MODE no.
nl
Support for Oracle Database Without ASM 21