Different Types of Tracing Levels In Informatica
The tracing levels can be configured at the transformation And/OR session level in informatica. There are 4 different types of tracing levels.
The different types of tracing levels are listed below:
Tracing levels:
None: Applicable only at session level. The Integration Service uses the tracing levels configured in the mapping.
Terse: logs initialization information, error messages, and notification of rejected data in the session log file.
Normal: Integration Service logs initialization and status information, errors encountered and skipped rows due to transformation row errors. Summarizes session results, but not at the level of individual rows.
Verbose Initialization: In addition to normal tracing, the 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, the 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. 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.
Configuring Tracing Levels:
At transformation level, you can find the Tracing Level option in the properties tab. Select the required tracing level. At session level, go to the Config Object tag and select the option Override Tracing.
Selecting Tracing Levels:
The question is which tracing level to use. If you want to debug the session, use the verbose data as it provides complete information about session run. However do not use this in tracing level in production. Because it will cause some performance issue as the integration service writes the complete information into the session log file.
In production use the normal tracing level. The normal tracing level is enough to identify most of the errors when a session fails. As the integration service writes less amount of data in the session log file, this tracing level wont cause any performance issue.
