In certain rare circumstances, malformed hits in a webserver log could cause Urchin 4 (primarily versions before 4.006) to crash and leave the database locked. Attempting to process further logs after this crash results in the following error:
ERROR: (7009-911-371) DB is locked - run sanitizer.At present, the only way to recover from this error is to delete the Urchin databases for that Profile for the affected month, and re-run the logs for that Profile for the entire month.
This can be accomplished by going to the data/reports/{profile-name} directory and remove all files with names that begin with year/month datestamp for this month. For example, if the affected database is for July 2002, remove all files that start with "200207". Once the files have been removed, re-process all the logs for that Profile for that month.