Teradata Parallel Data Pump

Chapter 3: Teradata TPump Commands
BEGIN LOAD
Syntax Element
LATENCY
seconds
NOTIMERPROCESS
minutes
SERIALIZE ON/OFF
PACKMAXIMUM
Description
Keyword for flushing stale buffers.
Note: When using the Teradata TPump latency option with Named
Pipe Access Module, need_full_block = no option should be added in the
Named Pipe Access Module initialization string.
Flushing threshold based on number of seconds oldest record has
resided in buffer.
LATENCY cannot be less than one second.
If the SERIALIZE parameter is set to OFF, only the current buffer can
possibly be stale. If SERIALIZE is ON, the number of stale buffers can
range from zero to the number of sessions.
Keyword to tell Teradata TPump not to fork a child process as a timer
process.
When a child process is forked, the SIGUSR2 signal notifies the parent
process when the latency period expires. When a child process is not
forked, the SIGALRM signal notifies the Teradata TPump process when
the latency period expires. A child process is necessary for the latency
function to work properly on the UNIX platforms when the MQSeries
Access Module is used.
Number of minutes to wait between unsuccessful logon attempts due to
session limits errors on Teradata Database or CLIv2.
If SLEEP is not specified, the default between unsuccessful logon
attempts is 6 minutes.
Keyword to set the state (ON/OFF) of the serialization feature which, if
ON, guarantees that operations on a given key combination (row) occur
serially.
If SERIALIZE is not specified, the default is OFF.
This feature is meaningful only when a primary key for the loaded data
is specified by using the KEY option of the FIELD command.
Serialization must be set to OFF if the .TABLE command is used and the
target table is a NoPI table.
To ensure data integrity, the SERIALIZE parameter defaults to ON in
the absence of an explicit value if there are upserts in a Teradata TPump
job.
Keyword requesting Teradata TPump to dynamically determine the
maximum possible PACK factor for the current load.
Maximum value is 2430.
Displayed in message UTY6652, the value thus determined should be
specifically used on subsequent runs, as the use of PACKMAXIMUM
requires iterative interactions with the database during initialization to
heuristically determine the maximum possible PACK factor.
Note: Since the maximum packing factor has changed from 600 to
2430, it will take a longer time for Teradata TPump to test the packing
factor if PACKMAXIMUM is specified.
102 Teradata Parallel Data Pump Reference