- Try running Fixup on the file. You can do this from the Admin client or the server console. See Domino Admin Help -> Index -> Fixup.
- Try recreating the file completely, using File -> Database -> New Copy. This will change the replica ID, so you have to make new replicas on each server in the domain. But this will often fix corrupted files.
We faced a similar address book corruption problem. Yes, Fixup and Updall will fix the problem temporary, but the address book will corrupt again after a few days. Hopefully, someone has more feedback about this problem.
If it is possible for you to shutdown the Domino Server Service, you could try running the shell command 'ncompact names.nsf -c' from the LotusDomino directory. This will create a new replica of the database and will try to remove corruption from within the database. This solution has worked in several organizations that I have been with. However, it's not full proof. On a couple of occasions we had to go to IBM for further assistance because the corruption was caused by having a large number of connection documents that were created in an R5.0 or R5.0.1.
Do you have comments on this Ask the Expert question and response? Let us know.
Dig deeper on Lotus Notes Domino Performance
Related Q&A from Chuck Connell
Is it possible to encrypt a user's name before sending an email? SearchDomino.com expert Chuck Connell weighs in.continue reading
Learn how to change authentication timeout interval for Domino Web Access logins.continue reading
SearchDomino.com expert Chuck Connell provides a resource for a Lotus Notes administrator who wants to filter out email containing the word "spam," ...continue reading
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.