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 266
If your disks are mirrored with LVM mirroring on separate physical
paths and you want to override quorum, use the following setting:
VGCHANGE="vgchange -a s -q n”
Enter the names of the CVM disk groups you wish to activate in shared
mode in the CVM_DG[] array. Use a different array element for each RAC
disk group. (Remember that CVM disk groups must also be coded in the
package ASCII configuration file using STORAGE_GROUP parameters.) Be
sure to an appropriate type of shared activation with the CVM activation
command. For example:
CVM_ACTIVATION_CMD="vxdg -g \$DiskGroup set
activation=sharedwrite"
Do not define the RAC instance as a package service. Instead, include the
commands that start up an RAC instance in the
customer_defined_run_commands section of the package control script.
Similarly, you should include the commands that halt an RAC instance
in the customer_defined_halt_commands section of the package control
script.
Define the Oracle monitoring command as a service command, or else
use the special Oracle script provided with the ECM Toolkit.
Configuring an Oracle RAC Instance Package
To configure an Oracle RAC Instance Package, you can use either
Serviceguard Manager or the command line.
The Enterprise Cluster Master Toolkit (ECMT) provides a generic Oracle
database script template which can be used to configure package
behavior for an Oracle RAC Instance package. This script is integrated
by the user into the standard Serviceguard package control script, to
simplify the startup, monitoring, and shutdown of an Oracle database
instance. Refer to the ECMT documentation for details on the use of
ECMT.
Each Oracle RAC database can have a database instance running on all
nodes of a SGeRAC cluster. Therefore, it is not necessary to failover the
database instance to a different SGeRAC node. This is the main
difference between an Oracle RAC Instance Package and a single
instance Oracle package.