Recent Posts


Oracle Business Intelligence Cloud Service (BICS): Managing Cache and Session Log for Administrator User
Posted on November 2, 2016
Author: Cameron Ross, Performance Architects

Managing the Cache and Session Log as an administrative user in an Oracle Business Intelligence Cloud Service (BICS) environment are very important tasks. You can do everything from filter out the session log by users, to canceling any running queries, to clearing the session log of previous queries to clear the cache. There are many other neat features that you can use on the “Sessions and Query Cache” screen.


To get started, log in to the BICS instance and select the “Console” button in the group of icons in the middle of the screen.

Notice all of the options available in the console for the Administrator. For the purposes of this blog post, select the icon that is labeled “Sessions and Query Cache.”

The “Session and Query Cache” capability gives you a list of all users in the instance, as well as information about the browser they are using and the time the user logged in and last accessed anything in the instance. Below is a table that gives you information about the users in the environment:

Underneath the user table are all of the queries that are run along with the user profiles and the logical SQL. You have the ability to close a specific query, as well as viewing the log. Viewing the log allows you to then see the physical SQL of the query.

Notice at the end of the table that displays the user data that there is now the ability to filter the session log underneath by the user selected above.

This becomes very useful in order to get to a user’s exact actions in the BICS environment with one click of a button. Notice below how this new feature works:

Another neat feature in the sessions log is the ability to download a CSV file of the queries. This can then be opened in an Excel document and you can pivot that data.

The ability to cancel running requests allows the administrator to do exactly as it sounds. If there is a query that is taking a long amount of time, clicking the “Cancel Running Requests” button will cancel that query from being completed.

Closing all cursors will take all executed queries in the session log with a status of “Finished” and will clear them from the log. This gives the administrator a better idea of any open and running queries.

Lastly you can see at the end of the session log that there is an area where you can sort your queries in the table. Below is the image of the different options for how the administrator can sort the queries:

After sorting the queries by “User Name Descending” the administrator should now see all of the queries in the table sorted in order based off of the “User” column in the table.


© Performance Architects, Inc. and Performance Architects Blog, 2006 - present. Unauthorized use and/or duplication of this material without express and written permission from this blog's author and/or owner is strictly prohibited. Excerpts and links may be used, provided that full and clear credit is given to Performance Architects, Inc. and Performance Architects Blog with appropriate and specific direction to the original content.

Leave a Reply

Your email address will not be published. Required fields are marked *