When using NFS storage, Oracle recommends using Oracle Direct NFS (dNFS) rather than native kNFS.

Note: According to Oracle, caution should be exercised when considering using NFS storage in an Oracle database that uses ASM. In general, such configurations should be avoided or at least carefully considered. The issue is that to prevent data corruption, NFS file systems must be hard-mounted. Hard mounting means that the database or an ASM instance must wait indefinitely when an NFS server, or the communications link it operates over, becomes unavailable. NFS on ASM might be reasonable in some situations. See Oracle MOS note doc ID 1620238.1, “Creating File Devices On NAS/NFS FileSystems for ASM Diskgroups.”

To create ASM disks from PowerStore file systems, follow these steps:

1. In PowerStore Manager, create the PowerStore NAS export. See the section Dell PowerStore NFS file system and NFS export.
2. Log in to the NFS client (database server) as root.
3. Create a mount point for the NAS export. Change the owner, group, and privileges of the mount point to the Linux user owning the Oracle Grid software install.

mkdir /ora-asm-db2

chown grid:oinstall /ora-asm-db2

chmod 770 /ora-asm-db2

4. Mount the PowerStore NFS export using the IPv4 address of the NFS Export Path.

mount -t nfs -o rw,bg,hard,nointr,tcp,vers=3,\

timeo=600,rsize=32768,wsize=32768,\

actimeo=0 mmm.mmm.mmm.mmm:/ora-asm-db2 /ora-asm-db2

Note: For rsize and wsize values, see the sections Mount options for an NFS share and Display PowerStore’s current nfs v3 buffer sizes.

5. The first time the NFS share is mounted, change the owner, group, and privileges of the root directory on the NFS export to the Linux user owning the Oracle Grid software install:

chown grid:oinstall /ora-asm-db2

chmod 770 /ora-asm-db2

6. Prepare the ASM disks and set their permissions, ownership, and group membership to the operating system user owning the Oracle Grid software: