Restart Paused FastLoad Job After Database Failure | Teradata FastLoad - After a Database Failure - FastLoad

Restarting a Teradata FastLoad job that was paused because of a database failure depends on the operational database configuration when it returns to service:

• If the configuration of the restarted database is exactly the same as it was when Teradata FastLoad was invoked, then Teradata FastLoad restarts the job automatically. In this case, if the Teradata FastLoad job was paused in the end loading phase, the database resumes processing at the same place it was stopped.
  If the Teradata FastLoad job was paused in the loading phase, the database resumes processing:

  • At the last checkpoint if the BEGIN LOADING command specified the checkpoint option.
  • At the beginning if the BEGIN LOADING command did not specify the checkpoint option.
    If the Teradata FastLoad job uses an INMOD routine, the routine must be able to handle restarts and checkpoints when restarted in the loading phase.
• If the configuration of the restarted database is different from the way it was when Teradata FastLoad is invoked, then Teradata FastLoad does not restart the job. In this case, to restart and continue with the paused Teradata FastLoad job, must reestablish the original database configuration. If this is not possible, then the Teradata FastLoad job must perform the following tasks:
  1. Delete the Teradata FastLoad table and error tables.
  2. Resubmit the Teradata FastLoad job, from the beginning, as a new job.