Teradata Parallel Data Pump

Chapter 4: Troubleshooting
Teradata TPump Performance Checklist
7 The ErrorField field of the error row shows that the error occurred while building field3 of
the table.
8 The script then shows that the error occurred when field3 was being built from :FIELD3 in
the client data.
9 The LAYOUT clause in the script shows where the problem data is positioned within the
row coming from the client.
10 The script shows that the IMPORT clause with the error was loading file2, and indicates
what error occurred, which statement detected the error, and which file has the error.
11 The SourceSeq field of the error table pinpoints the problem location in the 20456th
record of this file. The problem is isolated and can now be fixed.
Most problems in the error tables do not require as much research as this example. This
error was selected in order to use all of the information in the error table. As a rule, only
one or two error table items need to be looked at to locate and correct problems.
Teradata TPump Performance Checklist
The following checklist helps to isolate and analyze Teradata TPump performance problems
and their causes.
• Monitor the Teradata TPump job using the Monitor macros. Determine whether the job is
making progress.
• Check for locks using the Teradata Database Showlocks utility. Transaction locks can be
detected by checking for blocked Teradata utilities that use the performance monitor
feature of Teradata Database (Teradata Manager).
• Check table DBC.Resusage for problem areas (for example, data bus capacity or CPU
capacity at 100% for one or more processors).
• Avoid large error tables, if possible, because error processing is generally expensive.
• Verify that the primary index is unique. Nonunique primary indexes can cause severe
Teradata TPump performance problems.
202 Teradata Parallel Data Pump Reference