Overload of session log in informatica

Question

I have a mappig to update certain columns in a table. Only 10% or less records should get updated. The remaining records should be rejected by the informatica.

The mapping works just fine if not for all the records getting logged into the session log file. Is there a way to prevent this other than using the filter transformation? I am aware this can be eliminated with a filter transforamtion. But just wanted to check if there is any simpler approach like selecting an option or something.

Answer 1

Change the tracing level to Terse - you can configure it for the update strategy transformation transformation or for the entire session (Config Object / Override tracing).

Answer 2

If you are using Update Strategy Transformation in your mapping then there is a property 'ForwardRejectedRows'. By default this property is checked, just un-check this property then the integration service drops rejected rows and no details will be written in the bad file but details will be passed to session log file.
Tracing level is also a very good option to minimize the tracing details. At session level set the trace as NONE and in Tranformations use Terse as tracing level.