ORA-27054 ERRORS WHEN RUNNING RMAN WITH NFS

Starting Control File and SPFILE Autobackup at 01-SEP-15
RMAN-00571: ===========================================================
RMAN-00569: ERROR MESSAGE STACK FOLLOWS
===========================================================
RMAN-03009: failure of Control File and SPFILE Autobackup command on ORA_DISK_2
channel at 08/01/2006 16:43:49
ORA-19504: failed to create file "/u01/backup/c-4256538111-20060801-02"
ORA-27054: NFS file system where the file is created or resides is not mounted  with correct options Additional information: 2

SOLUTION

Cause 1: - Mount Options are Correct but still getting the errors (Bug 5146667 )

From  Oracle 10G R2 , Oracle checks the options with which a NFS mount is mounted on the filesystem. and this is done to ensure that no corruption of the database can happen as incorrectly mounted NFS volumes can result in data corruption.

There are no single set of NFS mount options that work across all Oracle platforms
Please ensure that you have the proper mount options specified by the NAS vendor /Vendor user guide

The exact checks used for an NFS mounted disk vary between platforms but in general the basic checks will include the following checks

a) The mount table (eg; /etc/mnttab) can be read to check the mount options
b) The NFS mount is mounted with the "hard" option
c) The mount options include rsize>=32768 and wsize>=32768
d) For RAC environments, where NFS disks are supported, the "noac" mount option is used.

Please refer the section -- NFS Mount Options in Oracle Database Installation Guide10g Release 2 (10.2)
If you have  ensured that the mount  options are appropriate and still getting the errors then you are encountering symptoms as  in Bug 5146667   Fixed In Ver: 11.0. 0.0


And this  issues is  found to be  port specific and reproducable on Solaris

Solution 1 :-

To implement the solution, please execute the following steps:

From the errors that we see from the RMAN stack this looks like Bug 5146667

This behaviour has been observed on Solaris and AIX Platform.

A) WORKAROUND:

As suggested in the bug  the workaround recommended is to use the Event 10298.

sql> alter system set events '10298 trace name context forever, level 32';
or

sql> alter system set events '10298 trace name context forever, level 32' scope=spfile;

or:
  Set the following event in the init.ora
      event="10298 trace name context forever, level 32"