solution for ORA-27054: NFS file system where the file is created or resides is not mounted with correct options in RAC env

solution for ORA-27054: NFS file system where the file is created or resides is not mounted with correct options in RAC env

some issue with expdp failure on a RAC database and want to share some info reg that. We have ten 10.2.0.4 RAC databases  on the same server.

For database files, we are using ASM and for rman backup we are using tapes. Only for export backup (FULL=Y), we created NFS mount point and scheduled export to that file system.

We have observed that out of 10 databases, export is failing for one database with the below error

ORA-39001: invalid argument value
ORA-39000: bad dump file specification
ORA-31641: unable to create dump file “/dbexports/EXP/proddb2/proddb2_120807225312.dmp”
ORA-27054: NFS file system where the file is created or resides is not mounted with correct options
Additional information: 2

This is the error we are facing in 2nd instance. when we execute the same script from 1st instance, it is working fine. After some analysis, found that it is a bug in 10.2.0.4 with bug # 9115046. More info about this bug is in metalink note

ORA-27054 from EXPDP to NFS disk which does not have “noac” set (Doc ID 9115046.8)

As per this note, the above error will occur when NFS file system is not mounted with correct options.

“ORA-027054 error is reported by expdp when run against a RAC enabled database if the target location for the data pump data file is an NFS disk which does not have the “noac” property set against it. “noac” is required for datafiles and many other database file types but should not be needed for expdp output files.”

This bug is fixed in 11.2.0.1 version, so we may get this in 11.1.0.7 also.

As a workaround to avoid this, use a different destination for the datapump export file which does have relevant attributes, or is a local file system
OR
Use event 10298 level 32 to disable the noac check   (but take care as this avoid all NFS checks for all file types which can lead to corruption scenarios if disks are not mounted with the correct options)

ALTER SYSTEM SET EVENTS ‘10298 trace name context forever, level 32′;

As a permanent fix, we need to apply patch aganist that bug