Table of Contents

Search

  1. Preface
  2. Introduction to PowerExchange for Teradata Parallel Transporter API
  3. PowerExchange for Teradata Parallel Transporter API Configuration
  4. PowerExchange for Teradata Parallel Transporter Connections
  5. PowerExchange for Teradata Parallel Transporter API Data Objects
  6. PowerExchange for Teradata Parallel Transporter API Mappings
  7. Teradata Parallel Transporter API Run-time Processing
  8. Data Type Reference

PowerExchange for Teradata Parallel Transporter API User Guide

PowerExchange for Teradata Parallel Transporter API User Guide

Error Tables

Error Tables

Teradata writes rejected data to error tables ErrorTable1 and ErrorTable2.
ErrorTable1 contains data that was rejected for the following reasons:
  • Data conversion errors
  • Constraint violations
  • Access Module Processor configuration changes
ErrorTable2 contains data that was rejected for the following reasons:
  • Unique primary index constraint violations
  • Load driver job acquisition phase errors
When you configure a Teradata mapping, you can enter a name for each error table. You can create the error tables in any database. By default, the error tables are stored in the default database. Choose where you want to create the error tables when you configure a mapping to load to Teradata.
When a mapping fails, see the error tables for more information about the errors. Before you run the mapping again, drop the error tables or enter different table names in the data object operation write properties. Otherwise, the mapping fails.
The following table describes the data object operation write properties that allow you to specify error table names:
Property
Description
Error Database
Name of the database that stores the error tables. If you do not enter an error database name in the data object operation write properties, Teradata PT API stores the error tables in the database you specify in the connection object.
Error Table Name1
Name of the first error table.
If you do not specify a name for the first error table, the Data Integration Service uses the name
<error_database>.INFA_ET1_<number>
. The table name appears in the mapping log.
Error Table Name2
Name of the second error table.
If you do not specify a name for the second error table, the Data Integration Service uses the name
<error_database>.INFA_ET2_<number>
. The table name appears in the mapping log.


Updated October 05, 2018