Installing Storage Management Software With Sun Cluster Support for Oracle Real Application Clusters
Install the software for the storage management schemes that you are using for Oracle files. For more information, see Storage Management Requirements for Oracle Files.
Note –
For information about how to install and configure Network Appliance NAS devices with Sun Cluster Support for Oracle Real Application Clusters, see Sun Cluster 3.1 With Network-Attached Storage Devices Manual for Solaris OS.
How to Use Solaris Volume Manager for Sun Cluster
To use the Solaris Volume Manager for Sun Cluster software with Sun Cluster Support for Oracle Real Application Clusters, perform the following tasks.
Steps
-
Ensure that you are using Solaris 9 9/04, Solaris 10, or compatible versions.
Solaris Volume Manager for Sun Cluster is installed during the installation of the Solaris Operating System.
-
Configure the Solaris Volume Manager for Sun Cluster software on the cluster nodes.
For more information, see Installing and Configuring Solstice DiskSuite or Solaris Volume Manager Software in Sun Cluster Software Installation Guide for Solaris OS.
Next Steps
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 Preparing the Sun Cluster Nodes.
SPARC: How to Use VxVM
To use the VxVM software with Sun Cluster Support for Oracle Real Application Clusters, perform the following tasks.
Steps
-
If you are using VxVM with the cluster feature, obtain a license for the Volume Manager cluster feature in addition to the basic VxVM license.
See your VxVM documentation for more information about VxVM licensing requirements.
Caution – Failure to correctly install the license for the Volume Manager cluster feature might cause a panic when you install Oracle Real Application Clusters support. Before you install the Oracle Real Application Clusters packages, run the vxlicense -p or vxlicrep command to ensure that you have installed a valid license for the Volume Manager cluster feature.
-
Install and configure the VxVM software on the cluster nodes.
See Chapter 4, Installing and Configuring VERITAS Volume Manager, in Sun Cluster Software Installation Guide for Solaris OS and the VxVM documentation for more information.
Next Steps
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 Preparing the Sun Cluster Nodes.
How to Use Hardware RAID Support
You can use Sun Cluster Support for Oracle Real Application Clusters with hardware RAID support.
For example, you can use Sun StorEdgeTM A3500/A3500FC disk arrays with hardware RAID support and without VxVM software. To use this combination, configure raw device identities (/dev/did/rdsk*) on top of the disk arrays' logical unit numbers (LUNs). To set up the raw devices for Oracle Real Application Clusters on a cluster that uses StorEdge A3500/A3500FC disk arrays with hardware RAID, perform the following steps.
Steps
-
Create LUNs on the disk arrays.
See the Sun Cluster hardware documentation for information about how to create LUNs.
-
After you create the LUNs, run the format(1M) command to partition the disk arrays' LUNs into as many slices as you need.
The following example lists output from the format command.
# format 0. c0t2d0 <SUN18G cyl 7506 alt 2 hd 19 sec 248> /sbus@3,0/SUNW,fas@3,8800000/sd@2,0 1. c0t3d0 <SUN18G cyl 7506 alt 2 hd 19 sec 248> /sbus@3,0/SUNW,fas@3,8800000/sd@3,0 2. c1t5d0 <Symbios-StorEDGEA3000-0301 cyl 21541 alt 2 hd 64 sec 64> /pseudo/rdnexus@1/rdriver@5,0 3. c1t5d1 <Symbios-StorEDGEA3000-0301 cyl 21541 alt 2 hd 64 sec 64> /pseudo/rdnexus@1/rdriver@5,1 4. c2t5d0 <Symbios-StorEDGEA3000-0301 cyl 21541 alt 2 hd 64 sec 64> /pseudo/rdnexus@2/rdriver@5,0 5. c2t5d1 <Symbios-StorEDGEA3000-0301 cyl 21541 alt 2 hd 64 sec 64> /pseudo/rdnexus@2/rdriver@5,1 6. c3t4d2 <Symbios-StorEDGEA3000-0301 cyl 21541 alt 2 hd 64 sec 64> /pseudo/rdnexus@3/rdriver@4,2
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.
-
Run the scdidadm(1M)command to find the raw device identity (DID) that corresponds to the LUNs that you created in Step 1.
The following example lists output from the scdidadm -L command.
# scdidadm -L 1 phys-schost-1:/dev/rdsk/c0t2d0 /dev/did/rdsk/d1 1 phys-schost-2:/dev/rdsk/c0t2d0 /dev/did/rdsk/d1 2 phys-schost-1:/dev/rdsk/c0t3d0 /dev/did/rdsk/d2 2 phys-schost-2:/dev/rdsk/c0t3d0 /dev/did/rdsk/d2 3 phys-schost-2:/dev/rdsk/c4t4d0 /dev/did/rdsk/d3 3 phys-schost-1:/dev/rdsk/c1t5d0 /dev/did/rdsk/d3 4 phys-schost-2:/dev/rdsk/c3t5d0 /dev/did/rdsk/d4 4 phys-schost-1:/dev/rdsk/c2t5d0 /dev/did/rdsk/d4 5 phys-schost-2:/dev/rdsk/c4t4d1 /dev/did/rdsk/d5 5 phys-schost-1:/dev/rdsk/c1t5d1 /dev/did/rdsk/d5 6 phys-schost-2:/dev/rdsk/c3t5d1 /dev/did/rdsk/d6 6 phys-schost-1:/dev/rdsk/c2t5d1 /dev/did/rdsk/d6
-
Use the DID that the scdidadm output identifies to set up the raw devices.
For example, the scdidadm output might identify that the raw DID that corresponds to the disk arrays' LUNs is d4. In this instance, use the /dev/did/rdsk/d4sN raw device, where N is the slice number.
Next Steps
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 Preparing the Sun Cluster Nodes.
How to Use Sun StorEdge QFS Shared File System
You must use Sun StorEdge QFS shared file system with hardware RAID support.
Note –
For detailed instructions for installing, configuring, and using Sun StorEdge QFS shared file system, see Sun StorEdge QFS and Sun StorEdge SAM-FS Software Installation and Configuration Guide and Sun StorEdge QFS and Sun StorEdge SAM-FS File System Administration Guide.
Steps
-
Ensure that the Sun StorEdge QFS software is installed.
-
Ensure that each Sun StorEdge QFS shared file system is correctly configured for use with Sun Cluster Support for Oracle Real Application Clusters.
-
Ensure that each Sun StorEdge QFS shared file system is mounted with the correct options for use with Sun Cluster Support for Oracle Real Application Clusters.
-
For the file system that contains binary files, configuration files, alert files, and trace files, use the default mount options.
-
For the file systems that contain data files, control files, online redo log files, and archived redo log files, set the mount options as follows:
-
In the /etc/opt/SUNWsamfs/samfs.cmd file or the /etc/vfstab file, set the following options:
stripe=width sync_meta=1 mh_write qwrite forcedirectio nstreams=1024 rdlease=300Set this value for optimum performance. wrlease=300Set this value for optimum performance. aplease=300Set this value for optimum performance.
- width
-
Specifies the required stripe width for devices in the file system. The required stripe width is a multiple of the file system's disk allocation unit (DAU). width must be an integer that is greater than or equal to 1.
Note –Ensure that settings in the /etc/vfstab file do not conflict with settings in the /etc/opt/SUNWsamfs/samfs.cmd file. Settings in the /etc/vfstab file override settings in the /etc/opt/SUNWsamfs/samfs.cmd file.
-
-
Register and configure the data service for the Sun StorEdge QFS metadata server.
For detailed instructions, see Sun StorEdge QFS and Sun StorEdge SAM-FS Software Installation and Configuration Guide.
Next Steps
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 Preparing the Sun Cluster Nodes.
How to Use ASM
Steps
-
Run the scdidadm(1M) command to find the raw device identity (DID) that corresponds to shared disks that are available in the cluster.
The following example lists output from the scdidadm -L command.
# scdidadm -L 1 phys-schost-1:/dev/rdsk/c0t2d0 /dev/did/rdsk/d1 1 phys-schost-2:/dev/rdsk/c0t2d0 /dev/did/rdsk/d1 2 phys-schost-1:/dev/rdsk/c0t3d0 /dev/did/rdsk/d2 2 phys-schost-2:/dev/rdsk/c0t3d0 /dev/did/rdsk/d2
-
Use the DID that the scdidadm output identifies to set up the disk in the ASM disk group.
For example, the scdidadm output might identify that the raw DID that corresponds to the disk is d2. In this instance, use the /dev/did/rdsk/d2sN raw device, where N is the slice number.
-
Modify the ASM_DISKSTRING parameter to specify the devices that you are using for the ASM disk group.
For example, to use the /dev/did/ for the ASM disk group, add the value /dev/did/rdsk/d* to the ASM_DISKSTRING parameter as follows:
ASM_DISKSTRING = '/dev/did/rdsk/*'
For more information, see your Oracle documentation.
Next Steps
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 Preparing the Sun Cluster Nodes.
How to Use the Cluster File System
Steps
-
Create and mount the cluster file system.
See Configuring the Cluster in Sun Cluster Software Installation Guide for Solaris OS for information about how to create and mount the cluster file system.
-
If you are using the UNIX file system (UFS), ensure that you specify the correct mount options for various types of Oracle files.
For the correct options, see the table that follows. You set these options when you add an entry to the /etc/vfstab file for the mount point.
File Type
Options
global, logging, forcedirectio
Oracle application binary files, configuration files, alert files, and trace files
global, logging
Next Steps
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 Preparing the Sun Cluster Nodes.
- © 2010, Oracle Corporation and/or its affiliates