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
Table 6 Variables or Parameters in haoracle.conf file (continued)
DescriptionParameter Name
NOTE: If the Oracle database package is dependent on the SGeRAC
clusterware multi-node package (OC MNP), the Oracle database package
automatically goes into toolkit maintenance mode when the SGeRAC OC MNP
is put into toolkit maintenance mode. To put the SGeRAC OC MNP into toolkit
maintenance mode, its MAINTENANCE_FLAG attribute must be set to 'yes' and
a file oc.debug must be created manually in the OC MNP working directory
on that node. For more information on how to put the SGeRAC OC MNP
package in toolkit maintenance mode, see SGeRAC toolkit README file. If the
MAINTENANCE_FLAG attribute of the SGeRAC OC MNP is set to 'yes', this
parameter must also be set to 'yes' in the Oracle database package.
The time interval (in seconds) the script waits between checks to ensure that the
Oracle instance is running. Default is 30 seconds. This parameter must be set
in the ASM and database instance packages.
MONITOR_INTERVAL
The amount of time, in seconds, the script waits during package halt for the
Oracle database shutdown to complete before removing the Oracle processes
TIME_OUT
defined in MONITOR_PROCESSES. The TIME_OUT variable is used to protect
against a worst-case scenario where a hung instance prevents the package
halt script from completing, therefore preventing the standby node from starting
the instance. This parameter must be set for the ASM and database instance
packages.
This is used to mention if the Oracle or ASM administrator's shell should be
invoked as a new shell or as a sub-shell that inherits the variables set in the
PARENT_ENVIRONMENT
parent shell. This can be set to either 'yes' or 'no' only. Set to 'yes' if the Oracle
or ASM administrator's shell should be invoked as a sub-shell. Set to 'no' if the
Oracle or ASM administrator's shell should be invoked as a new shell. If set to
'no', the Oracle or ASM administrator's .profile file is executed and the variables
set in this .profile file are available to the new shell. This parameter can be set
in the ASM and database instance package.
This parameter indicates whether 'shutdown abort' must be executed before
the startup of the Oracle or ASM instance. 'shutdown abort' ensures the cleanup
CLEANUP_BEFORE_STARTUP
of uncleared shared memory or semaphores. This parameter can be set to only
yes or no. Default value is no. This parameter can be set in the ASM and
database instance package.
This parameter is used to specify the instance shutdown mode only when a
shutdown is initiated by the user and not due to a failure of a service. this
USER_SHUTDOWN_MODE
parameter can take values "abort" or "immediate" only. If "abort" is specified,
the instance is shutdown using the abort option. If "immediate" is specified,
the instance is shutdown using the immediate option. The default value is
"abort". This parameter can be set in the ASM and database instance package.
When ASM is being used, this parameter is used to specify whether the ASM
foreground processes of the form Oracle <ASM_SID> having file descriptors
KILL_ASM_FOREGROUNDS
open on the dismounted disk group volumes must be killed during database
package halt. The Oracle scripts wait for a timeout of 12 seconds before
terminating the foreground processes that continue to have file descriptors open
on the dismounted disk group volumes. This parameter can be set to either
"yes" or "no". The default value is 'yes'. This parameter must be set only in the
case of an ASM database instance package.
This parameter should be populated only in case the Oracle database package
is dependent on the SGeRAC OC MNP package. This parameter should point
OC_TKIT_DIR
to the working directory of the SGeRAC OC MNP. For modular packages, the
value for this parameter is automatically populated when the package is created
using the cmapplyconf command. For legacy packages, this attribute must be
populated manually in the haoracle.conf file. This parameter can be set only
using the CLI and not using the Serviceguard Manager.
Setting up the Toolkit 43