Using the Serviceguard Toolkit for Oracle Data Guard in an HP Serviceguard Cluster B.01.00, September 2010

ManualsBrandsHP ManualsSoftwareHP Serviceguard Toolkit for Oracle Data Guard

Using the Serviceguard Toolkit for Oracle Data Guard in an HP

Serviceguard Cluster

=========================================================================

=================

Version: B.01.00

CONTENTS:

A. Overview

B. Supported versions

C. Setting Up Oracle Data Guard

D. Setting Up the Toolkit

E. Oracle Data Guard Package Configuration Example

F. Adding the Package to the Cluster

G. Oracle Data Guard Maintenance

H. Using Serviceguard Toolkit for Oracle Data Guard in

Continentalclusters environment

I. Using Serviceguard Toolkit for Oracle Data Guard in Metrocluster and

Extended Distance

Cluster environments

J. Verification of the setup

PREFACE:

This README file describes the High Availability Serviceguard Toolkit for

Oracle Data Guard

(also referred to as "Oracle Data Guard Toolkit") designed for use in a

Serviceguard environment.

This README covers the basic steps for configuring Oracle Data Guard in

an HP-UX cluster, and

is intended for users who want to integrate in an HP-UX cluster, and is

intended for users who

want to integrate Oracle Data Guard with HP Serviceguard.

This README assumes that its readers are already familiar with

Serviceguard configuration,

as well as with Oracle Data Guard concepts, including installation and

configuration procedures.

A. Overview

The Serviceguard Toolkit for Oracle Data Guard consists of a set of shell

scripts that are used

to start, stop, and monitor Oracle Data Guard primary and standby

database instances.

Oracle Data Guard provides protection to Oracle Database by replicating

the database data to

one or more standby databases. Integrating Oracle Data Guard with HP

Serviceguard has the following

advantages:

- Provides High Availability for Data Guard processes for both primary

and the standby databases.

Summary of content (15 pages)

