Reputation: 24630
I have a Notes DB where doc. might be edited by diferent users. So i enable locking to avoid conflicts. After working some weeks w/o problems now it seems that locks don't get released after closing of the document. So i disable locking and the users can edit again.
Is there any action (compact, copy) to do, to get that stable again ?
This is a single DB (others working fine) on Domino 8.
Upvotes: 0
Views: 2026
Reputation: 9561
These symptoms sound similar to this issue reported on the IBM support site. Details on the intracacies of Document locking are here, suffice to say it's not bullet proof, see here. If this is the same issue it was resolved in release 7.0.2 and 6.5.5 FP2. Given that you're using version 8 it should remain fixed, unless it has been introduced as a regression.
Upvotes: 1
Reputation: 942
I will assume that you are saying that this behavior (locked documents not unlocking when users close the document) is persistent (whenever document locking is enabled) and consistent among all users.
You can try a fixup on the database- the server console command would be:
Load fixup yourdb.nsf
You could also create a "Release All Locks" agent (must be run under an ID with Manager access) with target "All Documents in Database":
SELECT @IsAvailable($Writers) | @IsAvailable($PWriters) | @IsAvailable($PTWriters);
@DocLock([UNLOCK])
An education-based strategy might be to retrain users to use Actions-Lock Document and Action-Unlock Document rather than relying on automatic locks from editing or closing a document.
A good source for deeper understanding of document locking is this eView article.
Upvotes: 3