Blog

While doing your DBA tasks, you may encounter this ORA-27086 error. Today we will discuss how to resolve this error with steps in detail. First of all, it is not an Oracle error, you need to contact your OS admin to troubleshoot further on this.

Problem :

ORA-39000: bad dump file specification
ORA-31641: unable to create dump file "/oracle/data/export/TEST_table_exp.dmp"
ORA-27086: unable to lock file - already in use
Linux-x86_64 Error: 37: No locks available

Solution :

Various scenarios may occur from the server end too. So you can ask your Linux admin to check the below issues if needed:

Case 1 :

Sometimes the error may occur due to NFS hung, that time usually you used to see “statd: server localhost not responding, timed out” message in OS Logs. so you can contact your Linux Admin. Dismount or Mount of NFS may help. Or sometimes, restarting NFS services may help.

Command to Check and restart NFS service .

Note: Please check with your OS Admin before issuing below commands. Its not recommended to do without OS Admin intervention in the production environment.

Check NFS service :
service nfslock status

Check NFS service :
/etc/init.d/nfs restart

Steps to restart NFS Manually :

Stop NFS service :

service nfslock stop
service nfs stop
service portmap stop
umount /proc/fs/nfsd

Start NFS Service:

service portmap start
service nfs start
service nfslock start
mount -t nfsd nfsd /proc/fs/nfsd

Case 2:

If it’s not working, for an emergency workaround you can reboot your server.

Case 3 :

Please check the NFS version as well because it may be a Bug also (Bug 8727960) as per Oracle Doc ID 2205485.1. So its solution is to upgrade the nfs -utils-1.0.9-66 or later.

So, here are the steps to troubleshoot ORA-27086 error with the help of OS admin. Hope this helps!!

Our Other ORA Error-Related Articles:

• Troubleshooting ORA-03113 Error: end-of-file on communication channel

• ORA-19802: cannot use DB_RECOVERY_FILE_DEST without DB_RECOVERY_FILE_DEST_SIZE