Expdp on NAS - ORA - 27086 unable to lock file - already in use

Lately came across an error while taking an export using datapump on database version 12.2.0.4 on a NAS drive.

Error Stack

ORA-39001: invalid argument value

ORA-39000: bad dump file specification

ORA-31641: unable to create dump file "<NAS mount location>/export_file.dmp"

ORA - 27086 unable to lock file - already in use

Linux-x86_64 Error: 37: No locks available

Additional information: 10

ORA-27037: unable to obtain file status

Linux-x86_64 Error: 2: No such file or directory


It may initially looks like the file has been already been used by some other process, but looking at the file it was never existed and only created while this export dump and no other process was holding lock on this.

Now one may also think of any problem with NAS export option, but same option has been working fine for long time with no changes. 

At last came to know about about DNFS, this feature is pretty cool and help in pacing up the speed of exports. Check within your database if you see any NAS already being listed

select * from v$dnfs_servers;

If it list zero records then, there is high change your DNFS is disabled and you can enable it by:

make -f ins_rdbms.mk dnfs_on

Note : Please be careful while implementing this production and reach out to experts or oracle support.

After enabling DNFS some time database instance also needs to be restarted to get effect of this and then try export again. This time it will be success.


Often it's observed this feature is not heavily used by organizations. This feature will also speed up your Datapump jobs. These are some caveats as well of using this functionality in case your underlying NAS path is not changed but and using an alias. For such alias if it's pointed to new server you may see error while export and in that case database bounce is needed.

Comments

Post a Comment

Popular posts from this blog

How to Solve - "WAIT FOR EMON PROCESS NTFNS"

Event Monitor Process in short called as EMON is generally used by oracle to send notification. Often applications uses Database Change Notification process also called as DBCN to be aware of changes in the database, based on these notifications they take further actions. Often clients subscribe to the database and notifications are send as callback to them. In some cases you will notice database sessions are showing wait event "WAIT FOR EMON PROCESS NTFNS" and it can even make your database un-responsive. One observation can be these processes are taking more CPU (may not in be in all cases). As stated EMON process deals with database notification and it's spawn and gets down itself and Administrators have no control on theses processes. Anyone can go through oracle documents to read more EMON functioning process.  EMON uses oracle advanced queues and database queue notifications into them and EMON process these notifications to clients based on their subscriptions. In s
Read more

Query Regression - "OR" Transformation Oracle 19c

Recently while upgrading Oracle Database from version 12.1 to 19.10 found there were couple of queries which was running slow post upgrade. Usually these type of behavior is seen while upgrading to newer version and oracle provide various ways to fix them. The difference between good and bad plan was an introduction of  "MERGE JOIN CARTESIAN" (aka MJC) and that's in where regressed query in 19c taking most of the time. MJC sometimes works for queries but in this case it was clearly not helping.  We had following options here:     1. Copy the profile from 12c to 19c database and it worked, but the problem was not just to specific query but with many similar query. This means profile option is not very attractive in this case.     2. We also tried running query with OFE 12.1 to use the same optimizer features as previous version and query behaves well. Though this option can't be placed as we need to use 19c OFE and can be placed only for testing purpose.           alte
Read more

ORA - 12537: TNS: connection closed

Often when active clone to be done to create a new environment, we land up into couple of issues. I will discuss about one issues during this process. Action : Create a new database on different machine from a source. Error : ORA - 12537: TNS: connection closed In order to duplicate the environment was using below rman log /tmp/duplicate.log connect target sys/<password>@<source tns alias> connect auxiliary sys/<password>@<target tns alias> run{ allocate channel ch1 device type disk; allocate channel ch2 device type disk; allocate channel ch3 device type disk; allocate channel ch4 device type disk; allocate auxiliary channel ax1 device type disk; allocate auxiliary channel ax2 device type disk; allocate auxiliary channel ax3 device type disk; allocate auxiliary channel ax4 device type disk; DUPLICATE TARGET DATABASE TO <TARGET_DBNAME> FROM ACTIVE DATABASE NOFILENAMECHECK; } While making connection to Auxiliary database received mentioned error ORA - 12537:
Read more