Configuring HP Serviceguard Toolkit for Oracle Data Guard

ManualsBrandsHP ManualsSoftwareHP Serviceguard Toolkit for Oracle Data Guard

Configuring HP Serviceguard Toolkit for

Oracle Data Guard

Technical white paper

Table of contents

Introduction ......................................................................................................................................... 2

Terms and definitions ........................................................................................................................... 2

Oracle Data Guard overview ................................................................................................................ 2

Physical and logical standby databases .............................................................................................. 2

Active Data Guard ........................................................................................................................... 3

Data Guard Broker ........................................................................................................................... 3

Role transitions ................................................................................................................................ 3

Serviceguard support for Oracle Data Guard .......................................................................................... 3

Dependencies .................................................................................................................................. 4

Supported configurations .................................................................................................................. 4

Continentalclusters environment ......................................................................................................... 6

Metrocluster and EDC configurations .................................................................................................. 8

Metrocluster in Continentalclusters environment .................................................................................. 10

Supporting multiple instances of single-instance ODG configuration ..................................................... 11

HA for Data Guard Broker .............................................................................................................. 11

Installation and configuration of the toolkit ............................................................................................ 12

Setting up the application ............................................................................................................... 12

Setting up the toolkit ....................................................................................................................... 12

ODG package configuration example .............................................................................................. 14

Adding the package to the cluster .................................................................................................... 19

ODG maintenance ......................................................................................................................... 19

Troubleshooting ................................................................................................................................. 20

Known problems and workarounds ...................................................................................................... 21

For more information .......................................................................................................................... 22

Appendix A ...................................................................................................................................... 22

Configuring ODG example ............................................................................................................. 22

Preparing the primary database ....................................................................................................... 22

Creating a physical standby database .............................................................................................. 23

Summary of content (26 pages)

