Go to the first, previous, next, last section, table of contents.


Repairing a damaged database

Starting from THOR 2.4, a script for repairing the database has been included. Look for "ValidateThor" in the THOR bin/ directory. Note the following about this procedure:

- Only run ValidateThor after a reboot.
- For the best stability leave the system alone while validating.
- Be aware that validating the databases can take a long time.
- ValidateThor will perform a pack/purge after deleting corrupt messages.
- Use Sushi to avoid error requesters. Sushi can be found on AmiNet.

ValidateThor takes a single argument, namely the name of the system in
THOR to repair.  Example:

ValidateThor "News&Mail"

ALL can be used instead of the system to validate all systems in THOR.

Afterwards, you might consider doing the following steps:

-  Start  Thor, enter the system and set the view ALL mode.  Go trough
all  conferences  to  see if there are any messages in the messagelist
window  that  are  marked  with *BAD* *DATA* (These may show up on the
last  messages  in  the  list.).  Multiselect (with the shift key) all
messages  with  "*BAD  DATA*" or "Failed to get message data" and then
select Delete msgs from the menu.

If  this do not help, try to delete the offending messages by hand and
pack/purge the conference.


Go to the first, previous, next, last section, table of contents.