OBIEE Log levels

What is log in Obiee?
Ans: OBIEE creates a log file called NQQuery.log which records valuable information about the operations performed by the OBIEE server.

The most useful part is the information it can provide about the actions performed by the users, the logical sql that it generates, whether the data was returned from a cache hit, or if it had to get it from the database.

In case the data was gotten from the database, it provides the actual sql statements that were sent to the database and the time that each one took to complete.

By looking at this log file, administrators can quickly determine which pages took a long time to return, and can then quickly view the sql that were responsible for the slow response time.

The log file is created by default in the $ORACLE_HOME/biee/server/Log directory. The default maximum size of this file is 10Mb. OBIEE does limited log rotation. After the log fills up, it copies it over to NQQuery.log.old and then reuses the log file. The previous contents of the NQQuery.log.old are overwritten.

The size of the log file can be increased by changing the setting USER_LOG_FILE_SIZE in the configuration file - NQSConfig.INI, which can be found in $ORACLE_HOME/biee/server/Config.

How to set logging level in Obiee 10g?

Ans: Open Administration tool, start>Programs>Oracle Business Intelligence>Administration

Step-1

Open repository in online mode to set log level.

Step-2

Open Security Manager window which is under Manage.

Step-3

select log level.

Step-4

What are the log levels?

Set the logging level by clicking the Up or Down arrows next to the Logging Level field.

To disable logging level set the logging level to 0.

Log levels and corresponding information is given below in the table.

Logging Level	Information That Is Logged
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.
Level 3	Logs everything logged in Level 2. Additionally, adds a log entry for the logical query plan, when a query that was supposed to seed the cache was not inserted into the cache, when existing cache entries are purged to make room for the current query, and when the attempt to update the exact match hit detector fails. Do not select this level without the assistance of Technical Support.
Level 4	Logs everything logged in Level 3. Additionally, logs the query execution plan. Do not select this level without the assistance of Technical Support.
Level 5	Logs everything logged in Level 4. Additionally, logs intermediate row counts at various points in the execution plan. Do not select this level without the assistance of Technical Support.
Level 6 and Level 7	Reserved for future use.