Restarting Fastload if we have error with the source data file

Tools & Utilities
Enthusiast

Restarting Fastload if we have error with the source data file

Hi,

I had encountered today a failure with fastload. There was some issue with the source file for which the fastload got paused. I corrected the data and restarted the run, but it didnt succeed.

I got the error:

**** 21:36:29 RDBMS error 2634: Existing ERROR table(s) or Incorrect

              use of unit_Inf  in  Fast Load operation.

**** 21:36:29 Delete the Error Tables or fix the BEGIN LOADING statement

I dropped the error tables, it then succeeded.

So my question is, do we have to drop the error tables every time we restart ?

Tags (1)
2 REPLIES
Enthusiast

Re: Restarting Fastload if we have error with the source data file

Remove the TPT checkpoints. That worked for me

Teradata Employee

Re: Restarting Fastload if we have error with the source data file

No, if everything is done correctly, you are actually NOT supposed to drop the error tables in order to restart a job that was paused. Dropping the error tables (and the row in the restart log table) will mean the job will start from the beginning.

Apparently, something was wrong with the error tables and the job could not be resumed. And thus you were instructed to drop them and start all over.

-- SteveF