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 3 75
DAALL_DB 0 10396 comanche
1 10501 chinook
IGOPALL 2 10423 comanche
1 10528 chinook
where the cmviewcl output values are:
GROUP the name of a configured group
MEMBER the ID number of a member of a group
PID the Process ID of the group member
MEMBER_NODE the Node on which the group member is running
Service Status
Services have only status, as follows:
• Up. The service is being monitored.
• Down. The service is not running. It may have halted or failed.
• Uninitialized. The service is included in the package
configuration, but it was not started with a run command in the
control script.
• Unknown.
Network Status
The network interfaces have only status, as follows:
• Up.
• Down.
• Unknown. We cannot determine whether the interface is up or down.
This can happen when the cluster is down. A standby interface has
this status.
Serial Line Status
The serial line has only status, as follows:
• Up. Heartbeats are received over the serial line.
• Down. Heartbeat has not been received over the serial line within 2
times the NODE_TIMEOUT value.