Oracle^® Business Intelligence Presentation Services Administration Guide > Administering Oracle BI Presentation Services >

Administering Sessions in Oracle BI Presentation Services

Using the Session Management screen in Oracle BI Presentation Services Administration, you can view information about logged on users and running requests, cancel requests, and clear the cache.

To access the Session Management screen

1. Log in to Oracle BI Presentation Services.
2. Choose Settings > Administration.
3. Click the Manage Sessions link.

   The Session Management screen appears, displaying the following tables:

   • The Sessions table, which gives information about users who are logged on to Oracle BI Presentation Services:

     Field	Description
     User ID	The name of the user connected to Oracle BI Presentation Services.
     Host Address	The name or IP address of the machine that initiated the HTTP connection to the Web server. This could be a user's PC, a handheld device, a firewall, and so on.
     Session ID	A unique identifier assigned by Oracle BI Presentation Services for each client session.
     Browser Info	Information about the browser being used to access Oracle BI Presentation Services.
     Logged On	The time stamp when the user ID logged on to Oracle BI Presentation Services.
     Last Access	The time stamp of the user ID's last activity on Oracle BI Presentation Services. This can be any kind of activity on the system, such as switching from one dashboard page to another.

   • The Cursor Cache table, which shows the status of requests made by users:

     Field	Description
     ID	The unique internal cache identifier for this entry.
     User	The name of the user who ran the request and last placed it into the cache. If two IDs are shown, the second ID is impersonating the first. For example, the entry lhurley/administrator means that the Administrator account logged on and impersonated lhurley. This can happen when the Oracle Business Intelligence Scheduler starts an iBot on someone's behalf. Oracle BI Scheduler logs on and impersonates that user so security and content filters still apply.
     Refs	The number of references to this entry since it was placed into the cache.
     Status	The status of the request using this cache entry: Running. The request is currently running. Finished. The request has finished. Queued. The system is waiting for a thread to become available so the request can be processed. Canceling. The application is in the process of canceling the request. Error. An error was encountered during the processing or running of the request. Look in the Statement column for information about the error.
     Time	The time taken to process and run the request, displayed in one second increments. A value of 0s (zero seconds) indicates that the request took under 1 second to complete.
     Action	Cancel. Kills the request. Appears for in-progress requests. The user running the request will receive an informational message indicating that the request was canceled by an administrator. Close. Clears the cache entry associated with this request. Appears for completed requests. View Log. Displays the entry in the nQQuery.log file for this request (if logging is turned on for this user). This file logs query activity on the system at the individual user level. Query logging is, by default, turned off. It can be enabled for individual users at different logging levels. The Oracle BI Server Administrator uses Security manager to enable logging for a user. You can also view the nQQuery.log file (located by default in the Log directory in the Oracle Business Intelligence installation directory) using a text editor such as Windows Notepad. The Oracle BI Server Administrator determines the maximum size of the nQQuery.log file by setting the USER_LOG_FILE_SIZE parameter in the NQSConfig.ini file.
     Last Accessed	The time stamp of the last time the cache entry for this request was used to satisfy a request.
     Statement	The SQL issued for the request, or if the request resulted in an error, information about the nature of the error.
     Information	Usage tracking information (for example, what report contained the query).
     Records	The number of records in the result set that have been seen (for example, 50+ to indicate that 50 records have been seen but there are additional records to be fetched or 75 to indicate that 75 records have been seen and there are no more records to be fetched)

To cancel all running requests

1. Click the Cancel Running Requests button.
2. Click Finished.

To cancel one running request

• In the Cursor Cache table, identify the request and click the Cancel link in the Action column.

  The user receives a message indicating that the request was canceled by an administrator.

To clear the Web cache

1. In the Cursor Cache table, identify the request and click the Close All Cursors button.
2. Click Finished.

To clear the cache entry associated with a request

• In the Cursor Cache table, identify the request and click the Close link in the Action column.

To view the query file for information about a request

• In the Cursor Cache table, identify the request and click the View Log link.

NOTE:  Query logging must be turned on for data to be saved in this log file. For more information about query logging, read Oracle Business Intelligence Server Administration Guide.