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

Row-level Error Processing

Row-level Error Processing

When you write data to a Teradata target, you can configure how Teradata PT API treats duplicate rows, missing rows, and extra rows.

Duplicate Rows

You can configure how Teradata PT API handles duplicate rows when it tries to insert or upsert rows in the target table.
You can select one of the following values:
  • None. If Teradata PT API receives a row marked for insert or upsert that causes a duplicate row in the target table, Teradata PT API does not write the row to the error table and does not mark it as an error row in the workflow log.
  • For Insert. If Teradata PT API receives a row marked for insert that exists in the target table, Teradata PT API writes the row to the error table and marks it as an error row in the workflow log.
  • For Update. If Teradata PT API receives a row marked for update that causes a duplicate row in the target table, Teradata PT API writes the row to the error table and marks it as an error row in the workflow log.
  • Both. If Teradata PT API receives a row marked for insert or upsert that causes a duplicate row in the target table, Teradata PT API writes the row to the error table and marks it as an error row in the workflow log.

Missing Rows

You can configure how Teradata PT API handles rows that do not exist in the target table when it tries to update or delete rows.
You can select one of the following values:
  • None. If Teradata PT API receives a row marked for update or delete but it is missing in the target table, Teradata PT API does not write the row to the error table and does not mark it as an error row in the workflow log.
  • For Update. If Teradata PT API receives a row marked for update but it is missing in the target table, Teradata PT API writes the row to the error table and marks it as an error row in the workflow log.
  • For Delete. If Teradata PT API receives a row marked for delete but it is missing in the target table, Teradata PT API writes the row to the error table and marks it as an error row in the workflow log.
  • Both. If Teradata PT API receives a row marked for update or delete but it is missing in the target table, Teradata PT API writes the row to the error table and marks it as an error row in the workflow log.

Extra Rows

You can configure how Teradata PT API marks error rows when it tries to update or delete multiple target table rows.
You can select one of the following values:
  • None. If Teradata PT API receives a row marked for update or delete that affects multiple rows in the target table, Teradata PT API does not write the row to the error table and does not mark it as an error row in the workflow log.
  • For Update. If Teradata PT API receives a row marked for update that affects multiple rows in the target table, Teradata PT API writes the row to the error table and marks it as an error row in the workflow log.
  • For Delete. If Teradata PT API receives a row marked for delete that affects multiple rows in the target table, Teradata PT API writes the row to the error table and marks it as an error row in the workflow log.
  • Both. If Teradata PT API receives a row marked for update or delete that affects multiple rows in the target table, Teradata PT API writes the row to the error table and marks it as an error row in the workflow log.
This attribute is available only for the Stream system operator.


Updated October 05, 2018