Unexpected truncated documents
Category None
Bookmark :
Two weeks ago I visited a customer that had a problem in one of their Lotus Notes applications. The application replicated to approximately 20 servers and on 2 servers there were documents missing.
It turned out that all replica's did have the same number of documents but these 2 replica's contained a number of truncated documents. These documents only had 2 fields left, $UpdatedBy and $Revisions.
However, there were no replication settings that could explain the document truncation. I found document 1165053 in the Lotus Software Knowledge Base explaining that the truncation can be caused by corrupt replication settings documents. So I ran an agent to delete all replication settings and everything seemed fine.
2 days later I got a call and was told that there were truncated documents again.
So, I went over there a second time and found in the log that the corrupt replication settings documents were added to the database from the template by the design task. So I now ran the agent to remove the replication settings documents from both the database and the template. Since then, no more truncated documents.
Bookmark :
Two weeks ago I visited a customer that had a problem in one of their Lotus Notes applications. The application replicated to approximately 20 servers and on 2 servers there were documents missing.
It turned out that all replica's did have the same number of documents but these 2 replica's contained a number of truncated documents. These documents only had 2 fields left, $UpdatedBy and $Revisions.
However, there were no replication settings that could explain the document truncation. I found document 1165053 in the Lotus Software Knowledge Base explaining that the truncation can be caused by corrupt replication settings documents. So I ran an agent to delete all replication settings and everything seemed fine.
2 days later I got a call and was told that there were truncated documents again.
So, I went over there a second time and found in the log that the corrupt replication settings documents were added to the database from the template by the design task. So I now ran the agent to remove the replication settings documents from both the database and the template. Since then, no more truncated documents.
- 


Comments
Nice find! Congrats.
Posted by Jorn At 17:51:26 On 05-07-2009 | - Website - |
I am having a similar problem with one of my users. All replication settings seem to be fine from the client options that can be viewed. However the emails over 40kb still truncate. Could you please send me a link or the name of the agent you ran accross the database so that I can see if I can fix this issue.
Thanks,
Luke
Posted by Luke Everett At 01:29:05 On 07-08-2009 | - Website - |