Teradata Parallel Data Pump

Chapter 2: Using Teradata TPump
Program Considerations
The logged on user must have the appropriate user privileges on the tables. At the time the
BEGIN LOAD is initiated, SELECT privileges, as well as INSERT, UPDATE, and DELETE
privileges are required, depending on the DML statements specified in the current task.
Privileges must follow standard Teradata privilege rules. The kind of privilege required
depends on the kind of DML statements to be applied. Teradata TPump tasks require that the
target table is owned or access is available. Additional privilege for the target table is required,
depending on the DML command, INSERT, UPDATE, or DELETE. The additional privilege is
described for each statement type in later sections. No matter what kind of statement,
CREATE TABLE privilege on the databases where the error tables are going to be placed.
CREATE TABLE privilege for Teradata TPump to create a restart log table is also required. If
the restart log table specified for the support environment already exists, INSERT and
UPDATE privileges on the table are required.
In a Teradata TPump task, it is possible for more than one statement/data record combination
to affect a single row. If application of any statement/data record combination to a row would
produce an error, it is not applied, but all prior and subsequent error-free combinations
affecting the same row or other rows are applied.
Teradata TPump can guarantee the order of operations on a given row via the correct use of
the serialize option to specify the primary index of a given target table. When serialize is used,
operations for a given set of rows occurs in order on one session. Without serialize, statements
are executed on the first session available; hence, operations may occur out of order.
Assuming that the serialize option is in effect, note that the order in which DML statement or
host record pairings are applied to a given target row is totally deterministic; so too is the
order in which rows are applied to the target rows. Operations occur in exactly the same order
as they are read from the data source and, if there are multiple apply clauses, in order by apply
clause from first to last.
In addition to using serialize option in the BEGIN LOAD command, the SERIALIZEON
keyword can also be specified in the DML command, which lets serialization be turned on for
the fields specified. The SERIALIZEON keyword can be used in the DML command with the
SERIALIZE keyword in the BEGIN LOAD command. When this is done, the DML-level
serialization ignores and overrides the BEGIN LOAD-level serialization. In this case, the DML
command with the serialization option in effect will be serialized on the fields specified.
Operations generated from the first IMPORT statement take place before operations
generated from the second IMPORT.
Variables
This section contains information about the variables used in Teradata TPump.
Predefined System Variables
Avoid use of the prefix &SYS in user-defined symbols because the names of predefined utility
variables begin with the prefix. Table 15 contains a list of predefined system variables.
58 Teradata Parallel Data Pump Reference