Table of Contents

Search

  1. Preface
  2. Introduction to PowerExchange Bulk Data Movement
  3. PowerExchange Listener
  4. Adabas Bulk Data Movement
  5. Datacom Bulk Data Movement
  6. DB2 for i5/OS Bulk Data Movement
  7. DB2 for Linux, UNIX, and Windows Bulk Data Movement
  8. DB2 for z/OS Bulk Data Movement
  9. IDMS Bulk Data Movement
  10. IMS Bulk Data Movement
  11. Microsoft SQL Server Bulk Data Movement
  12. Oracle Bulk Data Movement
  13. Sequential File Bulk Data Movement
  14. VSAM Bulk Data Movement
  15. Writing Data with Fault Tolerance
  16. Monitoring and Tuning Options

Bulk Data Movement Guide

Bulk Data Movement Guide

Reject Files with Fault Tolerance

Reject Files with Fault Tolerance

PowerExchange creates reject files on the target platform. The reject files contain the rows of data that the writer did not write to targets.
The writer might reject a row that violates a database constraint or that contains a field with truncated or overflow data if the target database is configured to reject such data.
You can read a reject file by using a text editor that supports the reject file code page.
In a reject file, the row and column indicators provide information that is noteworthy. For example, an attempt to insert a duplicate key generates the following reject file entry:
23,D,FAILNAME,D,1,D
To identify the reason why rows were rejected, review the column indicators and consult the session log.
PowerCenter reject files are also created during a session that uses PowerExchange asynchronous write. However, the PowerCenter reject files are empty. The rejected data is written to the PowerExchange reject files.

0 COMMENTS

We’d like to hear from you!