This is the usual message we get when we try to open the log file(ie, When we click on View Log in Session Management). This is due to the logging level the current user having.
The logging level is a parameter which control the level of information that you can retrieve in the log file.
If we want the user to see log information in the log file, we should change the logging level in RPD.
Logging level = 0 means, no access to log file.
You can enable logging level for individual users, you cannot configure a logging level for a group.
In normal operations :
The logging level is a parameter which control the level of information that you can retrieve in the log file.
If we want the user to see log information in the log file, we should change the logging level in RPD.
Logging level = 0 means, no access to log file.
You can enable logging level for individual users, you cannot configure a logging level for a group.
In normal operations :
- users have a logging level set to 0
- administrator have a logging level set to 2
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 queryLevel 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 applicationLevel 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 failsLevel 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.To change the logging level follow the below steps :- In the Administration Tool, select Manage > Security . 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.
very useful, simply superb and easy to understand jagga :)
ReplyDelete