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
Table 4 Modular Package Scripts (continued)
DescriptionScript Name
analogous to the package directory in the legacy method of packaging. The
ADF is used to generate a package ASCII template file.
This script is called by the Master Control Script and acts as an interface
between the Master Control Script and the Toolkit interface script
(toolkit.sh). It also calls the toolkit configuration file generator script.
Module Script (tkit_module.sh)
This script is called by the Module Script when the package configuration is
applied using cmapplyconf, to generate the user configuration file in the
package directory (TKIT_DIR).
Toolkit Configuration File Generator
Script (tkit_gen.sh)
Support for multiple listeners
This feature provides support for multiple listeners with the Enterprise Cluster Master Oracle Toolkit.
It enables you to configure:
1. Single service to monitor all the listeners together: This is the default behavior. If one of the
configured listeners fail, it does not impact the service. However, if all the configured listeners
fail, the service fails, and it leads to the failover of the package to an alternate node. To enable
single service to monitor for all listeners, you must not pass the listener name to the service
command. The service_cmd in the package configuration file appears as follows:
DescriptionAttribute Name
oracle_listener_monitorservice_name
“$SGCONF/scripts/ecmt/oracle/tkit_module.sh
oracle_monitor_listener ”
service_cmd
noneservice_restart
noservice_fail_fast_enabled
300service_halt_timeout
2. A separate service to monitor each listener: This service is recommended if listeners are critical.
This approach of packaging listeners provides high availability to listeners. If any one of the
configured listeners fail, it leads to a failure of the listener service, and the package fails over
to an alternate node. To include the listener name, the default service_cmd in the package
configuration file must be changed.
For example:
DescriptionAttribute Name
oracle_listener_monitor_1service_name
“$SGCONF/scripts/ecmt/oracle/tkit_module.sh
oracle_monitor_listener <listener_name1>”
service_cmd
noneservice_restart
noservice_fail_fast_enabled
300service_halt_timeout
18 Using the Oracle Toolkit in an HP Serviceguard Cluster