Using Serviceguard Extension for RAC, 2nd Edition, February 2005 Update
Table Of Contents
- Using Serviceguard Extension for RAC
- 1 Introduction to Serviceguard Extension for RAC
- 2 Serviceguard Configuration for Oracle RAC
- Planning Database Storage
- Installing Serviceguard Extension for RAC
- Configuration File Parameters
- Creating a Storage Infrastructure with LVM
- Building Volume Groups for RAC on Mirrored Disks
- Building Mirrored Logical Volumes for RAC with LVM Commands
- Creating RAC Volume Groups on Disk Arrays
- Creating Logical Volumes for RAC on Disk Arrays
- Oracle Demo Database Files
- Displaying the Logical Volume Infrastructure
- Exporting the Logical Volume Infrastructure
- Installing Oracle Real Application Clusters
- Cluster Configuration ASCII File
- Creating a Storage Infrastructure with CVM
- Initializing the VERITAS Volume Manager
- Preparing the Cluster for Use with CVM
- Starting the Cluster and Identifying the Master Node
- Converting Disks from LVM to CVM
- Initializing Disks for CVM
- Creating Disk Groups for RAC
- Creating Volumes
- Oracle Demo Database Files
- Adding Disk Groups to the Cluster Configuration
- Using Packages to Configure Startup and Shutdown of RAC Instances
- Starting Oracle Instances
- Creating Packages to Launch Oracle RAC Instances
- Configuring Packages that Access the Oracle RAC Database
- running cluster:adding or removing packages
- Writing the Package Control Script
- Using Serviceguard Manager to Write the Package Control Script
- Using Commands to Write the Package Control Script
- Customizing the Package Control Script
- Optimizing for Large Numbers of Storage Units
- Customizing the Control Script for RAC Instances
- Configuring an Oracle RAC Instance Package
- Using Serviceguard Manager to a Configure Oracle RAC Instance Package
- Enabling DB Provider Monitoring
- 3 Maintenance and Troubleshooting
- Reviewing Cluster and Package States with the
- Managing the Shared Storage
- Removing ServiceGuard Extension for RAC from a System
- Monitoring Hardware
- Adding Disk Hardware
- Replacing Disks
- Replacement of I/O Cards
- Replacement of LAN Cards
- Monitoring RAC Instances
- A Blank Planning Worksheets
Serviceguard Configuration for Oracle RAC
Using Packages to Configure Startup and Shutdown of RAC Instances
Chapter 2 61
1. Shut down the Oracle applications, if any.
2. Shut down Oracle.
3. Deactivate the database volume groups or disk groups.
4. Shut down the cluster (cmhaltnode or cmhaltcl).
If the shutdown sequence described above is not followed, cmhaltcl or
cmhaltnode may fail with a message that GMS clients (RAC 9i) are
active or that shared volume groups are active.
Creating Packages to Launch Oracle RAC Instances
To coordinate the startup and shutdown of RAC instances with cluster
node startup and shutdown, you create a one-node package for each node
that runs an RAC instance. In the package configuration file, you should
specify only the single node on which the instance will run and specify
the control script that is to be executed every time the instance node or
the entire RAC cluster starts up or shuts down.
NOTE You must create the RAC instance package with a PACKAGE_TYPE of
FAILOVER, but the fact that you are entering only one node ensures that
the instance will only run on that node.
To simplify the creation of RAC instance packages, you can use the
Oracle template provided with the separately purchasable ECM Toolkits
product (B5139BA). This file is found in /opt/cmcluster/tookit/DB/Oracle.
Use the special oracle.sh script that is provided, and follow the
instructions that appear in the README file. Also refer to the section
“Customizing the Control Script for RAC Instances,” below.
To create the package with Serviceguard Manager select the cluster.
From the actions menu, choose configure package. To modify a package,
select the package. For an instance package, create one package for each
instance. On each node, supply the SID name for the package name.
To create a package on the command line, use the cmgetconf command
to get an editible configuration file.
Set the AUTO_RUN parameter to YES, if you want the instance to start up
as soon as the node joins the cluster. In addition, you should set the
NODE_FAILFAST_ENABLED parameter to NO.