Since upgrade from 8.5.3 document locking it’s not working as expected.
Before upgrade, when one user edit a specific document, and a second user try to open it for edit, this second user got a message and could not edit the document.
After upgrade, the user receives a message that this document is being edited, and it opens it for edit. When the users save the document, it creates a replication conflict.
We did not changed nothing, this database resides on a single server, without replicas, and users work online on it.
I did a fixup in the database, but no help.
Can someone help, or give a direction on how to solve this?
Check to make sure the database property allowing Document locking didn’t get un-set during your upgrade - its on the bottom of the first tab of database properties
Thank you for your response, but I did it already. As I said, the configuration was checked, and the database was already compacted, fixup, updall, with all switches we can think.
I even have replicated to another server, then removed from the original, and created a fresh new replica, checked configuration, and the problem still exists.
I have now a PMR open, and we are now on the second level, no solution so far.
If you only have 1 replica on 1 server, IBM recommend you disable document locking in the application properties. By default, Domino provides soft locking which prevents 2 users from editing the same document at the same time from the same replica. Only way I know around this is to use EDIT_NO_SOFT_LOCKS=1 in Notes. Now, conflicts can still occur is certain situations even with the default soft locking. If 2 people open the same document at the same time, one edits it and saves and closes, then the other edits it (has old version of the doc open, not updated version), a conflict occurs. One way around this is to set the document to open up to edit mode so it automatically is locked when anyone opens it. Of course, then 2 people cannot read the same doc at the same time.