OBIEE 11g No Log found Error:
When we are looking into log file we are getting error like No Log Found.
In this scenario we need to set log level 7 in RPD .
Setting Log Level in RPD:
We have to check the Logging Level in three places in RPD.
Step 1 : Open RPD by using the credentials.
Step 2 : Go to Tools–>Options–>Repository
You can find a default logging level in the option of the repository:
Step 3 : Go to Manage–>Identity–>web logic and set the Logging level to 7 here.
Step 4 : Sometimes we used to define the Log Level in Initialization Blocks.
Go to Variables–>Session–>Initialization Blocks–Log Level.
Edit the Data Target and set the Log Level to 7.
Description of logging levels
Logging Levels
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
Level 4
Logs everything logged in Level 3
Additionally, logs the query execution plan.
Level 5
Logs everything logged in Level 4
Additionally, logs intermediate row counts at various points in the execution plan.
Thanks,
Satya Ranki Reddy
When we are looking into log file we are getting error like No Log Found.
In this scenario we need to set log level 7 in RPD .
Setting Log Level in RPD:
We have to check the Logging Level in three places in RPD.
Step 1 : Open RPD by using the credentials.
Step 2 : Go to Tools–>Options–>Repository
You can find a default logging level in the option of the repository:
Step 3 : Go to Manage–>Identity–>web logic and set the Logging level to 7 here.
Step 4 : Sometimes we used to define the Log Level in Initialization Blocks.
Go to Variables–>Session–>Initialization Blocks–Log Level.
Edit the Data Target and set the Log Level to 7.
Description of logging levels
Logging Levels
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
Level 4
Logs everything logged in Level 3
Additionally, logs the query execution plan.
Level 5
Logs everything logged in Level 4
Additionally, logs intermediate row counts at various points in the execution plan.
Thanks,
Satya Ranki Reddy
No comments:
Post a Comment