Group Discounts available for 3+ students and Corporate Clients

Error Operations in TeraData

Error operations


.DML Lable{Lable Name}



Do Insert For{missions update}Rows







The value which loaded to the data base



The value which skipped before loaded to the database




DML Lablel

A name to the DML Operation to differentiate from one to other


Multi load Tables

For every table it Require ET,UV,WT Table for every Import task, it Requires a log table


ET Table

  1. It takes the errors that occur in AQuision phase
  2. It contains primary index overflow error, that occur in application phase



The ET Table contains the below fields

    • Sequence Number that identify the import command where
    • Sequence Number for the DML statement invalid the error
    • Sequence of the DML statement being carried out when the error was discovered.
  4. Applyseq:
    • Sequence Number that tells which Aplly clause was Running when the error occurred
  5. Sourceseq
    • The Record number in input file which having error




UV Table

it contains the error that occur in Application phase:

a)unique violation error

  1. b) constrain error
  2. c) overflow error on column other than PI




Import Seq

Dml Seq

Smt Seq

Apply Seq

Source Seq


DBC error cod

DBC errorcod

DBC error Field


Work Table

It contain DML Task Information

The input data that is Ready to Apply the amp1

Create multi set table w T c Parties


Field, Var Byte(64)Formal ’x(64)’NOT Null

) primary Index(Field);


Log Table

2We need to specify this explicitly

2Mainly it is Import the time of Restorable the script



“At TekSlate, we are trying to create high quality tutorials and articles, if you think any information is incorrect or want to add anything to the article, please feel free to get in touch with us at, we will update the article in 24 hours.”

0 Responses on Error Operations in TeraData"

Leave a Message

Your email address will not be published. Required fields are marked *


Please Enter Your Details and Query.
Three + 6