16.20 - Correcting Stream Errors - Parallel Transporter

Teradata® Parallel Transporter User Guide

Parallel Transporter
Release Number
August 2020
English (United States)
Last Update

Following is an abbreviated Stream operator task, an error table listing, and a procedure for determining the cause of the error. The task example includes only one DML group consisting of two DML statements, an INSERT statement, and an UPDATE statement, for a complete Stream operator job.

The example procedure, below, uses all of the error information from the error table. In most cases, you can determine the cause by evaluating only one or two columns of the error table entry. The example uses the following APPLY statement to create error tables:

UPDATE table2 SET field3 = :FIELD3 WHERE field4 = :FIELD4;'

Task Example

In the following task example, the Sequence Type and Number columns are the type and number assignments for each statement. The Statement column shows the actual Stream operator job statements.

Task Example 
Sequence Statement
Type Number
DML 001
UPDATE table2 SET field3 = :FIELD3 WHERE field4 = :FIELD4;'
STMT 001
STMT 002
UPDATE table2 SET field3 = :FIELD3 WHERE field4 = :FIELD4;

The following table shows an error in the first error table created by the above task.

DataSeq DMLSeq SMTSeq SourceSeq ErrorCode ErrorField
002 001 002 20456 2679 000

Use the following procedure to evaluate the error information and isolate the problem:

  1. Check the DMLSeq field to find the DML group. It contains the sequence number 001.
  2. Check the STMTSeq field. The sequence number 002 in this field means that the error occurred while executing the second DML statement, which is the UPDATE statement in the example task.
  3. Verify that the Stream operator job script uses two DML statements in the first DML group (because DMLSeq was 001).
  4. Check the DataSeq field. The value of 002 indicates that the error occurred while processing a row from the second input data source. (The input data source sequence is determined by Teradata PT.)
  5. Check the meaning of the ErrorCode field. Error 2679, “The format or data contains a bad character,” indicates a problem with the data from your client system.
  6. Because the script shows that the UPDATE statement was loading table2, you now know:
    • What error occurred
    • Which statement detected the error
    • Which input data source has the error
  7. Check the SourceSeq field. The value of 20456 indicates that the problem is with the 20,456th record of the input data source.
  8. Fix the problem.