Restart Procedures
The procedure which is used and the Teradata FastLoad response to restarting a paused Teradata FastLoad job depends on the phase that the Teradata FastLoad job was in when it was paused.
Note: Generally, nothing needs to be done because processing after the END LOADING command is executed on the Teradata Database does not depend on Teradata FastLoad. However, if restarting the job in the end loading phase is required, see the following procedure.
1 Remove the CREATE TABLE statement and any DROP TABLE and DELETE statements from the Teradata FastLoad job script to prevent the restarted job from dropping the partially loaded Teradata FastLoad table or deleting the entries in the two error tables.
2 Invoke Teradata FastLoad to start the job. The Teradata FastLoad utility:
If, for example, the job had a checkpoint specification of 100, and the failure occurred at row 1100, the Teradata FastLoad response would be:
FastLoad RESTARTED
The last checkpoint was taken at row: 1100
FastLoad will now restart at row: 1101
Note: If the Teradata FastLoad job was paused during the loading phase and uses an INMOD routine, the INMOD routine must be able to handle restarts and checkpoints when restarted in the loading phase. Following a restart, Teradata FastLoad passes a status code of 2 or 4 to an INMOD routine that is participating in a load operation. The routine must adjust the record to be read to the position of the last checkpoint and, upon subsequent calls, send records to Teradata FastLoad.
1 Use the same LOGON command described in the preceding procedure.
2 Submit BEGIN LOADING and END LOADING commands, as in the following example:
LOGON dbc/sjn,music ;
BEGIN LOADING Fast_Table
ERRORFILES Error_1, Error_2 ;
END LOADING ;
Note: If a Teradata FastLoad job script is used to assemble these commands, make sure to delete the CREATE TABLE and any DROP TABLE and DELETE statements before restarting the job.