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
Maintenance and Troubleshooting
Reviewing Cluster and Package States with the cmviewcl Command
Chapter 376
• Recovering. A corrupt message was received on the serial line, and
the line is in the process of resynchronizing.
• Unknown. We cannot determine whether the serial line is up or down.
This can happen when the remote node is down.
Failover and Failback Policies
Packages can be configured with one of two values for the
FAILOVER_POLICY parameter:
• CONFIGURED_NODE. The package fails over to the next node in the
node list in the package configuration file.
• MIN_PACKAGE_NODE. The package fails over to the node in the cluster
with the fewest running packages on it.
Packages can also be configured with one of two values for the
FAILBACK_POLICY parameter:
• AUTOMATIC. With this setting, a package, following a failover, returns
to its primary node when the primary node becomes available again.
• MANUAL. With this setting, a package, following a failover, must be
moved back to its original node by a system administrator.
Failover and failback policies are displayed in the output of the cmviewcl
-v command.
Examples of Cluster and Package States
The following sample output from the cmviewcl -v command shows
status for the cluster in the sample configuration.
Normal Running Status
Everything is running normally; both nodes in a two-node cluster are
running, and each Oracle RAC instance package is running as well. The
only packages running are Oracle RAC instance packages.
CLUSTER STATUS
example up
NODE STATUS STATE
ftsys9 up running
Network_Parameters:
INTERFACE STATUS PATH NAME