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
fs_directory /dbpath/db2_payroll_inst/NODE0000
fs_type "ext3"
fs_mount_opt "-o rw"
fs_umount_opt ""
fs_fsck_opt ""
fs_name /dev/vg_dd0/lvol2
fs_directory /dbpath/db2_payroll_inst2/NODE0001
fs_type "ext3"
fs_mount_opt "-o rw"
fs_umount_opt ""
fs_fsck_opt ""
This example above defines the variable for two database partitions, that is, partition 0 and
partition 1, NODE0000 and NODE0001. The variables are named NODE0000 in accordance
with DB2 directory structure.
5. Use cmcheckconf command to check the validity of the specified configuration. For example,
#cmcheckconf -P pkg.conf
6. If the cmcheckconf command does not report any errors, use the cmapplyconf command
to add the package into Serviceguard environment. For example,
#cmapplyconf -P pkg.conf
Creating Serviceguard package using legacy method.
Create the Serviceguard package using legacy method.
To create Serviceguard package using legacy method:
mkdir /etc/cmcluster/pkg/db2_pkg/
Copy the toolkit files from db2
cd /etc/cmcluster/pkg/db2_pkg/
cp /opt/cmcluster/toolkit/db2/* ./
Create a configuration file (pkg.conf) and package control script pkg.cntl) as follows:
cmmakepkg -p pkg.conf
cmmakepkg -s pkg.cntl
NOTE: There should be one set of configuration and control script files for each DB2 instance.
The Serviceguard package control script (pkg.cntl).
The following are some examples of modifications to the Serviceguard package control script that
you must make to customize to your environment.
VOLUME GROUPS
1. Define the volume groups that are used by the DB2 instance. File systems associated with
these volume groups are defined as follows:
VG[0]=/dev/vg0_payroll
For example:
VG[0]=/dev/vg0_payroll
2. Define the file systems which are used by the DB2 instance.
NOTE: One of these file systems must be the shared file system/logical volume containing
the DB2 home configuration information ($DB2_HOME). The name of the instance is used to
name the volume groups, logical volumes and file systems. For example,
LV[0]=/dev/vg0_payroll/lvol1
FS[0]=/mnt/payroll
DB2 Package configuration example 83