We are seeing a lot of customers who are concerned that NFS has been desupported in RAC with 12cR2. We got the same concerns with 12cR1.
What actually happened is Oracle removed support for certain RAC configuration files directly on a filesystem, NFS or otherwise, with new 12cR1 installs, although older 11g installs could be upgraded to 12cR1 in place. Oracle has totally desupported files directly on a filesystem for 12cR2 RAC.
Instead, ASM must be used for all RAC installations. This does not create a complicated management requirement for ASM. The RAC installer will prompt the user for the paths to some files on NFS. These are then configured as a basic ASM instance with the RAC related files stored inside. The administrator can essentially forget that ASM exists after installation unless they plan to use ASM for the databases themselves.
Here’s what it looks like when complete:
root@jfs3-a ~]# cd /crs root@jfs3-a crs]# ls -l total 36096508 -rw-rw---- 1 oracle dba 39641088000 Oct 18 06:38 ocrvfdgdisk0
I’m using NFS with just a one-disk ASM diskgroup. Yes, there are some ASM processes running, but it was all set up automagically when I installed RAC. If I wanted extra reliability, I could have made this a 3-disk group using three different NFS shares from different controllers, but on the whole one is fine for a local cluster. Previously there were a bunch of files in an NFS share that I ignored. Now there are a bunch of files encapsulated in an ASM diskgroup based on some NFS files that I am ignoring.
The installer has options for all of this. The only real difference is you have to use “dd” to make a big, blank file on the NFS shares you use for CRS/voting, and set the permissions. You then point the installers to those giant pseudo-LUNs rather than pointing the installer to the filesystem itself. The installer does the rest.