Oracle Database Oracle Clusterware Installation Guide for HP-UX

Configuring Storage for Oracle Database Files on Shared Storage Devices
5-16 Oracle Clusterware Installation Guide
# chown oracle:dba /dev/rdsk/cxtydz
# chmod 660 /dev/rdsk/cxtydz
Note: If you are using a multi-pathing disk driver with ASM,
make sure that you set the permissions only on the correct logical
device name for the disk.
If the nodes are configured differently, the device name for a
particular device might be different on some nodes. Make sure that
you specify the correct device names on each node.
6. If you also want to use raw devices for storage, then refer to the following section,
"Configuring Disks for Database Files on Raw Devices" section on page 5-17.
5.6 Configuring Storage for Oracle Database Files on Shared Storage
Devices
The following subsections describe how to configure Oracle Clusterware files on raw
devices.
■ Planning Your Shared Storage Device Creation Strategy
■ Identifying Required Shared Partitions for Database Files
■ Desupport of the Database Configuration Assistant Raw Device Mapping File
5.6.1 Planning Your Shared Storage Device Creation Strategy
Before installing the Oracle Database 11g release 1 (11.1) software with Oracle RAC,
create enough partitions of specific sizes to support your database, and also leave a
few spare partitions of the same size for future expansion. For example, if you have
space on your shared disk array, then select a limited set of standard partition sizes for
your entire database. Partition sizes of 50 MB, 100 MB, 500 MB, and 1 GB are suitable
for most databases. Also, create a few very small and a few very large spare partitions
that are (for example) 1 MB and perhaps 5 GB or greater in size. Based on your plans
for using each partition, determine the placement of these spare partitions by
combining different sizes on one disk, or by segmenting each disk into same-sized
partitions.
Note: Be aware that each instance has its own redo log files, but
all instances in a cluster share the control files and data files. In
addition, each instance's online redo log files must be readable by
all other instances to enable recovery.
In addition to the minimum required number of partitions, you
should configure spare partitions. Doing this enables you to
perform emergency file relocations or additions if a tablespace data
file becomes full.
5.6.2 Identifying Required Shared Partitions for Database Files
Table 5–3 lists the number and size of the shared partitions that you must configure for
database files.