Teradata Parallel Data Pump

Chapter 3: Teradata TPump Commands
LOGTABLE
LOGTABLE
Purpose
Caution:
The LOGTABLE command identifies the table to be used for journaling checkpoint
information required for safe, automatic restart of the Teradata TPump support environment
in the event of a client or Teradata Database hardware platform failure.
The LOGTABLE command is used in conjunction with the LOGON command, both of which
are required. Both LOGON and LOGTABLE may appear in any order. The ACCEPT and SET
commands are valid commands preceding LOGON and LOGTABLE commands. If LOGON is
entered first, a warning is returned that the LOGTABLE is required.
Do not share the restart log table between two or more Teradata TPump jobs. Each Teradata
TPump job must have its own restart log table to ensure that it runs correctly. If a distinct
restart log table for each Teradata TPump job is not used, the results are unexpected. In
addition, one or more of the affected jobs may not be able to restart.
Syntax
.LOGTABLE
dbname.
tname
;
3021A029
where
Syntax Element
dbname
tname
Description
(Optional) Database name under which the log table exists
The default is the database name associated with the username specified in the
LOGON command. Teradata TPump searches for the table (tname) in that
database unless another database name is specified in this option.
Identifier for the restart log table
Usage Notes
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.
Teradata Parallel Data Pump Reference 171