For information about the types of Oracle files that you can store by using ASM, see Storage Management Requirements for Oracle Files.
Use ASM with one storage management scheme from the following list:
Hardware RAID. For more information, see How to Use ASM With Hardware RAID.
Solaris Volume Manager for Sun Cluster. For more information, see How to Create a Multi-Owner Disk Set in Solaris Volume Manager for Sun Cluster for the Oracle RAC Database.
VxVM. For more information, see How to Create a VxVM Shared-Disk Group for the Oracle RAC Database.
This procedure provides the long forms of the Sun Cluster maintenance commands. Most commands also have short forms. Except for the forms of the command names, the commands are identical. For a list of the commands and their short forms, see Appendix A, Sun Cluster Object-Oriented Commands, in Sun Cluster Data Services Planning and Administration Guide for Solaris OS.
On a cluster member, log in as root or become superuser.
Determine the identities of device identity (DID) devices that correspond to shared disks that are available in the cluster.
Use the cldevice(1CL) command for this purpose.
The following example shows an extract from output from the cldevice list -v command.
# cldevice list -v DID Device Full Device Path ---------- ---------------- … d5 phys-schost-3:/dev/rdsk/c3t216000C0FF084E77d0 d5 phys-schost-1:/dev/rdsk/c5t216000C0FF084E77d0 d5 phys-schost-2:/dev/rdsk/c4t216000C0FF084E77d0 d5 phys-schost-4:/dev/rdsk/c2t216000C0FF084E77d0 d6 phys-schost-3:/dev/rdsk/c4t216000C0FF284E44d0 d6 phys-schost-1:/dev/rdsk/c6t216000C0FF284E44d0 d6 phys-schost-2:/dev/rdsk/c5t216000C0FF284E44d0 d6 phys-schost-4:/dev/rdsk/c3t216000C0FF284E44d0 …
In this example, DID devices d5 and d6 correspond to shared disks that are available in the cluster.
Obtain the full DID device name for each DID device that you are using for the ASM disk group.
The following example shows the output from the cldevice show for the DID devices that were identified in the example in Step 2. The command is run from node phys-schost-1.
# cldevice show d5 d6 === DID Device Instances === DID Device Name: /dev/did/rdsk/d5 Full Device Path: phys-schost-1:/dev/rdsk/c5t216000C0FF084E77d0 Replication: none default_fencing: global DID Device Name: /dev/did/rdsk/d6 Full Device Path: phys-schost-1:/dev/rdsk/c6t216000C0FF284E44d0 Replication: none default_fencing: global
Create or modify a slice on each DID device to contain the disk-space allocation for the ASM disk group.
For example, if you choose to use slice s0 for the ASM disk group, you might choose to allocate 100 Gbytes of disk space in slice s0.
Change the ownership and permissions of the raw devices that you are using for ASM to allow access by ASM to these devices.
To specify the raw device, append sN to the DID device name that you obtained in Step 3, where N is the slice number.
For example, the cldevice output in Step 3 identifies that the raw DIDs that correspond to the disk are /dev/did/rdsk/d5 and /dev/did/rdsk/d6. If you choose to use slice s0 on these devices, specify the raw devices /dev/did/rdsk/d5s0 and /dev/did/rdsk/d6s0.
For more information about changing the ownership and permissions of raw devices for use by ASM, see your Oracle documentation.
For example, to use the /dev/did/ path for the ASM disk group, add the value /dev/did/rdsk/d* to the ASM_DISKSTRING parameter. If you are modifying this parameter by editing the Oracle initialization parameter file, edit the parameter as follows:
ASM_DISKSTRING = '/dev/did/rdsk/*'
For more information, see your Oracle documentation.
Ensure that all other storage management schemes that you are using for Oracle files are installed.
After all storage management schemes that you are using for Oracle files are installed, go to Registering and Configuring the RAC Framework Resource Group.