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
2 Using the Oracle Toolkit in an HP Serviceguard Cluster
This chapter describes the High Availability Oracle Toolkit designed for use in a HP Serviceguard
environment. This chapter covers the basic steps for configuring an Oracle instance in a HP-UX
cluster, and is intended for users who want to integrate an Oracle Database Server with
Serviceguard.
You must be familiar with the installation and configuration procedures, for ServiceGuard
configuration and Oracle Database Server concepts.
Use this toolkit to configure only single instance Oracle database and if you want to configure
Oracle RAC, use SGeRAC. For more information, see www.hp.com/go/hpux-serviceguard-docs
-> HP Serviceguard Extension for RAC.
Overview
The Oracle Toolkit for Serviceguard consists of a set of shell scripts that are used to start, stop, and
monitor an Oracle database instance, Automatic Storage Management (ASM) instance and the
configured listeners.
The Oracle toolkit is designed to work in either of the following two modes:
• As a database instance failover package.
• As an ASM Multi-Node Package (MNP).
There can be only one ASM MNP package configured per cluster, while there can be multiple
database instance packages per cluster.
To use this toolkit in legacy style, the toolkit scripts must be integrated into the Serviceguard package
control script. For example to create a legacy package, See “Support for Oracle Database Without
ASM” (page 10) and “Supporting Oracle ASM Instance and Oracle Database with ASM” (page 29)
Legacy style packages have been deprecated. HP strongly recommends that you use modular
packages.
For more information on creating modular packages, see “Support for Oracle Database Without
ASM” (page 10) “Supporting Oracle ASM Instance and Oracle Database with ASM” (page 29)
and the whitepaper Modular package support in Serviceguard for Linux and ECM Toolkits available
at http://www.hp.com/go/hpux-serviceguard-docs —>HP Serviceguard Enterprise Cluster Master
Toolkit.
Supported Versions
You must install the supported and compatible versions of Serviceguard, Oracle, and the Enterprise
Cluster Master Toolkit (ECMT), which contains the Oracle toolkit.
Unless otherwise stated, this toolkit supports all storage and volume managers that Serviceguard
supports.
To find the latest supported versions of these products on Serviceguard, Oracle, Cluster File System
(CFS) and HP-UX versions, check the compatibility matrix available at http://www.hp.com/go/
hpux-serviceguard-docs —>HP Serviceguard.
To use CFS, you must install the appropriate version of HP Serviceguard Storage Management
Suite. For more information on the latest version of the HP Serviceguard Storage Management
Suite Release Notes, see the appropriate version of HP Serviceguard Storage Management Suite
at http://www.hp.com/go/hpux-serviceguard-docs.
In a Serviceguard cluster, packages created using the ECMT Oracle toolkit can co-exist with
packages created using the SGeRAC toolkit. In such cases, the single-instance database failover
packages must be made dependent on the SGeRAC clusterware multi-node package (OC MNP
Overview 9