Teradata Parallel Data Pump

Chapter 2: Using Teradata TPump
Program Considerations
Table 20: Restrictions and Limitations on Operational Features and Functions (continued)
Operational Feature/Function
Date specification
Access logging
Primary Indexes and Partitioning
Column Sets
Restriction/Limitation
For dates before 1900 or after 1999, the year portion of the
date must be represented by four numerals (yyyy). The default
of two numerals (yy) to represent the year is interpreted to be
the 20th century, and must be overridden to avoid spurious
year information. If the table column defined as type DATE
does not have the proper format, the dates may not process
properly. The correct date format must be specified at the time
of table creation, for example:
CREATE TABLE tab (ADATE DATE*);
DEFINE a (char(10))
INSERT tab (ADATE = :a(DATE, FORMAT 'yyyy-mmdd'));
Unlike the MultiLoad and FastLoad utilities, access logging can
cause a severe performance penalty in Teradata TPump. This is
because Teradata TPump uses normal SQL operations rather
than a proprietary protocol, and if all successful table updates
are logged, a log entry is made for each operation. The primary
index of the access logging table may then create the possibility
of row hash conflicts.
Specify values for the partitioning column set when
performing Teradata TPump deletes and updates to avoid lock
contention problems that can degrade performance. Avoid
updating primary index and partitioning columns with
Teradata TPump to minimize performance degradation.
Termination Return Codes
When a Teradata TPump job terminates, it returns a completion code to the client system.
Table 21 lists the conventions used.
Table 21: Termination Return Codes
Code
Description
0 Normal completion
4 Warning
8 User error
12 Severe internal error
16 No message destination is available
Note: To avoid ambiguous or conflicting results, always use values greater than 20 when
specifying a return code with the LOGOFF command.
68 Teradata Parallel Data Pump Reference