Mark/Ignore Options for Error Tables
The Stream and Update operators allow you to MARK or IGNORE various types of errors
generated during execution of a job. Rows for error types designated as IGNORE will
thrown away. Rows for error types designated as MARK are retained in the error table.
Note: For Update operator, MARKed rows will only appear in ErrorTable 2, the application
error table. Stream operator has only a single Error Table and MARKed rows will appear
For Stream and Update operators:
DUPLICATE ROWS (for both insert and update operations)
DUPLICATE INSERT ROWS (for insert operations)
DUPLICATE UPDATE ROWS (for update operations)
MISSING ROWS (both update and delete operations)
MISSING UPDATE ROWS (for update operations)
MISSING DELETE ROWS (for delete operations)
For Stream operator only:
EXTRA ROWS (for both update and delete operations) [default]
EXTRA UPDATE ROWS (for update operations)
EXTRA DELETE ROWS (for delete operations)
Enter MARK or IGNORE and the affected row type from the list above immediately following
the INSERT, UPDATE, or DELETE statement in the APPLY statement. MARKed items are added
to the error tables.
Note: If neither option is specified in the APPLY statement, MARK is the default condition.
For details, see “APPLY Statement” in Teradata Parallel Transporter Reference.
Consider the following when deciding whether to MARK or IGNORE a particular error
If you need to know about each duplicate, missing or extra row that is encountered
during the job, use MARK to send them to the error tables.
Saving row data and storing it in the error table may slightly degrade overall Teradata
PT job performance. When job performance is important and the data is likely to include
a high percentage of duplicate, missing, or extra rows, it may be best to IGNORE them.
Even if minor job performance degradation is not a concern, using MARK to save all
of the duplicate, missing, or extra rows may create so much clutter in the error table
that it is difficult to read.
You may need to run a job several times before you can determine the best use of MARK