We recently discovered a database that had some corruption due to the document compression bug related to 8.5.1. We have received a hot fix from Lotus Support to prevent any further database corruption, but we have had to repair and resolve issues with a number of databases.
As I was working on this particular database, after running fixup on the database, I attempted to run a folder upgrade, as we have found that some of the corruption relates to older folder designs. The folder upgraded failed. The error message returned indicated that the agent had exceeded the 64k limit.
So I started investigating further. We have a little agent we run to look at folder structures. It will look through each folder, determine how many documents in a folder, and prepare a list of all folders. I ran that agent. And waited, and waited, and waited.
The results came back. The user’s database contained 2,937 folders. Yes, you are reading that correctly. 2,937! This is an all time record for the users at our site. And we’ve had a few who have run amok with folders. My next step was to push data from a backup replica to the repaired replica to restore the corrupted documents that had been deleted during the fixup. Again, I waited, and waited, and waited. And here is the dialog that appeared after the replication completed. Yes 40,191,544 databases replicated! Well done Domino is all I could say!
My best guess is that because the folder structure exceeded the 64k limit on naming structure, somehow this affected the report back to the replication statistics dialog. I confirmed that the correct number of documents were restored by reviewing the database properties.
Sometimes you just have to see it to “believe it.”

