Teradata Parallel Data Pump

Chapter 2: Using Teradata TPump
Writing a Teradata TPump Job Script
Many CLI and Teradata Database errors generate return codes of 12. For Teradata Database
errors that can be corrected and resubmitted, Teradata TPump tries up to 16 times to resubmit
and, at the end of this process, returns a code of 12. Many CLI and Teradata Database errors
generate the return code of 12, except for:
• Errors on Teradata SQL statements outside of the Teradata TPump task (before the BEGIN
LOAD command or after the END LOAD command). Teradata TPump ignores these
errors, which display error messages but do not cause early termination, nor generate
Teradata TPump return codes.
• Retryable errors or errors caused by Teradata Database restarts.
Writing a Teradata TPump Job Script
This section describes the contents of a Teradata TPump job script and explains how to write
one.
Definition
Caution:
The Teradata TPump job script, or program, is a set of Teradata TPump commands and
Teradata SQL statements that alter the contents of the specified target tables in Teradata
Database. These commands and statements:
• Insert new rows
• Update some or all of the contents of selected existing rows
• Delete selected existing rows
Each Teradata TPump job includes a number of support commands that establish and
maintain the Teradata TPump support environment, and a number of task commands that
perform the actual database insert, update, or delete operations. These commands and
statements identify and describe the input data to be applied to the target table, and then place
that data into the target table. These activities may commence anytime after configuring the
program as described in “Teradata TPump Support Environment” on page 37.
In the event of a client failure, the identical script must be resubmitted in order to restart. If
the script is edited, a restart will not be permitted.
Script Writing Guidelines
The following script writing guidelines will help write a Teradata TPump job script:
• A script may contain up to four IMPORTs (tasks), delimited by a leading BEGIN LOAD
command and a trailing END LOAD command.
• The BEGIN LOAD command specifies the number of sessions and establishes a number of
controlling parameters.
The BEGIN LOAD command also specifies the error table, and is the only table specified.
An optional qualifying database name may also be specified. This database name may be
Teradata Parallel Data Pump Reference 69