PAGE 1
Configuring HP Serviceguard Toolkit for Oracle Data Guard Technical white paper Table of contents Introduction ......................................................................................................................................... 2 Terms and definitions ........................................................................................................................... 2 Oracle Data Guard overview .....................................................................................
PAGE 2
Introduction This document describes how the HP Serviceguard Toolkit for Oracle Data Guard assists in easy integration of Oracle Data Guard (ODG) with HP Serviceguard. ODG is the host-based datareplication software for Oracle Database. It provides management, monitoring, and automation features to create and maintain one or more standby databases to protect data from failures, disasters, human error, and data corruptions.
PAGE 3
The standby databases in a Data Guard configuration can be a combination of physical and logical standby databases. Active Data Guard Active Data Guard is a new feature for Oracle 11g. Oracle Active Data Guard enhances the quality of service by offloading resource-intensive activities from a production database to one or more synchronized standby databases.
PAGE 4
Serviceguard has extensive dependencies that allow these application interdependencies to be built in for a complete environment/deployment. This is advantageous from the complete application stack, as opposed to accounting for the Oracle Database alone. 3. Serviceguard’s robust failover mechanism can be extended to provide reliable automatic Data Guard role management (failover and switchover) operations. 4. Serviceguard is integrated with Insight Dynamics—VSE for Integrity Servers.
PAGE 5
As a combinational package, the Oracle database will be brought up first using the ECMT Oracle Toolkit; then the Data Guard processes will be started by the ODG Toolkit; then the application is monitored. Since the Oracle database and the Data Guard are packaged together, the package will failover if either the Oracle database or any of the Data Guard processes fail.
PAGE 6
Continentalclusters environment Figure 2: ODG Toolkit in a Continentalclusters environment Continentalcluster SG Cluster 2 (Recovery Cluster) SG Cluster 1 ( Primary Cluster) Recovery group Primary package Data Receiver package Recovery package Node 2 Node 1 Primary DB Node 1 Node 2 Standby DB Figure 2 depicts a typical Continentalclusters environment, which consists of a Primary Cluster (SG Cluster 1) and a Recovery Cluster (SG Cluster 2).
PAGE 7
Initially, the Primary package and the Data Receiver package will be up and running and the Recovery package will be in halted state. The Primary package will bring up the Oracle database on the Primary Cluster in Primary mode and the Data Receiver package will bring up the Oracle database on the Recover Cluster in Standby mode. Thus, a typical Data Guard environment is set up with data replication done from the primary database on the Primary Cluster to the standby database on the Recovery Cluster.
PAGE 8
Metrocluster and EDC configurations Metrocluster is an HP high availability product for Serviceguard customers who require integrated disaster recovery solutions. HP Metrocluster uses Serviceguard clustering technology to form a single cluster of systems that are located apart from each other at different data centers at metropolitan distances.
PAGE 9
In Figure 3, Metrocluster is configured with two data centers: one as the primary site and the other as the recovery site. The Data Guard primary database instance is configured in Data Center 1 such that the archived logs and the primary database reside on the disk that is shared locally between the nodes in that data center. The primary database instance will be brought up on any one node in Data Center 1 while other nodes in the data center will serve as backup nodes for that instance.
PAGE 10
Figure 4 shows a Data Guard setup in an EDC environment. Both the primary and standby databases are configured as single instance Serviceguard failover packages inside the EDC. All the four nodes are present inside the same Serviceguard cluster. Failover from Site A to Site B and vice versa is not allowed. When Site A goes down, the role of Standby on Site B has to be manually changed to primary, since the role transitions will not be supported in the first release.
PAGE 11
The standby database is configured as a Data Receiver package in the Recovery Cluster. It will receive the archived redo logs sent by the primary database instance irrespective of the node on which the primary database is running. Cross subnet failover is allowed across the sites. When the Primary Cluster fails, the user must run the “cmrecovercl” command to halt the Data Receiver package and start the Recovery package.
PAGE 12
Installation and configuration of the toolkit Setting up the application ODG is included with the Enterprise Edition and Standard Edition of the Oracle database software. Oracle must be installed on all the nodes of the cluster, by the user “oracle” and shared storage has to be configured. For information on configuring ODG, please refer to Appendix A.
PAGE 13
brought up properly. Delete the file “dataguard.debug” from the package directory. This will enable the toolkit to continue monitoring the database server application. NOTE: If the maintenance flag is set to “no,” then the above feature will not be available and the toolkit cannot be brought into maintenance mode. MONITOR_INTERVAL: The time interval, in seconds, this script will wait between checks to make sure that the Oracle instance is running. The default value is 30 seconds.
PAGE 14
ODG package configuration example This section explains an ODG package configuration example. Follow the instructions in the chapter “Building an HA Cluster Configuration” in the manual “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 the ODG Toolkit. Create file systems on all logical volumes on the volume groups.
PAGE 15
package_name dgpkg -----------------------------------------------------------------------# # “package_description” specifies the application that the package runs. # package_description “Serviceguard Package” -----------------------------------------------------------------------# # “package_type” is the type of package. # The package_type attribute specifies the behavior for this package.
PAGE 16
# 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 -----------------------------------------------------------------------# # Define Oracle database startup mode # ecmt/oracle/oracle/START_MODE mount ------
PAGE 17
# #ecmt/oracle/oracle/ASM_HOME -----------------------------------------------------------------------# # Define user name of Oracle ASM administrator # ecmt/oracle/oracle/ASM_USER oracle ---------------------------------------------------------------------# # The ASM session name # #ecmt/oracle/oracle/ASM_SID -----------------------------------------------------------------------------# # Define whether the configured listener has to be started with the server # ecmt/oracle/oracle/LISTENER yes --------
PAGE 18
service_restart none service_fail_fast_enabled service_halt_timeout no 300 service_name service_cmd oracle_listener_service_test “$SGCONF/scripts/ecmt/oracle/tkit_module.sh oracle_monitor_listener” service_restart none service_fail_fast_enabled service_halt_timeout no 300 service_name service_cmd oracle_hang_service_test “$SGCONF/scripts/ecmt/oracle/tkit_module.
PAGE 19
# Define email address for sending alerts # #tkit/dataguard/dataguard/ALERT_MAIL_ID -----------------------------------------------------------------------# # “vg” is used to specify which volume groups are used by this package. # vg vgora -----------------------------------------------------------------------# # “fs_name,” “fs_directory,” “fs_mount_opt,” “fs_umount_opt,” “fs_fsck_opt,” # and “fs_type” specify the filesystems that are used by this package.
PAGE 20
Note: The example assumes that the package name is dgpkg, package directory is /etc/cmcluster/pkg/dgpkg, and the ORACLE_HOME is configured as /orahome. 1. Disable the failover of the package through cmmodpkg command. $ cmmodpkg -d dgpkg 2. Pause the monitor script. Create an empty file /etc/cmcluster/pkg/dgpkg/dataguard.debug as shown below: $ touch /etc/cmcluster/pkg/dgpkg/dataguard.
PAGE 21
For example, enter: SQL> SELECT dest_id “ID” 2> status “DB_status” 3> destination “Archive_dest” 4> error “Error” 5> FROM v$archive_dest; ID DB_status Archive_dest Error -- --------- ------------------------------------------------------------------1 VALID /vobs/oracle/work/arc_dest/arc 2 ERROR standby1 ORA-16012: Archivelog standby database identifier mismatch 3 INACTIVE 4 INACTIVE 5 INACTIVE 5 rows selected If the output of the query does not help, check the following list of possible issues.
PAGE 22
2. In case of a Metrocluster environment where only the primary database is configured within the Metrocluster and the standby database is configured on a third site that is not part of the Metrocluster, the data replication can happen only from the site where the primary is running. Even if the proximity of the other site is better, data replication cannot happen from that site. This is a restriction put by Data Guard, and not the ODG Toolkit. 3.
PAGE 23
following SQL statement: SQL> ALTER DATABASE FORCE LOGGING; 2. Create a password file: Create a password file if one does not already exist. Every database in a Data Guard configuration must use a password file, and the password for the SYS user must be identical on every system for redo data transmission to succeed. 3.
PAGE 24
b. Configure listeners for the primary and standby databases. On both the primary and standby sites, use Oracle Net Manager to configure a listener for the respective databases. To restart the listeners (to pick up the new definitions), enter the following LSNRCTL utility commands on both the primary and standby systems: % lsnrctl stop % lsnrctl start Ensure that the tnsnames.ora of a node contains the entries of all those nodes that it wants to communicate with. c.
PAGE 25
For each table space identified in the previous query, add a new temporary file to the standby database. The following example adds a new temporary file called TEMP1 with size and reuse characteristics that match the primary database temporary files: SQL> ALTER TABLESPACE TEMP1 ADD TEMPFILE 2> “/arch1/standby/temp01.dbf” 3> SIZE 40M REUSE; c. Start Redo Apply.
PAGE 26
Further preparations At this point, the physical standby database is running and can provide the maximum performance level of data protection. The following list describes additional preparations you can take on the physical standby database: 1. Upgrade the data protection mode: The Data Guard configuration is initially set up in the maximum performance mode (the default). This can be change to either maximum protection mode or maximum availability mode. 2.