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.