Professional Documents
Culture Documents
Mount Options for Oracle files for RAC databases and Clusterware when used with NFS on NAS devices
(Doc ID 359515.1)
In this Document
Purpose
Scope
Details
RAC including RACone and single instance RAC
References
APPLIES TO:
PURPOSE
The options with which the NAS systems should be mounted are described. This note does not cover the new dNFS feature that was
introduced in 11g.
SCOPE
This document is relevant to all environments using Oracle Clusterware & RAC.
DETAILS
Binaries is the shared mount points where the Oracle Home and CRS_HOME is installed.
Datafiles includes Online Logs, Controlfile and Datafiles
nfsvers and vers are identical on those OS platforms that has nfsvers. The ver option is an alternative to the nfsvers option. It is
included for compatibility with other operating systems
Please note that the mount options on each of the following cells are applicable only to those type of files listed in the column
heading.
The non-shared GI HOME and ORACLE HOME on non-shared NFS mount point is not tested, so although noac may not be
needed, its absence still cause problems at runtime because the RDBMS (and ASM) code
contains validations of the NFS mount options, so this configuration should not be used.
For RMAN backup sets, image copies, and Data Pump dump files, the "NOAC" mount option should not be specified
- that is because RMAN and Data Pump do not check this option and specifying this can adversely affect
performance.
In 12.2, both OCR and voting disks must reside in ASM. Refer to Document 2201844.1
1 of 3 10/08/2020 15:51
Document 359515.1 https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-stat...
The NFS storage for asm diskgroup (not quorum disks) that has the OCR and voting disk must use the mount
options listed for CRS Voting Disk and OCR
The NFS storage for asm diskgroup (not quorum disks) that does not have the OCR and voting disk must use the mount options
listed for Oracle Datafiles
rw,bg,hard,nointr,rsize=32768,
rw,bg,hard,nointr,rsize=32768, rw,bg,hard,nointr,rsize=32768,
Sun Solaris * wsize=32768,proto=tcp,noac, wsize=32768,proto=tcp,noac, wsize=32768,proto=tcp,vers=3,
forcedirectio, vers=3 noac,forcedirectio
vers=3,suid
rw,bg,hard,nointr,rsize=32768,
cio,rw,bg,hard,nointr,rsize=32768, cio,rw,bg,hard,intr,rsize=32768,
AIX (5L) ** wsize=32768,proto=tcp, wsize=32768,proto=tcp,noac, wsize=32768,tcp,noac,
vers=3,timeo=600 vers=3,timeo=600
vers=3,timeo=600
* NFS mount option “forcedirectio” is required on Solaris platforms when mounting the OCR/CRS files when using Oracle 10.1.0.4 or
10.2.0.2 or later (Oracle unpublished bug 4466428)
** AIX is only supported with NAS on AIX 5.3 TL04 and higher with Oracle 10.2.0.1 and later
*** NAS devices are only supported with HPUX 11.23 or higher ONLY
# These mount options are for Linux kernels 2.6 and above. For older kernels please check Note 279393.1
## The stated mount options for binaries are applicable only if the ORACLE HOME is shared.
Soft mounts are recommended for ASM Quorum Disk mounts. Hard mounts may hang I/O and bring down the entire ASM system.
When using a soft mount, ASM handles an I/O failure gracefully, and will offline only the associated quorum disk. ASM quorom disks do
not store user data, so there is no risk of data corruption on the quorum disk itself.
When using NFS for regular database files, see: General Configuration Guidelines for NAS Devices
2 of 3 10/08/2020 15:51
Document 359515.1 https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-stat...
Due to Unpublished bug 5856342, it is necessary to use the following init.ora parameter when using NAS with all versions of RAC on
Linux (x86 & X86-64 platforms) until 10.2.0.4. This bug is fixed and included in 10.2.0.4 patchset.
filesystemio_options = DIRECTIO
REFERENCES
NOTE:1567137.1 - Sun ZFS Storage Appliance: Oracle Database 11g R2 NFS Mount Point Recommendations
NOTE:279393.1 - Linux/NetApp: RHEL/SUSE Setup Recommendations for NetApp Filer Storage
3 of 3 10/08/2020 15:51