A LOGTABLE command is required for each invocation of Teradata TPump. Only a single LOGTABLE command is allowed for each execution. It must precede all environmental and application commands (other than RUN FILE and LOGON) in the input stream.
The specified table is used as the Teradata TPump restart log. It does not have to be fully qualified. If the table exists, it is examined to determine if this is a restart. When this is the case, a restart is done automatically. If the table does not exist, it is created and used as a restart log during this invocation of Teradata TPump.
The log table is maintained automatically by Teradata TPump. If this table is manipulated in any way, the restart capability is lost. The only action that should be taken is to DROP the log table; never attempt to delete rows from the table. The log table should not be dropped when the Teradata TPump job using that log table is running. If the log table is dropped during a job run, Teradata TPump will run into errors.
The default for the database name cannot be overridden with a DATABASE statement because it must come after LOGTABLE/ LOGON. Instead, the LOGTABLE dbname option must be used.
Teradata TPump allows a DELETE DATABASE statement because DELETE is a standard Teradata SQL function. This statement can delete the current restart log after it has been created, which terminates the job.