Database corruption -- some common causes
Database corruptions are typically caused by a lack of system resources or when a component of a database exceeds a hardcoded design threshold. Here are some recommendations. If possible, remove the use of read marks from the database. For example, use a status flag in both documents and views. This will have a significant impact on performance. In addition, deletion stubs in the databases should be minimized. The default purge interval is one-third of 90 days. To determine the number of deletion stubs the following server console command may be utilized.
>Sh database "DatabaseName"
The Notes Indexer task is very CPU intensive. If the Indexer is found to almost always be active, balance its use with available system resources. Several of the following Notes.in parameters could be implemented.
Default is 1 minute. Increase to index less often. Unit is minutes.
Forces update at X# of update requests.
Undocumented. Default is 1 minute. Increase to update hidden NAB views less often. Unit is minutes.
Undocumented. Disables automatic updating of hidden NAB views.
Undocumented. Does not force rebuild of namespace views if they are out of date. Indexer will update views in background. Faster name resolution.
It is recommended that you use UPDATE_SUPPRESSION_TIME and UPDATE_SUPPRESSION_LIMIT.
To order the book Lotus Notes & Domino 5 Scalable Network Design visit http://www.osborne.com/lotus/lotus_domino_network.htm
This was first published in December 1999
Our Tips Exchange is a forum for you to share technical advice and expertise with your peers and to learn from other enterprise IT professionals. TechTarget provides the infrastructure to facilitate this sharing of information. However, we cannot guarantee the accuracy or validity of the material submitted. You agree that your use of the Ask The Expert services and your reliance on any questions, answers, information or other materials received through this Web site is at your own risk.