Go to main content

Oracle® Solaris Cluster Data Service for Oracle Real Application Clusters Guide

Exit Print View

Updated: April 2016
 
 

Using Hardware RAID Support

For information about the types of Oracle Database files that you can store by using hardware RAID support, see Storage Management Requirements.

How to Use Hardware RAID Support

  1. Create LUNs on the disk arrays.

    See the Oracle Solaris Cluster hardware documentation for information about how to create LUNs.

  2. After you create the LUNs, run the format (1M) command to partition the disk arrays' LUNs into as many slices as you need.
    # format

    Note -  To prevent a loss of disk partition information, do not start the partition at cylinder 0 for any disk slice that is used for raw data. The disk partition table is stored in cylinder 0 of the disk.
  3. Determine the raw device identity (DID) that corresponds to the LUNs that you created in Step 1.

    Use the cldevice (1CL) command for this purpose.

    The following example lists output from the cldevice list –v command.

    # cldevice list -v
    
    DID Device     Full Device Path
    ----------     ----------------
    d1             phys-schost-1:/dev/rdsk/c0t2d0
    d2             phys-schost-1:/dev/rdsk/c0t3d0
    d3             phys-schost-2:/dev/rdsk/c4t4d0
    d3             phys-schost-1:/dev/rdsk/c1t5d0
    d4             phys-schost-2:/dev/rdsk/c3t5d0
    d4             phys-schost-1:/dev/rdsk/c2t5d0
    d5             phys-schost-2:/dev/rdsk/c4t4d1
    d5             phys-schost-1:/dev/rdsk/c1t5d1
    d6             phys-schost-2:/dev/rdsk/c3t5d1
    d6             phys-schost-1:/dev/rdsk/c2t5d1
    d7             phys-schost-2:/dev/rdsk/c0t2d0
    d8             phys-schost-2:/dev/rdsk/c0t3d0

    In this example, the cldevice output identifies that the raw DID that corresponds to the disk arrays' shared LUNs is d4.

  4. Obtain the full DID device name that corresponds to the DID device that you identified in Step 3.

    The following example shows the output from the cldevice show for the DID device that was identified in the example in Step 3. The command is run from node phys-schost-1.

    # cldevice show d4
    
    === DID Device Instances ===
    
    DID Device Name:                                /dev/did/rdsk/d4
    Full Device Path:                                phys-schost-1:/dev/rdsk/c2t5d0
    Replication:                                     none
    default_fencing:                                 global
  5. If you are using a zone cluster configure the DID devices into the zone cluster. Otherwise, proceed to the next step.

    For information about configuring DID devices into a zone cluster, see How to Add a Global Storage Device to a Zone Cluster (clsetup) in Oracle Solaris Cluster 4.3 Software Installation Guide or How to Add a DID Device to a Zone Cluster (CLI) in Oracle Solaris Cluster 4.3 Software Installation Guide .

  6. Create or modify a slice on each DID device to contain the disk-space allocation for the raw device.

    Use the format (1M) command, fmthard (1M) command, or prtvtoc (1M) for this purpose. Specify the full device path from the cluster node where you are running the command to create or modify the slice.

    For example, if you choose to use slice s0, you might choose to allocate 100 GB of disk space in slice s0.

  7. Change the ownership and permissions of the raw devices that you are using to allow access to these devices.

    To specify the raw device, append sN to the DID device name that you obtained in Step 4, where N is the slice number.

    For example, the cldevice output in Step 4 identifies that the raw DID that corresponds to the disk is /dev/did/rdsk/d4. If you choose to use slice s0 on these devices, specify the raw device /dev/did/rdsk/d4s0.

Next Steps

Ensure that all other storage management schemes that you are using for Oracle Database files are installed. After all storage management schemes that you are using for Oracle Database files are installed, go to Chapter 3, Registering and Configuring the Resource Groups.