Previous Topic

Next Topic

Book Contents

Book Index

MySQL Database

If database errors have occurred and you are using MySQL as the database engine, there are steps you can take to repair the database.

Automatic Repair

Recent versions of MOVEit Automation have enabled a database option that automatically repairs tables that it finds corrupted. This means that most of these occurrences happen with little notice by end users. Although no action on the part of the administrators is required in these cases, administrators might want to keep informed of any such happenings. Information is logged by the database server when such corruptions occur, and when they are automatically repaired.

This log information is located in the \mysql\data directory of your MOVEit Automation server. It is stored in a file named HOSTNAME.err, where HOSTNAME is the name of the server. A typical corruption detection and repair event is logged like this:

041122 1:13:58 read_const: Got error 134 when reading table ./micstats/stats 
041122 1:14:00 read_const: Got error 134 when reading table ./micstats/stats 
041122 1:41:46 Warning: Checking table: './micstats/stats' 
041122 1:41:46 Warning: Recovering table: './micstats/stats'

Manual Repair

In the very rare case that the automatic table repair functionality fails, you must repair the table manually. It is not necessary to stop the MOVEit Automation service during the manual repair process.

The MySQL service MUST be running for this sequence of commands to succeed.

To manually repair a database table, open a command-prompt on your Central system and log in to the MySQL server using the root account created during the Central installation. To log onto the MySQL server using root, cd to your \mysql\bin directory and issue this command:

mysql --user=root --password=YOUR_ROOT_PASSWORD micstats

After you are logged in, execute the following CHECK TABLE command against the table you think has been corrupted:

CHECK TABLE stats;

This command typically generates several lines of information. The last line indicates the status of the table. If the CHECK response indicates the table needs to be repaired, issue the following repair command:

REPAIR TABLE stats;

This might take several minutes, depending on the size of the table, and generate several lines of output. If the repair was successful, the last line of output contain a status message of OK.

If the manual repair process is unsuccessful after several tries, contact MOVEit support for assistance.