Use of Serviceguard Extension for RAC Toolkit with Oracle RAC 10g Release 2 or later, March 2009

ManualsBrandsHP ManualsSoftwareHP Serviceguard Extension for RAC (SGeRAC)

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

Background...................................................................................................................................2

Coordinating the Oracle RAC/Serviceguard Extension for RAC stack...................................................2

Serviceguard/Serviceguard Extension for RAC multi-node packages and simple package dependencies....4

Why use multi-node packages/simple package dependencies for Oracle RAC integration..........................5

Serviceguard Extension for RAC Toolkit operation................................................................................6

Startup and shutdown of the combined Oracle RAC-SGeRAC stack .....................................................7

How Serviceguard Extension for RAC starts, stops and checks Oracle Clusterware.................................8

How Serviceguard Extension for RAC Toolkit starts, stops and checks the RAC database instance.............8

How Serviceguard Extension for RAC Toolkit interacts with storage management subsystems ...................9

Use Case 1: Oracle Clusterware storage and database storage in SLVM/CVM .................................9

Use Case 2: Oracle Clusterware storage and database storage in CFS ............................................9

How to create a Serviceguard Extension for RAC modular package...................................................10

How Serviceguard Extension for RAC Toolkit maintenance mode works..............................................10

Use Case 1: Performing maintenance with Oracle Clusterware......................................................10

Use Case 2: Performance maintenance with Oracle RAC database instance....................................11

Serviceguard Extension for RAC Toolkit internal file structure................................................................11

Conclusion..................................................................................................................................13

For more information.....................................................................................................................14

Use of Serviceguard Extension for RAC Toolkit

with Oracle RAC 10g Release 2 or later

March 2009

Summary of content (14 pages)

PAGE 1
Use of Serviceguard Extension for RAC Toolkit with Oracle RAC 10g Release 2 or later March 2009 Introduction ................................................................................................................................... 2 Background ................................................................................................................................... 2 Coordinating the Oracle RAC/Serviceguard Extension for RAC stack...................................................
PAGE 2
Introduction This document discusses how Serviceguard Extension for RAC Toolkit enables a new framework for the integration of Oracle 10g Release 2 (10.2.0.1) or later version of Real Application Clusters (Oracle RAC1) with HP Serviceguard Extension for Real Application Clusters A.11.17 or later (SGeRAC2). SGeRAC Toolkit leverages the multi-node package and simple package dependency features introduced by HP Serviceguard (SG) A.11.
PAGE 3
(on HP-UX 11i v3) or shared raw logical volumes managed by SGeRAC using SLVM.4 The responsibilities of Oracle Clusterware in this combined environment include: • Management of the database and associated resources (database instances, services, virtual IP addresses (VIPs), listeners, etc.) • Management of Oracle ASM instances, if configured All pieces of the combined stack must start up and shut down in the proper sequence and we need to be able to automate the startup and shutdown sequences, if desired.
PAGE 4
• This includes invocation of such commands from SGeRAC package control scripts or module scripts; hence SGeRAC packages can invoke commands to start up and shutdown Oracle Clusterware and/or RAC database instances. With these improvements, it became possible, using SGeRAC packages, to meet the sequencing requirements mentioned above for the startup and shutdown of Oracle Clusterware and RAC database instances with respect to the SGeRAC-managed storage used by these entities.
PAGE 5
• cmrunpkg will fail if the user attempts to start a package that has a dependency on another package that is not running. The package manager will not attempt to start a package if its dependencies are not met. If multiple packages are specified to cmrunpkg, they will be started in dependency order. If the AUTO_RUN attribute is set to YES, the package manager will start the packages automatically in dependency order.
PAGE 6
fit for our problem of coordinating Oracle RAC and SGeRAC. We configure Oracle Clusterware as one MNP and each RAC database as another MNP and we set up the database MNPs to depend on the Oracle Clusterware MNP. This is the core concept of SGeRAC. Both Oracle Clusterware and the RAC database are multi-instance applications well suited to being configured as MNPs. Further, the use of MNPs reduces the total package count and simplifies SGeRAC package configuration and administration.
PAGE 7
Figure 1. Resources managed by SGeRAC and Oracle Clusterware and their dependencies SG/SGeRAC object SGeRAC PM Services Oracle Clusterware object SGeRAC simple dependency Start Stop Monitor RAC DB instances MNP Oracle Clusterware dependency Optional SGeRAC MNP and dependency Optional Oracle Clusterware resource and dependency Start Stop Monitor Start Stop Check Node apps e.g.
PAGE 8
2. Next, SGeRAC package manager shuts down Oracle Clusterware via the Oracle Clusterware MNP, followed by the storage needed by Oracle Clusterware (this requires subsequent shutdown of mount point and disk group MNPs in the case of the storage needed by Oracle Clusterware being managed by CFS). It can do this since the dependent RAC database instance MNP is already down. Before shutting itself down, Oracle Clusterware shuts down the ASM instance if configured, and then the node applications. 3.
PAGE 9
placement error" occurs, indicating that CRS is not ready to start the instance, the function sleeps for 2 minutes and then retries. At most 3 attempts are made to start the instance. The stop function executes su to the Oracle software owner user id. It then determines the Oracle instance id on the current node for the specified database using srvctl status database. Then it stops the corresponding Oracle RAC instance using srvctl stop instance.
PAGE 10
Figure 3. Use Case 2 setup Oracle Clusterware MNP RAC DB instance MNP CFS mount point MNP for Oracle Clusterware CFS mount point MNP for RAC database CVM disk group MNP CVM disk group MNP CFS/CVM SMNP Similarly for each CFS used by the RAC database for database files, there will be a dependency configured from the RAC database MNP to the mount point MNP corresponding to that CFS.
PAGE 11
1. Make sure the MAINTENANCE_FLAG parameter for both the Oracle Clusterware MNP and the Oracle database instance MNPs are set to yes when these packages are created. If not, shutdown both MNPs first, set the MAINTENANCE_FLAG to yes on all nodes, then restart both MNPs. 2. On the maintenance node, create a debug file called oc.debug in the Oracle Clusterware MNP working directory. Both Oracle Clusterware MNP and the Oracle database instance MNP on this node will go into maintenance mode.
PAGE 12
Figure 4. Internal structure of SGeRAC for Oracle Clusterware Oracle Clusterware/RAC-specific configuration and logic SGeRAC-specific configuration and logic Oracle Clusterware MNP configuration file Oracle Clusterware Toolkit configuration file (oc.conf) sources Toolkit interface script (toolkit_oc.
PAGE 13
Figure 5. Internal structure of SGeRAC for RAC DB instance Oracle Clusterware/RAC-specific configuration and logic SGeRAC-specific configuration and logic RAC DB Instance MNP configuration file RAC DB instance MNP configuration file (rac_dbi.conf) sources Toolkit interface script (toolkit_dbi.sh) SGeRAC PM executes calls RAC DB Instance MNP control script (for legacy packages) RAC DB instance MNP module script (erac_tk_rac.
PAGE 14
For more information www.hp.com/go/serviceguardsolutions www.hp.com/go/sgerac © Copyright 2006-2009 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty.