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 262
If you are using CVM disk groups for the RAC database, be sure to
include the name of each disk group on a separate STORAGE_GROUP line in
the configuration file.
Configuring Packages that Access the Oracle RAC
Database
You can also use packages to start up applications that access the RAC
instances. If an application is intended to fail over among cluster nodes,
then you must set it up as a distinct package, separate from the package
that starts and stops the RAC instance. Use the following procedures for
packages that contain applications which access the RAC database:
1. In the ASCII package configuration file, set the AUTO_RUN parameter
to NO, or if you are using Serviceguard Manager to configure
packages, set Automatic Switching to Disabled. This keeps the
package from starting up immediately when the node joins the
cluster, and before RAC is running.
2. You can then manually start the package using the cmmodpkg -e
packagename command after RAC is started. Alternatively, you can
choose to automate the process of package activation by writing your
own script, and copying it to all nodes that can run the package. This
script should contain the cmmodpkg -e command and activate the
package after RAC and the cluster manager have started.
Adding or Removing Packages on a Running Cluster
You can add or remove packages while the cluster is running, subject to
the limit of MAX_CONFIGURED_PACKAGES. To add or remove packages
online, refer to the chapter on “Cluster and Package Maintenance.”
Writing the Package Control Script
The package control script contains all the information necessary to run
all the services in the package, monitor them during operation, react to a
failure, and halt the package when necessary. You can use either
Serviceguard Manager or HP-UX commands to create or modify the
package control script. For security reasons, the control script must
reside in a directory with the string cmcluster in the path.