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 63
Using Serviceguard Manager to Write the Package Control
Script
As you complete the tabs for the configuration, the control script can be
generated automatically. When asked to supply the the pathname of the
package run and halt scripts, use the filenames from the ECM toolkit.
For more information, use the Help key.
When you create a package control script this way, you do not need to do
any further editing, but you may customize the script if you wish.
Using Commands to Write the Package Control Script
Each package must have a separate control script, which must be
executable. The control script is placed in the package directory and is
given the same name as specified in the RUN_SCRIPT and HALT_SCRIPT
parameters in the package ASCII configuration file. The package control
script template contains both the run instructions and the halt
instructions for the package. You can use a single script for both run and
halt operations, or, if you wish, you can create separate scripts.
Use the following procedure to create a control scripts for the sample
package pkg1.
First, generate a control script template:
# cmmakepkg -s /etc/cmcluster/pkg1/control.sh
You may customize the script, as described in the section, “Customizing
the Package Control Script.”
Customizing the Package Control Script
Check the definitions and declarations at the beginning of the control
script using the information in the Package Configuration worksheet.
You need to customize as follows:
• Update the PATH statement to reflect any required paths needed to
start your services.
• If you are using LVM, enter the names of volume groups to be
activated using the VG[] array parameters, and select the
appropriate options for the storage activation command, including
options for mounting and unmounting filesystems, if desired. Do not
use the VXVM_DG[] or CVM_DG[] parameters for LVM volume groups.