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: If the Oracle database is running in a cluster where SGeRAC packages are also
running, the Oracle database must be disabled from being started automatically by the Oracle
Clusterware.
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
Setting up the Toolkit
The internal structure of the Oracle Toolkit Scripts is similar for ASM Support. For more information
on the various Oracle toolkit scripts, see “Support for Oracle Database Without ASM” (page 10)
There are new variables introduced for ASM support, namely, INSTANCE_TYPE, ASM,
ASM_HOME, ASM_USER, ASM_SID, ASM_DISKGROUP, ASM_VOLUME_GROUP ,and
KILL_ASM_FOREGROUNDS. The following variables contained in haoracle.conf will help
understanding these parameters better.
Table 6 Variables or Parameters in haoracle.conf file
DescriptionParameter Name
This parameter must be set only when Oracle database packages created using
ECMT Oracle toolkit and SGeRAC packages run in the same cluster. This
ORA_CRS_HOME
parameter must be set to the Oracle Clusterware home directory. This parameter
can be set only using the CLI not the Serviceguard Manager.
This parameter determines whether the instance is an ASM instance or a
database instance. This can be set either to "database" or "ASM" only. This
INSTANCE_TYPE
parameter must be set accordingly for both the database and ASM instance
packages.
The home directory of Oracle. This parameter must be set only for the database
instance package.
ORACLE_HOME
User name of the Oracle database administrator. Will be used for starting and
stopping of the database. This parameter must be set only for the database
instance package.
ORACLE_ADMIN
The Oracle session name. This is called the session ID (SID). This parameter
must be set only for the database instance package. This parameter is set to
oracle by default.
SID_NAME
This option determines whether Automatic Storage Management (ASM) must
be used to manage the storage for the database instance. This parameter can
ASM
be set to either yes or no. Set it to yes if an ASM database is being used. In
all other cases, set it to no. By default, this parameter is set to no.
This parameter gives the list of all ASM disk groups used by the database
instance. This parameter must be set only for the ASM database instance
package.
ASM_DISKGROUP
NOTE: For ASM instance package, no value must be set for this parameter.
This parameter gives the list of volume groups used in the disk groups for the
ASM database instance. This parameter must be set only for the ASM database
instance package.
ASM_VOLUME_GROUP
NOTE: For ASM instance package, no value must be set for this parameter.
Setting up the Toolkit 41