After a Job Abort or Client System Failure
Restarting a Teradata MultiLoad job that was either aborted or stopped after a client system failure or restart depends on whether the Teradata MultiLoad job stopped during the application phase.
The BEGIN MLOAD command is the first step in a multiple-step job. If commands are re-executed that modify tables or databases involved in the Teradata MultiLoad job, they can become corrupted.
Note: Do not modify or drop the Teradata MultiLoad restart log table or any of the work tables or error tables before restarting the Teradata MultiLoad job.
Note, however, that the restart procedure depends on the severity of the situation that stopped the job:
// EXEC MLOAD, PARM='OVERRIDE'
.BEGIN MLOAD . . . ;
The BEGIN MLOAD command must identify all of the target tables, work tables, and error tables of the original job, and they must all be intact and not corrupted. When submitting the abbreviated script, Teradata MultiLoad uses the checkpoint markers in the work tables to restart the task at the point it stopped in the application phase.