What are types of LOG LEVELS in ODI ?

Answer:-



The Log Level field value specifies a user-set level of severity for a specific Command Line and is used to determine which records will be retained in ODI Operator (the journal) after the execution post-processing clean-up operation.



7 levels of user-set values may be specified for the retention of the ODI journal records



ODI Log Level Description



0 –This will retain execution details ONLY in case of execution failure.



1 –This will retain only Session level details.Nothing will be displayed at Session Step, and Session Task level.



2, 3, 4 or 5 –These values are depending on those specified in the Procedure or Knowledge Module Command Line.



For example, if a Command Line is defined with a Log Level = 4, then the runtime information will be displayed in Operator (Journal) only if the user specifies a Log Level of 4 or 5 (command line parameter “-V=4” or value specified in the Agent and Context selection popup Window).



6 — Starting with ODI 11.1.1.6.0, an additional Log Level has been introduced in order to allow the tracking and debugging of Variables, and Sequence values.

With Log Level 6, when reviewing the execution results in ODI Studio > Operator or ODI Console, dig into the “Variables and Sequence Values” section of the Session Step or Session Task editor to view the current value of a Variable or Sequence.



Independent of the precise log level which is used, ODI always writes the complete Session, Step and Task information to the Repository execution-related tables. During the entire execution runtime these details are visible within Operator.



If the process is successful, all Task log records for which the log level value is less than (or equal to) the one set at execution launch time will be saved in the ODI Work Repository at the end of execution and will be visible within Operator.



If the process interrupts with an error message during execution, then, regardless of the Log Level value, all Task records will be retained in the ODI Work Repository and will be visible within Operator.



A Log level value of 5 or 6 will retain all records in ODI Operator at Session termination regardless of termination status of the process.



Impacts of the choice of log level values on ODI runtime performance?

The use of log levels inferior to 5 has an impact on execution performances.

This is explained by the fact that ODI writes to the Repository tables during session runtime.

Subsequently, after the process completes, ODI performs a number of delete instructions in order to retain only the desired logs records.



Therefore:



Yes, using log levels inferior to 5 will result in storing less data in the ODI Repository tables.

and No, this will not improve execution performances (the additional delete instructions addressed to the database require additional processing time and network communication bandwidth).



Best performance fit:



Use a log level of 5

Then either delete the desired level of detail at another moment of day, for example, when the use of database, network and ODI Agent resource are at low peak period.

This can be performed either :

• manually


• using the OdiPurgeLog tool at predetermined times