Database Locked

We are having intermittent issues with several of our databases locking up. These databases are used to store deleted documents from our primary application databases.

When this happens:

  • LotusScript agents fail when trying to reference the database (from another database in this case), with an error of “Unable to open Name and Address Book (%s), due to error ‘%e’”.

  • The Notes Client cannot open the database

  • Fixup will not run on the database. “This database is currently in use by another person or process, and cannot be accessed at this time.”

  • Windows ProcessMon reports handles to the database by nserver.exe and nclrepl.exe when this is happening. No other databases show the cluster replicator with a handle. Seems like a lock by the cluster replicator.

  • The server does not run anit-virus software, and as stated above - no other software has a handle on the file.

Any ideas or thoughts on how to track this down?

Matt

Subject: Solutions Tried

The only way to unlock the database is a full server reboot.

We have tried these, without success:

  • “restart server”
  • “drop all”
  • Restart cluster replicator
  • “dbcache flush”
  • “load fixup”
    We had 2 cluster replicators, but we are trying it with 1 to see if that prevents future locks.

Subject: Most likely fixed in 9.0.1 FP8: SPR # MKIN9Z6S5D

SPR Release Date modified Description
MKIN9Z6S5D http://www-10.lotus.com/ldd/fixlist.nsf/5c087391999d06e7852569280062619d/556a8b1af86627ee852580d800738c71?OpenDocument&Highlight=0,MKIN9Z6S5D%20 9.0.1 FP8 03/03/2017 Fix an intermittent database issue preventing users from opening a database resulting in the following error "This database is currently in use by…
http://www-10.lotus.com/ldd/fixlist.nsf/5c087391999d06e7852569280062619d/556a8b1af86627ee852580d800738c71?OpenDocument&Highlight=0,MKIN9Z6S5D%20 http://www-10.lotus.com/ldd/fixlist.nsf/5c087391999d06e7852569280062619d/556a8b1af86627ee852580d800738c71?OpenDocument&Highlight=0,MKIN9Z6S5D%20

Crucial tools for IBM Lotus Notes and Domino administration and development…

Find the “crucial tools you need to succeed” including product descriptions, downloads, demos and testimonials.
Speed up IBM Lotus Notes and Domino administration and development with these crucial software tools.
Better, stronger, faster productivity for administrators and developers.
Download and try the lite (free) version http://www.notesmail.com/IBM-Notes-tools

Subject: FP8 did not solve this issue

I am still having this problem occasionally, due to a lock by the cluster replicator.

Subject: maybe this will help?

If the database is in use by something in Notes, try the Domino Administrator to see who has the database open (server tab>database users). you can also force the users to let go of the database by right-clicking on the database name and choosing ‘drop’.

Hope that helps!

Subject: post your code

Could be the way your agen is trying to open or write to the database.

Subject: Updates

Hi Jean-Francios,

I used your fix today “tell clrepl quit” followed by “load clrepl” and it works. Thanks!

Have you been able to resolve this 100% with any new hotfixes?

Matt

Subject: Fixup after a reboot

You could try running fixup after a reboot manually without Domino running: http://www-01.ibm.com/support/docview.wss?uid=swg27006573 http://www-01.ibm.com/support/docview.wss?uid=swg27006573
You could try disabling the cluster replicator as a troubleshooting measure: http://www-10.lotus.com/ldd/dominowiki.nsf/dx/cluster_admin_on http://www-10.lotus.com/ldd/dominowiki.nsf/dx/cluster_admin_on

Subject: Same problem here

It’s very nice to see we are not alone with this problem. We hate this problem since 9.0.1,

IBM Tell us FP2 will solve the problem, problem still present
IBM Tell us FP2HF* will solve the problem, problem still present
IBM Tell us FP3 will solve the problem, problem still present

And so on !

We are currently running with FP4HF523 and the problem is still there.

We have a cluster of 4 serveurs with 6000+ mailfile on each of them… each days, all serveurs choose randomly 1,2,3 or more database to lock.

On my side, 99% of the time, if I run on the console “tell clrepl quit” followed by “load clrepl” to restart the cluster replicator, it solve the problem !

I hope this will be solve in 2016 !

JFLegendre

Subject: Thanks Stuart

Thanks Stuart. That sounds like the fix. I’ll give it a try.

Subject: What does ARAP Status REOP mean?

I just noticed that this has an APAR status of REOP. Does that mean Re-Opened? Do they know this fix did not work?

LO82330: PANIC: ASSERT(FDG->NUMFILEOPENS == 0) FAILED AT LINE 471 IN FILE OSFDG.C https://www-304.ibm.com/support/entdocview.wss?uid=swg1LO82330

Subject: 9.0.1FP5 - Still have this periodic locking issue

I’m losing faith that this will be resolve. Any other way to unlock the database with out rebooting?

Subject: FP3

hey…did you see this from the 9.0.1 FP3 release notes?

  • JPAI9CTMWE (LO82330) - Fixed an intermittent issue that would cause a single Notes database to be locked preventing anyone from opening the database until the Domino server is restarted. Before this fix, users would experience the following error attempting to open the database: "This database is currently in use by another person or process, and cannot be accessed at this time. In order to share a Notes database, it must be accessed via a Domino Server by all users of the database.”

Subject: post your code

Could be the way your agen is trying to open or write to the database.

Subject: Installed 9.0.1 FP3 - Still got error

This really does sound like the same issue, but the server I update has the issue again today.

Like the tech note describes, it appear it is a lock by the nCLREPL process.

LO82330: PANIC: ASSERT(FDG->NUMFILEOPENS == 0) FAILED AT LINE 471 IN FILE OSFDG.C http://www-01.ibm.com/support/docview.wss?crawler=1&uid=swg1LO82330

Maybe the fix did not really fix the issue.