PAGE 1
Using the Serviceguard Toolkit for Oracle Data Guard in an HP Serviceguard Cluster ========================================================================= ================= Version: B.01.00 CONTENTS: A. Overview B. Supported versions C. Setting Up Oracle Data Guard D. Setting Up the Toolkit E. Oracle Data Guard Package Configuration Example F. Adding the Package to the Cluster G. Oracle Data Guard Maintenance H. Using Serviceguard Toolkit for Oracle Data Guard in Continentalclusters environment I.
PAGE 2
HP Serviceguard includes built in monitoring capabilities to monitor system resources like network, volume groups, filesystems etc and to initiate failover in the instant of their failure. - Oracle Data Guard integration with HP Serviceguard Extended Distance Cluster or other Serviceguard based "Disaster Recovery (DR)" clusters, will provide disaster protection and recovery for Oracle database as well as the applications that use the databases.
PAGE 3
VxVM/CVM and CFS will not be supported in this release. NOTE: This version of toolkit supports only modular packages. C. Setting Up Oracle Data Guard: Oracle Data Guard provides the management, monitoring, and automation software to create and maintain one or more standby databases to protect Oracle data from failures, disasters, human error, and data corruptions. Oracle Data Guard is included with the Enterprise Edition and Personal Edition of the Oracle database software.
PAGE 4
These scripts are: - hadg.conf (user configuration file) This script contains a list of pre-defined variables that the user must customize for use with a particular database instance. This is a configuration file which is read by the toolkit script, hadg.sh. The following variables are contained in hadg.conf: TKIT_DIR: and This directory is synonymous to the package directory holds the toolkit configuration file. This parameter directs "cmapplyconf" to generate the hadg.conf file under this directory.
PAGE 5
instance may be brought down for maintenance. The package would not be failed over to the adoptive node even though the instance has been brought down for maintenance. After the maintenance work, make sure that the instance is brought up properly. Delete the file dataguard.debug the package directory. This would enable toolkit to continue monitoring the Database server application.
PAGE 6
START_STANDBY_AS_PRIMARY: Specify whether the standby database has to be started as the primary database by failing over the primary database. This parameter can be used in a Continentalcluster environment; the value of this parameter has to be 'yes' in the package configuration file of the recovery package. ALERT_MAIL_ID: This parameter is used to specify the e-mail address for sending alerts. - Main Script (hadg.
PAGE 7
"Managing HP Serviceguard" to create the logical volume infrastructure on shared disks. The disk must be available to all clustered nodes that will be configured to run ODG toolkit. Create file systems on all logical volumes on the volume groups. The ODG toolkit can be configured in one of the following methods: a) Install directory method: Here the scripts remain in the installation directory.
PAGE 8
Oncce the package configuration file has been created, the user must specify various parameter values. The parameters which are to be modified in dgpkg.conf specifically for this configuration are only shown here. Note that the package configuration file shown below contains attributes of both the ECMT Oracle toolkit and the ODG tookit. (NOTE: The following attributes are specific to the Oracle Toolkit in ECMT.
PAGE 9
ebs ecmt/oracle/oracle/INSTANCE_TYPE database -----------------------------------------------------------------------# # Define Oracle home # ecmt/oracle/oracle/ORACLE_HOME /var/orahome -----------------------------------------------------------------------# # Define user name of Oracle database administrator # ecmt/oracle/oracle/ORACLE_ADMIN oracle -----------------------------------------------------------------------# # Define oracle session name # ecmt/oracle/oracle/SID_NAME ORCL -----------------------
PAGE 10
# # Define whether configured listener has to be started with the server # ecmt/oracle/oracle/LISTENER yes -----------------------------------------------------------------------# # Define the Oracle listener name(s) # ecmt/oracle/oracle/LISTENER_NAME LISTENER_ORCL -----------------------------------------------------------------------# # Define the listener password(s) # #ecmt/oracle/oracle/LISTENER_PASS -----------------------------------------------------------------------# #ecmt/oracle/oracle/LISTENER_R
PAGE 11
# Define ACTIVE_STANDBY # tkit/dataguard/dataguard/ACTIVE_STANDBY no -----------------------------------------------------------------------# # Define DG_BROKER # tkit/dataguard/dataguard/DG_BROKER no -----------------------------------------------------------------------# # Define START_STANDBY_AS_PRIMARY # tkit/dataguard/dataguard/START_STANDBY_AS_PRIMARY no -----------------------------------------------------------------------# # Define e-mail address for sending alerts # #tkit/dataguard/dataguard/ALERT
PAGE 12
There might be situations, when the Oracle Data guard database instances have to be taken down for maintenance purposes like changing configuration, without having the instance to migrate to standby node. The following procedure should be followed: The maintenance feature is enabled only when the configuration variable MAINTENANCE_FLAG is set to "yes" in the toolkit configuration file.
PAGE 13
6. Allow monitoring scripts to continue normally as shown below: $ rm -f /etc/cmcluster/pkg/dgpkg/dataguard.debug The message "Starting Oracle Data Guard monitoring again after maintenance" appears in the Serviceguard Package Control script log. 7. Enable the package failover $ cmmodpkg -e dgpkg Note: If a package failure occurs during maintenance operations, the package does not automatically fail over to an adoptive node. You must manually start the package on the adoptive node.
PAGE 14
When the primary cluster fails, run "cmrecovercl" command on the recovery cluster to bring up the recovery package. I. Using Serviceguard Toolkit for Oracle Data Guard in Metrocluster and Extended Distance Cluster environments: The Primary database can be configured inside a Metrocluster or an Extended Distance Cluster. The standby database can be configured outside the Metrocluster/Extended Distance Cluster as a standalone database or as part of a Serviceguard cluster.
PAGE 15
5 rows selected If the output of the query does not help, check the following list of possible issues. * The service name for the standby instance is not configured correctly in the tnsnames.ora file at the primary site. * The service name listed in the LOG_ARCHIVE_DEST_n parameter of the primary initialization parameter file is incorrect. * The LOG_ARCHIVE_DEST_STATE_n parameter specifying the state of the standby archiving destination has the value DEFER. * The listener.