The fixup that didn't
Tags: Lotus Domino fixup corrupt database 8.5 8.5.x
After a problem at a customer with a corrupt database which could not be fixed by the fixup task, (the database kept reporting that a consistency check was in progress) one of my coworkers contacted IBM who eventually gave him the following bit of information
There is a known issue where fixup does not delete the bad document: SPR # TSOE8KCJCP - Fixup does not repair corrupt database
Setting the following ini variable should allow fixup to continue on the error.
DEBUG_FIXUP_DELETE_ERRORS_INCLUDE=2B8,227
The SPR is a regression that was introduced in 8.5.1 and the last known release where it worked is 8.5 . So if the workaround does not work, try to run fixup on a 8.5 server to see if the database is cleaned up.
After a problem at a customer with a corrupt database which could not be fixed by the fixup task, (the database kept reporting that a consistency check was in progress) one of my coworkers contacted IBM who eventually gave him the following bit of information
There is a known issue where fixup does not delete the bad document: SPR # TSOE8KCJCP - Fixup does not repair corrupt database
Setting the following ini variable should allow fixup to continue on the error.
DEBUG_FIXUP_DELETE_ERRORS_INCLUDE=2B8,227
The SPR is a regression that was introduced in 8.5.1 and the last known release where it worked is 8.5 . So if the workaround does not work, try to run fixup on a 8.5 server to see if the database is cleaned up.
