Logging Level

What is logging level?
Where can you set logging levels?

You can enable logging level for individual users; you cannot configure a logging level for a group.


Typically logging is set to enable some kind of debug or tuning exercise to take place. There is a slight overhead of writing the logging, so disabling this feature in production is probably a good idea.

Set the logging level based on the amount of logging you want to do. In normal operations, logging is generally disabled (the logging level is set to 0). If you decide to enable logging, choose a logging level of 1 or 2. These levels are designed for use by OBIEE administrators.


Level 0

• No logging.

Level 1

• Logs the SQL statement issued from the client application.
• Logs elapsed times for query compilation, query execution, query cache processing, and back-end database processing.
• Logs the query status (success, failure, termination, or timeout). Logs the user ID, session ID, and request ID for each query.

Level 2

• Logs everything logged in Level 1.
• Additionally, for each query, logs the repository name, business model name, presentation catalog (called Subject Area in Answers) name, SQL for the queries issued against physical databases, queries issued against the cache, number of rows returned from each query against a physical database and from queries issued against the cache, and the number of rows returned to the client application.

It is possible to set a higher number, but do not do so without the help of Oracle support.

How to Set Logging Level
1. In the Administration Tool, select Manage > Security.
2. The Security Manager dialog box appears.
3. Double-click the user's user ID.
4. The User dialog box appears.
5. Set the logging level by clicking the Up or Down arrows next to the Logging Level field