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
NOTE: For more information on the proposed framework for ASM integration with Serviceguard,
see whitepaper High Availability Support for Oracle ASM with Serviceguard available at:
www.hp.com/go/hpux-serviceguard-docs —> HP Enterprise Cluster Master Toolkit .
The Oracle toolkit uses Multi-Node Package (MNP) and the package dependency feature to
integrate Oracle ASM with HP Serviceguard. An MNP is used to encapsulate the per-node ASM
instances with one or more Oracle single-instance failover packages that are dependent on this
MNP. This configuration enables database instance to start up in the right order in relation to the
ASM instance, and in the event of a failover, to relocate to a node where an ASM instance is
available.
The Oracle toolkit scripts for ASM support with Serviceguard consists of a set of shell scripts that
are used to start, stop, and monitor an Oracle ASM and database instance and the configured
listeners. To use these scripts in legacy packages, the scripts must be integrated into the Serviceguard
package control script. For modular packages, the scripts must be integrated with the Serviceguard
master control script. Subsequent sections provide guidelines for integrating these scripts with the
Serviceguard package control script and the master control script.
In a Serviceguard cluster, packages created using the Oracle toolkit can co-exist with packages
created using the SGeRAC toolkit. In such an environment where the Oracle toolkit and the SGeRAC
toolkit coexist, the ASM MNP package need not be created using the Oracle toolkit. The
single-instance database failover packages must be made dependent on the SGeRAC Clusterware
multi-node package (OC MNP package). Also, you must create the package using the command
line interface and not the Serviceguard Managers.
A major advantage of ASM is the ease of management it provides for database files:
• The system administrator has only to specify the set of raw devices to be used in an ASM disk
group; the tasks of configuring and administering volume/disk groups and file systems are
eliminated. Oracle ASM makes use of the Oracle feature called Oracle-Managed Files and
performs the tasks of creating, deleting, and extending files on behalf of database instances;
additionally, it manages their mirroring and striping.
• If a device is added to, or deleted from, an ASM disk group, ASM automatically rebalances
database file striping based on the new disk layout.
Figure 1, contrasts the Oracle storage hierarchy as it appears when platform or third party volume
managers and file systems are used for Oracle data files, compared to when ASM is used. The
layers corresponding to file systems and volume managers are absorbed into ASM. The files and
directories in the storage hierarchy are not visible using standard operating system commands; to
display them the customer must use Oracle utilities.
Supporting Oracle ASM Instance and Oracle Database with ASM 31