Lately I’ve been dropping/missing documents out of our main database. … I have the main db replicating to a second server (push only) as a backup. … I can open the replicate db and find the documents showing there. I then have to copy the documents back into the main database to appear.
I have a “All Document” view that shows NotesID, UNID and other information along with parent and response documents.
The document has the setting of “Merge Conflict” enabled and “prior versions become responses”
When I look in the “All Document” view the documents do not appear. After I copy the documents back into the main db from the replica copy, I then see two parent documents along with all the response documents for just one of the parent documents. Only the parent document with a different UNID shows up in any of my views. The parent document with repsonses still do not show up in any of the other views. Only after I open this parent document and do a refresh and save does this parent document and responses show up in the views. I then have to delete the second parent document.
I have not a clue on what’s going on with this. Any help will be appreciated.
The other question is: Can a “merge conflict” change the document UNID? …
Well, your view is probably set to show documents in their response hierarchy and since the parent document goes missing, the responses (conflicts) do not appear. As soon as you put the parent document back into the view, the responses now have a parent to which they can attach and thus be displayed in the view. You could change the view property to not show response documents in a hierarchy and at least you will be able to see them in your All Documents view.
What’s causing the parent to disappear is another matter however - don’t know what that could be. Any maintenance agents that delete them? Any issue with server rights or selective replication?
Thanks for the quick response. … No maintenance agents are running and already checked the server rights and no selective replication is enabled. … I’ve been doing some more searching and found that the conflict document does get a new UNID. … I take it this does the same for a Save Conflict …??? …
However, the point of merging replication conflicts is to reduce the number of such documents, so setting that property to true is probably a good thing.
If you find that most of the replication conflicts you are getting are because you have few replications in comparison to the number of edits that different people will make to the document on different servers, then you could look at increasing the replication frequency.
If you have save conflicts because two people edited the same document on the same server at the same time, you might look into document locking
Thanks again for the response. … I think what is happening is more on the Save Conflict. I’ll look into the Lock document and see what I can come up with.