Teradata Parallel Data Pump

Chapter 3: Teradata TPump Commands
BEGIN LOAD
where
Syntax Element
SESSIONS
number
threshold
ERRORTABLE
APPEND
NODROP
QUEUETABLE
Description
Keyword for the number of Teradata TPump sessions.
Number of sessions to be logged on for update purposes for Teradata
TPump.
A Teradata TPump task logs on and uses the number of sessions
specified. One additional session is used for performing various utility
functions.
There is no default value for number; it must be specified. Neither is
there a maximum value, except for system-wide session limitations,
which vary among machines.
Limiting the number of sessions conserves resources on both the
external system and Teradata Database. This conservation is at the
expense of a potential decrease in throughput and increase in elapsed
time.
Minimum number of sessions to be logged on for update purposes for
the utility.
When logging on sessions, if the limits are reached above the threshold
value, Teradata TPump stops trying to log on, and uses whatever
sessions are already logged on.
If the sessions run out before the threshold is reached, Teradata TPump
logs off all sessions, waits for the time determined by the SLEEP value,
and tries to log on again.
Optional keyword for identifying a database and error table.
Use a database name as a qualifying prefix to the error tables. Specifying
a database that is not the production database avoids cluttering the
production system with error tables. This means that because the
database should have been allocated a lot of PERM space, that space will
not have to be increased for all databases with tables involved in the
Teradata TPump task.
Caution: It is the user’s responsibility to ensure that the error table
sharing was meaningful. Two jobs targeting different tables
with different input record layouts cannot share the same
error table.
Specifies the existing error table.
If the specified error table does not exist, Teradata TPump will create it.
If the structure of the existing error table is not compatible with the
error table Teradata TPump creates, the job will run into an error when
Teradata TPump tries to insert or update the error table.
Specifies to retain (not DROP) the error table, even it is empty at the
end of a job.
NODROP can be used with APPEND to persist the error table or alone.
Selects the error table as a Queue Table.
Teradata Parallel Data Pump Reference 97