Database Tutorials MSSQL, Oracle, PostgreSQL, MySQL, MariaDB, DB2, Sybase, Teradata, Big Data, NOSQL, MongoDB, Couchbase, Cassandra, Windows, Linux 
When you try to get a backup with Rman, if you get errors like ORA-27086, ORA-01580, the first place you should check is nfs shares.
If you are trying to create a control file snapshot file on a nfs share, you need to change the nfs mount options.
Unmount the Nfs mounted directory, add “noac” to the mount options, and re-mount it.
During the backup operation with Rman, noac option will be useful if an error is received as follows.
1 2 3 4 5 6 7 8 9 10 | ORA-00245: control file backup operation failed RMAN-03009: failure of Control File and SPFILE Autobackup command on ch00 channel at 10/27/2011 15:07:52 RMAN-00571: =========================================================== RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS =============== RMAN-00571: =========================================================== RMAN-08132: WARNING: cannot update recovery area reclaimable file list Additional information: 10 Linux-x86_64 Error: 37: No locks available ORA-27086: unable to lock file - already in use ORA-01580: error creating control backup file /snapcf/snapcf_orcl1.f |
Umount and mount operations:
Perform the umount operation first:
1 | [root@orcldb ~]# umount /snapcf |
In /etc/fstab, add a line as follows. Change IP and directory information according to your own system. Other options are the necessary options for the Oracle database’s nfs directory.
1 | 192.168.1.30:/export/snapcf /snapcf nfs noac,rw,bg,hard,nointr,rsize=1048576,wsize=1048576,tcp,nfsvers=3,timeo=600 0 0 |
Perform the mount operation again:
1 | [root@orcldb ~]# mount /snapcf |
