VDB operations such as start, provision, refresh and rewind may stall with the Oracle alert log reporting that the database is unable to lock a file due to no locks being available, as in the example below.
SQL> ORA-01565: error in identifying file '/provision/VDB1/datafile/spfile.ora' ORA-27086: unable to lock file - already in use Linux-x86_64 Error: 37: No locks available Additional information: 10
The Delphix engine is running version 6.0 or later.
The Delphix engine hosts VDBs that access their data files via NFS, for example Oracle, SAP ASE, or AppData.
Applicable Delphix Versions
- Click here to view the versions of the Delphix engine to which this article applies
Major Release All Sub Releases 6.0 184.108.40.206, 220.127.116.11, 18.104.22.168, 22.214.171.124, 126.96.36.199, 188.8.131.52, 184.108.40.206, 220.127.116.11, 18.104.22.168, 22.214.171.124, 126.96.36.199, 188.8.131.52, 184.108.40.206, 220.127.116.11, 18.104.22.168, 22.214.171.124, 126.96.36.199, 188.8.131.52, 184.108.40.206, 220.127.116.11, 18.104.22.168, 22.214.171.124, 126.96.36.199
The cause of the timeouts during reverse DNS lookups of the target host IP address(es) should be investigated in order to prevent further occurrences of this issue.
To work around this issue, entries for the target hosts can be added to the hosts file of the Delphix engine using the steps listed in the document below. This avoids the need to look up the details via DNS but would need to be actively maintained in the event that the names or IP addresses of the target hosts change or if target hosts are added or removed.
This issue will be resolved in a future Delphix version via bug DLPX-80112.
Please engage Delphix Support for troubleshooting assistance in the event that this issue is suspected.
The following articles may provide more information or related information to this article: