|
|
|
|
|
Normally, the statistics database operates silently, behind the scenes of MOVEit Automation, and requires no active maintenance on the part of the administrator to operate. Rarely, however, one or more database tables can become corrupted, which might prevent MOVEit Automation from successfully logging task run information. These corruptions are often caused by unexpected reboots, such as during a power failure. They can also occur when backup programs make copies of database table files while the database server is running. When a database table is corrupted, it can no longer be accessed by the database server until it has been repaired.
If you think you have had, or may be having a database corruption problem, first check the log output. MOVEit Automation accesses the database several times during a typical task run, and when serious database problems occur, they are always written to the running log, which is accessible from MOVEit Automation Admin and from the local system. Here is an example of a table corruption error that would be found in the log:
Task "My Task": Could not log task end: [TCX][MyODBC]Can't open file: 'stats.MYD'. (errno: 145)