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
Creating a Storage Infrastructure with LVM
Chapter 246
*
The size of the logical volume is larger than the Oracle file size because
Oracle needs extra space to allocate a header in addition to the file's
actual data capacity.
Create these files if you wish to build the demo database. The three
logical volumes at the bottom of the table are included as additional data
files, which you can create as needed, supplying the appropriate sizes. If
your naming conventions require, you can include the Oracle SID and/or
the database name to distinguish files for different instances and
different databases. If you are using the ORACLE_BASE directory
structure, create symbolic links to the ORACLE_BASE files from the
appropriate directory. Example:
# ln -s /dev/vg_ops/ropsctl1.ctl
/u01/ORACLE/db001/ctrl01_1.ctl
For more information about Oracle directories, refer to the Oracle Server
for HP 9000 Installation and Configuration Guide. More information
about the maximum sizes of data files is found in the Oracle 8i Reference
(Oracle Part Number A76961-01), Chapter 4, “Database Limits.”
After creating these files, set the owner to oracle and the group to dba
with a file mode of 660. The logical volumes are now available on the
primary node, and the raw logical volume names can now be used by the
Oracle DBA.
Displaying the Logical Volume Infrastructure
To display the volume group, use the vgdisplay command:
# vgdisplay -v /dev/vg_ops
ops3log3 28 /dev/vg_ops/rops2log3.log 20
opsdata1 208 /dev/vg_ops/ropsdata1.dbf 200
opsdata2 208 /dev/vg_ops/ropsdata2.dbf 200
opsdata3 208 /dev/vg_ops/ropsdata3.dbf 200
Table 2-1 Required Oracle File Names for Demo Database (Continued)
Logical Volume Name
LV
Size
(MB) Raw Logical Volume Path Name
Oracle
File
Size
(MB)*