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
• ASM Multi-Node Package Setup and Configuration
NOTE: This package must not be created if SGeRAC packages are created in the same
cluster.
Configuring ASM package:
1. Create your own ASM package directory under /etc/cmcluster and copy over the scripts
in the bundle.
2. Log in as root:
# mkdir /etc/cmcluster/asm_package_mnp
# cd /etc/cmcluster/asm_package_mnp
3. Copy the framework scripts to the following location : cp /opt/cmcluster/toolkit/oracle/*.
4. Edit the configuration file haoracle.conf for the ASM MNP to fit your specific Oracle
environment as indicated by the comments in that script. You must set the variables as
shown in the following example:
INSTANCE_TYPE=ASM
ASM_HOME=/ASM_TEST0
ASM_USER=oracle
ASM_SID=+ASM
PFILE=${ASM_HOME}/dbs/init${ASM_SID}.ora
LISTENER=no (Change from default value "yes" to "no")
MONITOR_PROCESSES[0]=asm_pmon_${ASM_SID}
MONITOR_PROCESSES[1]=asm_dbw0_${ASM_SID}
MONITOR_PROCESSES[2]=asm_ckpt_${ASM_SID}
MONITOR_PROCESSES[3]=asm_smon_${ASM_SID}
MONITOR_PROCESSES[4]=asm_lgwr_${ASM_SID}
MONITOR_PROCESSES[5]=asm_rbal_${ASM_SID}
MONITOR_PROCESSES[6]=asm_gmon_${ASM_SID}
MAINTENANCE_FLAG=yes
MONITOR_INTERVAL=30
TIME_OUT=30
PARENT_ENVIRONMENT=yes
CLEANUP_BEFORE_STARTUP=no
USER_SHUTDOWN_MODE=abort
5. Generate the ASM MNP package configuration file, control script, and then edit the
parameters in these files for the ASM MNP in the package directory.
# cmmakepkg -p asmpkg.conf
# cmmakepkg -s asmpkg.cntl
In the package configuration file asmpkg.conf, edit the following parameters:
PACKAGE_NAME - Set to any name desired.
PACKAGE_TYPE - Set to multi_node.
FAILOVER_POLICY, FAILBACK_POLICY - Should be commented out.
RUN_SCRIPT /etc/cmcluster/asm_package_mnp/asmpkg.cntl
HALT_SCRIPT /etc/cmcluster/asm_package_mnp/asmpkg.cntl
SERVICE_NAME ORACLE_ASM_SRV
SERVICE_FAIL_FAST_ENABLED NO
SERVICE_HALT_TIMEOUT 300
6. In the package control script asmpkg.cntl, edit the following parameters:
Configure the package service:
SERVICE_NAME[0]="ORACLE_ASM_SRV"
SERVICE_CMD[0]="/etc/cmcluster/asm_package_mnp/toolkit.sh monitor"
SERVICE_RESTART[0]="-r 2"
ASM Package Configuration Example 45