Friday, 17 February 2017

How to set a OBIEE logging level

You might want to diagnose performance or data issues by setting a temporary log level for a query. You can enable query logging for a specific query by preceding your Select statement with the following:
Set Variable LOGLEVEL=n;
This instruction sets the loglevel system session variable only for this SQL.
See the following example:
Set Variable LOGLEVEL=5; select year, product, sum(revenue) from time, products, facts
For this query, the logging level of five is used regardless of the value of the underlying LOGLEVEL variable.
Available in 11G
You can find a default logging level in the option of the repository:

This option determines the default query logging level for the internal BISystem user.
A query logging level of 0 (the default) means no logging. Set this logging level to 2 to enable query logging for internal system processes likeevent polling and initialization blocks.
By setting the loglevel system session variable via an initialization block, you can control the loglevel of each user.
The loglevel must be an integer datatype
The session variable LOGLEVEL overrides a user's logging level. For example, if the Oracle BI Administrator has a logging level defined as 4 and LOGLEVEL is defined as default 0 (zero) in the repository, the Oracle BI Administrator's logging level will be 0.
§  In the Administration Tool, select Manage > Security (10g) or Identity (11g). The Security Manager dialog box appears.
§  Double-click the user's user ID. The User dialog box appears.
§  Set the logging level by clicking the Up or Down arrows next to the Logging Level field.


You cannot configure a logging level for a group.

No comments:

Post a Comment