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
7. Add in the customer_defined_run_cmds function:
/etc/cmcluster/asm_package_mnp/toolkit.sh start
8. Add in the customer_defined_halt_cmds function:
if [ $SG_HALT_REASON = "user_halt" ]; then
reason="user"
else
reason="auto"
fi
/etc/cmcluster/asm_package_mnp/toolkit.sh stop $reason
Here, "user" indicates that the package halt is a user initiated halt and "auto" indicates
that the package is being failed over automatically due to package dependencies, failure
of a service, or due to dependent package failures.
9. Distribute the package configuration file, package control script, and the framework
scripts to all nodes, and then apply the package configuration.
# cmapplyconf -P asmpkg.conf
10. Run the ASM package.
cmrunpkg asmpkg_name
11. Check the package status using cmviewcl. Verify that the ASM instance is running on
all the nodes.
Database Failover Package Setup and Configuration
1. Create your own database package directory under /etc/cmcluster, and copy over the
files shipped in the bundle.
2. Log in as root:
# mkdir /etc/cmcluster/db1_package
# cd /etc/cmcluster/db1_package
3. Copy the framework scripts provided to this location:
cp /opt/cmcluster/toolkit/oracle/*
.
4. Edit the configuration file haoracle.conf for the database failover package to fit your
Oracle environment. Set the following parameters in the configuration file:
ORA_CRS_HOME=/app/oracle/crs # . This attribute is needed only when this toolkit is used
in an SGeRAC cluster.
INSTANCE_TYPE=database
ORACLE_HOME=/ORACLE_TEST0
ORACLE_ADMIN=oracle
SID_NAME=ORACLE_TEST0
ASM=yes
ASM_DISKGROUP[0]=asm_dg1
ASM_DISKGROUP[1]=asm_dg2
ASM_VOLUME_GROUP[0]=vgora_asm1
ASM_VOLUME_GROUP[1]=vgora_asm2
ASM_HOME=/ASM_TEST0
ASM_USER=oracle
ASM_SID=+ASM
LISTENER=yes
LISTENER_NAME=LSNR_TEST0
LISTENER_PASS=
PFILE=${ORACLE_HOME}/dbs/init${SID_NAME}.ora
MONITOR_PROCESSES[0]=ora_pmon_${SID_NAME}
MONITOR_PROCESSES[1]=ora_dbw0_${SID_NAME}
46 Using the Oracle Toolkit in an HP Serviceguard Cluster