Informatica: Tracing Levels

The choice of Tracing Level is very important, as it defines the amount of detail the integration services writes in the session log about the transformation. Default Tracing Level: Normal

Tracing Level Normal

Description

Usage

Integration Service logs It is the Default Tracing initialization and status Level information, errors encountered and skipped rows due to transformation row errors. Summarizes session results, but not at the level of individual rows. Integration Service logs initialization information and error messages and notification of rejected data. Terse tracing level is selected to add a slight performance boost as it writes minimum of details to the session log when running a workflow containing the transformation. Change the tracing level to a Verbose setting only when you need to debug a transformation that is not behaving as expected.

Terse

In addition to normal tracing, Verbose Initialization Integration Service logs additional initialization details; names of index and data files used, and detailed transformation statistics. Verbose Data In addition to verbose initialization tracing, Integration Service logs each row that passes into the mapping. Also notes where the Integration Service truncates string data to fit the precision of a column and provides detailed transformation statistics. Allows the Integration Service to write errors to both the session log and error log when you enable row error logging. When you configure the tracing

level to verbose data, the Integration Service writes row data for all rows in a block when it processes a transformation.