A restart log table, which contains restart information written during job runs, is required for any execution of the Update operator. Specify a restart log table in scripts with the LogTable attribute.
Restarts (as discussed in Staged Loading) are common during staged loading operations. When additional data is available after a job is paused, the job is restarted by submitting a second script that specifies the additional data. The Update operator recognizes the job as a restart, reads the restart log to determine the status of the job, then loads the additional file.
Restarts can also occur following any unexpected error on a database. For example, if a table runs out of available space during a load operation, the job terminates, the table is paused, and a checkpoint is recorded in the restart log. Pausing the job in this way allows you to manually increase the available space, if needed, then restart the job because the load operation can restart a job from the last checkpoint in the restart log.
If you do not specify a name for LogTable, the Update operator automatically creates a name of the log table as follow:
ttname_RL
wherettname is the name of the first target table.