Since we have gone to 6.0.1, we are experiencing a number of corruptions in mail files. Not sure why they are happening, but once out of every 3 times I try to repair a mail file while the server is up and running, we experience problems where some server task ends up hanging. I end up having to reboot the server to get full functionality back.
What are the best practices for repairing mail files online. I have been shutting down the router, then running fixup. Is there something else that I should be doing?
Thanks.
Subject: Repairing Mail DBs - Best Practices
Hi:
Had a lot of problems with this after migration from R5 to R6
They dissapeared after upgrading ODS of databases from 41 to 43
You can accomplish this issuing the ‘load compact’ command except for DBs which are in use.
For this DBs you can schedule the compact at off-hours or just running compact with server stopped, from windows (Similar on other OSs):
ncompact
Greetings,
J R
Subject: RE: Repairing Mail DBs - Best Practices
Thanks for the response. Yeah, I haven’t upgraded the ODS for all DBs yet. Perhaps that will solve my problems. After that, do you think that I will be able to run repairs without any issues?
Subject: RE: Repairing Mail DBs - Best Practices
There are some errors in the 6.0, 6.0.1 and 6.0.1 CF1 that makes the server hang/crash during fixup. Lotus Customer support has sent me a HotFix that solved this issue. I belive it`s a part of 6.0.2 or 6.0.1 CF2. Just be careful with the Fixup when you are running 6.0 6.0.1 or 6.01 CF1
Subject: RE: Repairing Mail DBs - Best Practices
Thanks for the reply. I will be on the look out for 6.0.2.
Subject: RE: Repairing Mail DBs - Best Practices
You could also create replicas of the affected mail databases and replace the old replicas with the new.