|
|
|
|
|
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 Central have enabled a database option which automatically repairs tables that it finds corrupted, meaning most of these occurrences come and go with hardly any notice by end users. Though no action on the part of the administrators is required in these cases, administrators may wish to keep informed of any such happenings. Information is logged by the database server when such corruptions occur, and when they are automatically repaired. Look for this log information in the \mysql\data directory of your MOVEit Central server. It will be stored in a file named HOSTNAME.err, where HOSTNAME is the name of the server. A typical corruption detection and repair event will be 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 will need to repair the table manually. It is not necessary to stop the MOVEit Central service or the MySQL service during the manual repair process. In fact, 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
Once logged in, execute the CHECK TABLE command against the table you believe has been corrupted, like so:
CHECK TABLE stats;
This command will typically generate several lines of information. The last line will tell you the status of the table. If the CHECK response indicates the table needs to be repaired, issue the repair command like so:
REPAIR TABLE stats;
This may 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 will contain a status message of "OK".
If the manual repair process was unsuccessful after several tries, contact MOVEit support for assistance.