ADMINISTERING
When you restart a server, the server quickly searches for any unlogged databases that were modified but improperly closed because of a server failure, power failure, hardware failure, and so on. A few minutes after server startup is complete, the Fixup task then runs on these databases to attempt to fix any inconsistencies that resulted from partially written operations caused by a failure.
When users attempt to access one of these databases and Fixup has not yet run on the database, the users see the message This database cannot be opened because a consistency check of it is in progress. A similar Fixup process occurs when you restart a Notes® client.
Multiple Fixup tasks run simultaneously at server startup to reduce the time required to fix databases. The number of Fixup tasks that Domino® runs by default at startup is equal to two times the number of processors available on the server. Although this default behavior should be adequate in most circumstances, you can edit the NOTES.INI file to include the Fixup_Tasks setting. The actual number of tasks run is the smaller of the configured number of tasks that can run and the number of databases that require fixing. For example, if you set Fixup_Tasks to 4 but only one database requires fixing, then only one Fixup task runs.
Keep in mind that after you set up transaction logging, Fixup is not needed or used to bring databases back to a consistent state.
Use Domino Administrator to use any of these methods to run Fixup manually to fix a corrupted database. With each of these methods, you can customize how Fixup runs.
Related reference Fixup options Fixing corrupted databases