The files needed by the Oracle database must be placed on
physical volumes that are accessible to all RAC cluster nodes. This
section shows how to plan the volumes using either SLVM or VERITAS
CVM storage groups.
Volume
Planning with CVM |
 |
Storage capacity for the Oracle database must be provided
in the form of volumes located in shared disk groups. The Oracle
software requires at least two log files (an one undo tablespace
for Oracle9) for each Oracle instance, several Oracle control files
and data files for the database itself. For all these files, Serviceguard
Extension for RAC uses HP-UX raw volumes, which
are located in disk groups that are shared between the nodes in
the cluster. High availability is achieved by using high availability
disk arrays in RAID nodes. The logical units of storage on the arrays
are accessed from each node through multiple physical volume links
via DMP (Dynamic Multi-pathing), which provides redundant paths
to each unit of storage.
Fill out the VERITAS Volume worksheet to provide volume names
for volumes that you will create using the VERITAS utilities. The
Oracle DBA and the HP-UX system administrator should prepare this worksheet
together. Create entries for shared volumes only. For each volume,
enter the full pathname of the raw volume device file. Be sure to include
the desired size in MB. Following is a sample worksheet filled out.
Refer to Appendix A “Blank
Planning Worksheets” for
samples of blank worksheets. Make as many copies as you need. Fill
out the worksheet and keep it for future reference.
|
ORACLE LOGICAL VOLUME WORKSHEET FOR CVM Page ___ of ____
===============================================================================
RAW LOGICAL VOLUME NAME SIZE (MB)
Oracle Control File 1: ___/dev/vx/rdsk/ops_dg/opsctl1.ctl______100______
Oracle Control File 2: ___/dev/vx/rdsk/ops_dg/opsctl2.ctl______100______
Oracle Control File 3: ___/dev/vx/rdsk/ops_dg/opsctl3.ctl______100______
Instance 1 Redo Log 1: ___/dev/vx/rdsk/ops_dg/ops1log1.log_____20______
Instance 1 Redo Log 2: ___/dev/vx/rdsk/ops_dg/ops1log2.log_____20_______
Instance 1 Redo Log 3: ___/dev/vx/rdsk/ops_dg/ops1log3.log_____20_______
Instance 1 Redo Log: ___________________________________________________
Instance 1 Redo Log: ___________________________________________________
Instance 2 Redo Log 1: ___/dev/vx/rdsk/ops_dg/ops2log1.log____20________
Instance 2 Redo Log 2: ___/dev/vx/rdsk/ops_dg/ops2log2.log____20________
Instance 2 Redo Log 3: ___/dev/vx/rdsk/ops_dg/ops2log3.log____20_________
Instance 2 Redo Log: _________________________________________________
Instance 2 Redo Log: __________________________________________________
Data: System ___/dev/vx/rdsk/ops_dg/system.dbf___400__________
Data: Temp ___/dev/vx/rdsk/ops_dg/temp.dbf______100_______
Data: Users ___/dev/vx/rdsk/ops_dg/users.dbf_____120_________
Data: Tools ___/dev/vx/rdsk/ops_dg/tools.dbf____15___________
Data: User data ___/dev/vx/rdsk/ops_dg/data1.dbf_200__________
Data: User data ___/dev/vx/rdsk/ops_dg/data2.dbf__200__________
Data: User data ___/dev/vx/rdsk/ops_dg/data3.dbf__200__________
Data: Rollback ___/dev/vx/rdsk/ops_dg/rollback.dbf__300_________(Oracle8) |
|
|
parameter: spfile1 /dev/vx/rdsk/ops_dg/spfile1.ora __5_____(Oracle9)
Instance 1 undotbs1: /dev/vx/rdsk/ops_dg/undotbs1.dbf___312___(Oracle9)
Instance 2 undotbs2: /dev/vx/rdsk/ops_dg/undotbs2.dbf___312___(Oracle9)
Data: example1__/dev/vx/rdsk/ops_dg/example1.dbf__________160____(Oracle9)
data: cwmlite1__/dev/vx/rdsk/ops_dg/cwmlite1.dbf__100____(Oracle9)
Data: indx1__/dev/vx/rdsk/ops_dg/indx1.dbf____70___(Oracle9)
Data: drsys1__/dev/vx/rdsk/ops_dg/drsys1.dbf___90___(Oracle9) |
Printable version
