You must use the Sun StorEdge QFS shared file system with one storage management scheme from the following list:
Hardware RAID support
Solaris Volume Manager for Sun Cluster
Distribute these files among several file systems as explained in the subsections that follow.
For RDBMS binary files and related files, create one file system in the cluster to store the files.
The RDBMS binary files and related files are as follows:
Oracle relational database management system (RDBMS) binary files
Oracle configuration files (for example, init.ora, tnsnames.ora, listener.ora, and sqlnet.ora)
System parameter file (SPFILE)
Alert files (for example, alert_sid.log)
Trace files (*.trc)
Oracle Cluster Ready Services (CRS) binary files
For database files and related files, determine whether you require one file system for each database or multiple file systems for each database.
For simplicity of configuration and maintenance, create one file system to store these files for all Oracle RAC instances of the database.
To facilitate future expansion, create multiple file systems to store these files for all Oracle RAC instances of the database.
If you are adding storage for an existing database, you must create additional file systems for the storage that you are adding. In this situation, distribute the database files and related files among the file systems that you will use for the database.
Each file system that you create for database files and related files must have its own metadata server. For information about the resources that are required for the metadata servers, see Resources for the Sun StorEdge QFS Metadata Server.
The database files and related files are as follows:
Online redo log files
Archived redo log files
Flashback log files
Oracle cluster registry (OCR) files
Oracle CRS voting disk
For optimum performance with Solaris Volume Manager for Sun Cluster, configure the volume manager and the file system as follows:
Use Solaris Volume Manager for Sun Cluster to mirror the logical unit numbers (LUNs) of your disk arrays.
If you require striping, configure the striping by using the file system's stripe option.
Mirroring the LUNs of your disk arrays involves the following operations:
Creating RAID-0 metadevices
Using the RAID-0 metadevices or Solaris Volume Manager soft partitions of such metadevices as Sun StorEdge QFS devices
The input/output (I/O) load on your system might be heavy. In this situation, ensure that the LUN for Solaris Volume Manager metadata or hardware RAID metadata maps to a different physical disk than the LUN for data. Mapping these LUNs to different physical disks ensures that contention is minimized.
You might use Solaris Volume Manager metadevices as devices for the shared file systems. In this situation, ensure that the metaset and its metadevices are created and available on all nodes before configuring the shared file systems.
Ensure that the Sun StorEdge QFS software is installed on all nodes where Sun Cluster Support for Oracle RAC is to run.
For information about how to install Sun StorEdge QFS, see Sun StorEdge QFS Installation and Upgrade Guide, Version 4, Update 5.
Ensure that each Sun StorEdge QFS shared file system is correctly created for use with Sun Cluster Support for Oracle RAC.
For information about how to create a Sun StorEdge QFS file system, see Sun StorEdge QFS Configuration and Administration Guide, Version 4, Update 5.
For each Sun StorEdge QFS shared file system, set the correct mount options for the types of Oracle files that the file system is to store.
fs=fs-name 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.
Specifies the name that uniquely identifies the file system.
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.
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.
Mount each Sun StorEdge QFS shared file system that you are using for Oracle files.
# mount mount-point
Specifies the mount point of the file system that you are mounting.
Owner: the database administrator (DBA) user
Group: the DBA group
The DBA user and the DBA group are created as explained in How to Create the DBA Group and the DBA User Accounts.
# chown user-name:group-name mount-point
Specifies the user name of the DBA user. This user is normally named oracle.
Specifies the name of the DBA group. This group is normally named dba.
Specifies the mount point of the file system whose ownership you are changing.
Grant to the owner of each file system whose ownership you changed in Step 4 read access and write access to the file system.
# chmod u+rw mount-point
Specifies the mount point of the file system to whose owner you are granting read access and write access.
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.