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
Monitoring Hardware
Chapter 390
Monitoring Hardware
Good standard practice in handling a high availability system includes
careful fault monitoring so as to prevent failures if possible or at least to
react to them swiftly when they occur. The following should be monitored
for errors or warnings of all kinds:
•Disks
•CPUs
• Memory
• LAN cards
• Power sources
• All cables
• Disk interface cards
Some monitoring can be done through simple physical inspection, but for
the most comprehensive monitoring, you should examine the system log
file (/var/adm/syslog/syslog.log) periodically for reports on all
configured HA devices. The presence of errors relating to a device will
show the need for maintenance.
Using Event Monitoring Service
Event Monitoring Service (EMS) allows you to configure monitors of
specific devices and system resources. You can direct alerts to an
administrative workstation where operators can be notified of further
action in case of a problem. For example, you could configure a disk
monitor to report when a mirror was lost from a mirrored volume group
being used in a non-RAC package. Refer to the manual Using the Event
Monitoring Service (B7612-90009) for additional information.
Using EMS Hardware Monitors
A set of hardware monitors is available for monitoring and reporting on
memory, CPU, and many other system values. Refer to the EMS
Hardware Monitors User’s Guide (B6191-90020) for additional
information.