The Sun QFS shared file system is always installed in the global-cluster node, even when a file system is used by a zone cluster. You configure specific Sun QFS shared file system into a specific zone cluster using the clzc command. The scalable mount-point resource belongs to this zone cluster. The metadata server resource, SUNW.qfs, belongs to the global cluster.
You must use the Sun 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 Database relational database management system (RDBMS) binary files
Oracle Database 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 Clusterware 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 Support for Oracle RAC instances of the database.
To facilitate future expansion, create multiple file systems to store these files for all Support for Oracle RAC instances of 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 QFS Metadata Server.
The database files and related files are as follows:
Online redo log files
Archived redo log files
Flashback log files
Oracle Database cluster registry (OCR) files
Oracle Clusterware 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 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.
Before You Begin
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 cluster nodes before configuring the shared file systems.
For information about how to install Sun QFS, see Using Sun QFS and Sun Storage Archive Manager with Oracle Solaris Cluster .
For information about how to create a Sun QFS file system, see Using Sun QFS and Sun Storage Archive Manager with Oracle Solaris Cluster .
For each Sun QFS shared file system, set the correct mount options for the types of Oracle Database files that the file system is to store.
fs=fs-name stripe=width mh_write qwrite forcedirectio rdlease=300
Set this value for optimum performance.wrlease=300 Set this value for optimum performance.aplease=300 Set this value for optimum performance.
# mount mount-point
Specifies the mount point of the file system that you are mounting.
For information about configuring Sun QFS shared file system into a zone cluster, see How to Add a Cluster File System to a Zone Cluster (clsetup) in Oracle Solaris Cluster Software Installation Guide or How to Add a Sun QFS Shared File System to a Zone Cluster (CLI) in Oracle Solaris Cluster Software Installation Guide .
Change the file-system ownership as follows:
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.
# 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 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.