Domino & Notes error

LkMgr BEGIN Long Held Lock Dump

Only appears with transaction logging enabled. A matching END line follows, with lock details in between.

What it means

The lock manager noticed a database lock held for an unusually long time and dumped details of it. HCL describes it as informational, but frequent dumps point to contention or slow storage.

Common causes

  • A long view index update or updall on a large database
  • Two tasks working on the same database, for example compact and fixup
  • Slow or overloaded disk I/O
  • A deadlock defect in some releases

Quick fixes

  1. Note the database named in the dump and check what is running against it with show tasks
  2. Let long tasks finish, or reschedule compact, fixup and updall so they do not overlap
  3. Check disk latency on the data and transaction log volumes
  4. If it persists or the server hangs, run nsd -detach three times a few minutes apart and log a case with HCL

Need a hand with this?

Paste your exact message into What's That Error? for a plain-English explanation, or get in touch. I've been supporting Domino and Notes for 28 years.

Disclaimer

The errors, causes and fixes on this site are carefully researched, drawing on HCL documentation and 28 years of hands-on Domino and Notes experience. Every environment is different, though, and a solution that works in one may not be right for yours. Exact wording can also vary between Domino and Notes versions.

This information is general guidance only and is provided without warranty of any kind. Always back up your data and test changes on a non-production system first. To the extent permitted by law, Bruinsma Services Pty Ltd accepts no responsibility or liability for any loss, damage, downtime or other consequence arising from use of this information. For advice specific to your environment, please contact me.