Teradata Parallel Data Pump

Chapter 1: Overview
The Teradata TPump Task
Macros
The use of macros slightly complicates the privileges for Teradata TPump. The remaining
privileges necessary to run a Teradata TPump job have two different scenarios:
• When a Teradata TPump macro is placed in the same database as the table which it affects,
required rights are INSERT/UPDATE/DELETE on the table affected, corresponding to the
DML executed.
• When a Teradata TPump macro is placed in a different database from the table it affects,
required rights specify that the database where the macro is placed must have INSERT/
UPDATE/DELETE, WITH GRANT in the table affected, corresponding to the DML
executed. The EXECUTE MACRO must also be located on the database where the macro
is placed.
Note that when the Teradata TPump job uses EXEC to directly specify a macro, the privileges
scenarios are the same, except that the CREATE/DROP MACRO privilege is not required since
the macro exists both before and after the job.
Tables
The corresponding INSERT, UPDATE, or DELETE privilege must exist for each table to be
changed by the Teradata TPump task. Multiple tables can be targeted by a single Teradata
TPump job.
The BEGIN LOAD command invokes Teradata TPump to execute task processing. Any
statement of this task applies each matching imported data record to each of its target table
rows having the specified index value. Teradata TPump supports all table types. Unlike
MultiLoad, there are no forbidden index types. Thus, the tables may be either empty or
populated, as well as being either with or without secondary indices.
All required data is imported; none is obtained from tables already existing in Teradata
Database. No statement of an IMPORT task may make any reference to a table or row other
than the one affected by the statement.
All INSERT statements, when considered in conjunction with each applicable imported
record, must explicitly specify values for all columns except those for which a default value
(including null) is defined. All UPDATE and DELETE statements, when considered in
conjunction with each applicable imported record, must explicitly specify values for all
columns of the primary index. In order to fulfill this requirement for UPDATE and DELETE
statements, a series of ANDed terms of either form must be supplied:
or
column_reference = colon_variable_reference
column_reference = constant
Teradata TPump does not process UPDATE and DELETE statements that contain ORed terms
because Teradata TPump must hash the imported records with a value from the import file
(or with a NULL). Any attempt to use an OR with these statements causes Teradata TPump to
fail. To work around this, create two separate DML statements and apply them conditionally.
Teradata TPump imposes some restrictions on the updates of an IMPORT task. It rejects
updates that try to change the value of the primary index of a row, but accepts even reflexive
Teradata Parallel Data Pump Reference 35