Home Page for the TeradataForum
 

Archives of the TeradataForum

Message Posted: Mon, 20 Feb 2012 @ 15:49:49 GMT


     
  <Prev Next>   <<First <Prev Next> Last>>  


Subj:   Re: Find record position for Fastload/Multiload error
 
From:   td newsgroup

Hi,

according to the documentation you should find the record in question in the Source Seq field of the ET table.

"SourceSeq Data row number in the client file that Teradata Database was building when the error occurred"

"Error Isolation Procedure

The following procedure shows how to use the information from the error table to isolate the problem:

1 Check the DMLSeq field to find the statement being executed. It contains the sequence number 001.

2 Check the SMTSeq field. The sequence number 002 in this field means that the error occurred while executing the second statement after the first DML LABEL command, which is the UPDATE command in the example task.

3 Verify that the Teradata MultiLoad job script uses two DML LABEL commands-one for each IMPORT command.

4 Check the ImportSeq field. The value of 002 indicates that the error occurred while processing the second IMPORT command.

5 Check the ApplySeq field. The value of 001 indicates that the error occurred while processing the first APPLY function.

6 Check the meaning of the ErrorCode field. Error 2679, "The format or data contains a bad character" indicates a problem with the data from the client system.

7 Check the ErrorField field. The field3 indicates that the error occurred while building field3 of the target table.

8 Check the Teradata MultiLoad job script. It shows that field3 of the target table was being built from FIELD3 of the client data.

9 Note that the LAYOUT specification of the IMPORT command shows where the problem data is positioned within the row of the client data.

Since the script shows that the IMPORT command was loading file2:

- The error that occurred is known

- Which statement detected the error

- Which file has the error


10 Check the SourceSeq field. The value of 20456 indicates that the problem is with the 20,456th record of the file.


The problem is isolated, and can now be fixed.


Ulrich



     
  <Prev Next>   <<First <Prev Next> Last>>  
 
 
 
 
 
 
 
 
  
  Top Home Privacy Feedback  
 
 
Copyright for the TeradataForum (TDATA-L), Manta BlueSky    
Copyright 2016 - All Rights Reserved    
Last Modified: 15 Jun 2023