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 parameters could be implemented. UPDATE_SUPPRESSION_TIME Default is 1 minute. Increase to index less often. Unit is minutes. UPDATE_SUPPRESSION_LIMIT Forces update at X# of update requests. UPDATE_NAB_SUPPRESSION_TIME Undocumented. Default is 1 minute. Increase to update hidden NAB views less often. Unit is minutes. UPDATE_NAB_VIEWS_DISABLE Undocumented. Disables automatic updating of hidden NAB views. SERVER_NAMELOOKUP_NOUPDATE 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

Dig Deeper on Lotus Notes Domino Database Management



  • Favorite iSeries cheat sheets

    Here you'll find a collection of valuable cheat sheets gathered from across the iSeries/ community. These cheat ...

  • HTML cheat sheet

    This is a really cool cheat sheet if you're looking to learn more about HTML. You'll find just about everything you every wanted ...

  • Carol Woodbury: Security

    Carol Woodbury