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

Set the TKIT_DIR variable as the path of <package_directory>. For example,
TKIT_DIR /etc/cmcluster/pkg/db2_pkg
Set the INSTANCE_NAME variable as the DB2 instance name. For example,
INSTANCE_NAME db2_payroll_inst
Set the PARTITION_NUMBER variable to the partition numbers of the database which need
to be started, stopped, and monitored using this package. By default it is set to 0. Repeat the
above variable to add additional partitions. For example,
PARTITION_NUMBER 0
PARTITION_NUMBER 1
NOTE: Logical partitions of a database can be grouped to run in a single package while
physical partitions need separate packages for each.
Set the MONITOR_PROCESSES variable to process names, which must be monitored and
cleaned up to ensure fail safe shutdown of the DB2 Instance or Partition. The actual monitoring
is done by a command called db2gcf. The MONITOR_PROCESSES is only used to kill the
processes that remain alive after the shutdown of the database. By default, .db2sysc. is
configured in this variable. Repeat the variable to additional processes, if required. For
example,
MONITOR_PROCESSES db2sysc
Set the MAINTENANCE_FLAG variable to yes or no, to enable or disable the maintenance
mode feature for the package. For example,
MAINTENANCE_FLAG yes
Set the MONITOR_INTERVAL in seconds to specify how often the partition or instance is
monitored. For example,
MONITOR_INTERVAL 30
Set the TIME_OUT variable to the time that the toolkit must wait for completion of a normal
shut down, before initiating a forceful halt of the application. For example,
TIME_OUT 30
Set the monitored_subnet variables to the subnet that is monitored for the package.
Set the monitored_subnet_access variable to full if the subnet is available on all nodes,
otherwise, set it to partial.
monitored_subnet_access full
Set the variables for adding the package relocatable IP address. For example,
ip_subnet x.x.x.x
Set the ip_subnet_node to the node names where the subnet is valid. For example,
ip_subnet_node node1
ip_subnet_node node2
Set theip_address to a valid package IP. For example,
ip_address x.x.x.x
Create a separate vg variable for each volume group. For example,
vg vg_dd0
Create a separate fs_name, fs_directory, fs_type, and fs_mount_opt variables
for each database partition. For example,
fs_name /dev/vg_dd0/lvol1
82 Using the DB2 Database Toolkit in a Serviceguard Cluster in HP-UX