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
SERVICE_FAIL_FAST_ENABLED NO
SERVICE_HALT_TIMEOUT 300
NOTE: If listener monitoring is not intended, do not create a new service.
The run and halt scripts are (typically) identified as the control script, as follows: RUN_SCRIPT
/etc/cmcluster/pkg/ORACLE_TEST0/ORACLE_TEST0.cntl HALT_SCRIPT
/etc/cmcluster/pkg/ORACLE_TEST0/ORACLE_TEST0.cntl .
If you use a CFS mounted file system for the Oracle package, you must configure dependency
of the Oracle package on a Serviceguard CFS package (for example, SG-CFS-MP-1, CFS
mount point package).
If the Oracle package is configured to depend on a Serviceguard CFS package, the Oracle
package runs as long as the dependee package is running. If the dependee package fails,
the dependent Oracle package also fails.
To configure dependency of the Oracle package, you must set the following configurable
parameters in the package configuration file:
DEPENDENCY_NAME
DEPENDENCY_CONDITION
DEPENDENCY_LOCATION
For example:
DEPENDENCY_NAME Oracle_dependency
DEPENDENCY_CONDITION SG-CFS-MP-1 = up
DEPENDENCY_LOCATION same_node
NOTE: If the Oracle database is running in a cluster where SGeRAC packages are also
running, the ECMT Oracle single-instance database package must be made dependent on
the SGeRAC Oracle clusterware multi-node package (OC MNP). The dependency type should
be 'SAME_NODE=up'. This is because, when the Oracle clusterware is halted, it halts the
Oracle single-instance database. By putting this dependency, we ensure that the database
package is always halted first and then the SGeRAC OC MNP is halted. Also, the Oracle
database must be disabled from being started automatically by the Oracle Clusterware. To
disable the Oracle database:
◦ Log in as the Oracle administrator and run the following command to set the database
management policy to manual:
For Oracle 10g:
# $ORACLE_HOME/bin/srvctl modify database -d <dbname> —y manual
For Oracle 11g:
# $ORACLE_HOME/bin/srvctl modify database -d <dbname> —y MANUAL
• The Oracle toolkit user configuration file.
In the package directory, modify the haoracle.conf configuration file for this Oracle
instance.
NOTE: In case of a modular package, the user need not specify the parameter values in the
haoracle.conf file. The toolkit populates haoracle.conf on its own.
For example:
Edit the haoracle.conf script as indicated by the comments in that script. You must set the
variables as shown in the following example:
Support for Oracle Database Without ASM 27