Error Operations in TeraData

Error operations

.DML Lable{Lable Name}

{Mark/IGNORE}duplicate{Insert/update}Rows

{Mark/IGNORE}MISSING{Insert/update}Rows

Do Insert For{missions update}Rows

Field

The value which loaded to the data base

Filler

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

Structure

The ET Table contains the below fields

1. IMPORTSEQ

   • Sequence Number that identify the import command where

2. DMLSEQ

   • Sequence Number for the DML statement invalid the error

3. SMTSEQ

   • 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

Unique

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

We need to specify this explicitly

Mainly it is Import the time of Restorable the script