Reject File in Informatica

Integration Service may create reject file when we run a session. So that we can rectify the reason of rejection and correct the code and run it again with the right code. Thanks to the people who developed the Informatica Power Center, they know that some people will come up with the wrong code or wrong data.

Then when and why the reject file will create

Reject file will create when

        1.       The field contains NULL values

        2.       When Numeric data exceeded the specified precision or scale for the column.

        3.       String data exceeded a specified precision for the column, so the Integration Service truncated it.

Integration Service create reject files for each instance in the mapping. By default the reject file is created at the $PMBadFileDir process variable directory. But we can change the directory path by changing value in the mapping tab for the session.

One important point is that Integration Service will create multiple reject files if we run a session with multiple partitions. Integration Service will create one reject file for each partition.

How reject file look like?

 When we open a reject file,( we can use any text editor) we will get rows of data rejected by the writer or target database. Even though the error occurred in only one column of a row, Integration Service will write the entire row in the reject file.

But the question is how we will quickly identify which column is responsible for the rejection?

The answer is, Integration Service adds row indicator and column indicator so that we can find out the reason of rejection.

Row Indicator: The firs column in each row in the reject file is row indicator. The row indicator defines the row was marked for insert, update, delete or reject.

Row Indicator	Meaning	Rejected by
0	Insert	Writer or target
1	Update	Writer or target
2	Delete	Writer or target
3	Reject	Writer
4	Rolled-back insert	Writer
5	Rolled-back update	Writer
6	Rolled-back delete	Writer
7	Committed insert	Writer
8	Committed update	Writer
9	Committed delete	Writer

Column Indicator: we can find column indicator, after every column of data. The column indicator defines whether the column contains valid, overflow, null, or truncated data.

Column Indicator	Type of data	Writer Treats As
D	Valid data.	Good data. Writer passes it to the target database. The target accepts it unless a database error occurs, such as finding a duplicate key.
O	Overflow. Numeric data exceeded the specified precision or scale for the column.	Bad data, if you configured the mapping target to reject overflow or truncated data.
N	Null. The column contains a null value.	Good data. Writer passes it to the target, which rejects it if the target database does not accept null values.
T	Truncated. String data exceeded a specified precision for the column, so the Integration Service truncated it.	Bad data, if you configured the mapping target to reject overflow or truncated data.