Reject rows logged

[bsellick]

Just curious if anyone has found a way to avoid having rejected rows (i.e. coming out of an update strategy) not get written to the session log.

I did try setting the property on the update strategy to both "forward rejected" and that option unchecked. In both cases, rejects got logged.

The way I'm getting around this at the moment is to mark rows as UPDATE rather than REJECT (I only need to worry about INSERT in this mapping) and then use a router to only send INSERT through to the target. I'd prefer not to do this.

I'm using Informatica v7.x.

Thanks

 

[bsellick]

I get to answer my own question. Found this on Informatica knowledgebase:

Problem Description:
When using an Update Strategy Transformation does checking the forward rejected rows option cause the rows to be written to the session log or the reject file. Also if DD_REJECT is assigned to the row how does it affect what is done with the row.

Solution:
This chart summarizes results for rows assigned a DD_REJECT status in the update strategy transformation:


Case 1 Case 2 Case 3 Case 4
* Options
Forward Reject Rows Checked? Yes No Yes No
Session Logging Level normal normal terse terse

* Results
Rejected records written
to bad file? Yes No Yes No
Reject info in session log? Yes Yes Yes No
Session summary includes
failed record count? Yes No Yes No

NOTE:
The only way to prevent the DD_REJECT rows from being written to the session log is to Uncheck the Forward Reject Rows option and set the logging level in the session to terse.