Monitor Users and Activity Logs

You can see information about any users who are currently signed in and troubleshoot report queries from the Manage Session page.


Monitor Users Who Are Signed In

You can see how many users are signed in to your service and view detailed information about each user from the Manage Session page.

  • User ID: Name that the user entered when they signed in.
  • Browser Info: Information about the browser used to sign in.
  • Logged On: Time when the user signed in.
  • Last Access: Time stamp for the last activity for this user. This can be any kind of activity, such as switching from one page to another.
  1. In the Oracle Analytics Home page, click the Navigator, and then click Console.
  2. Click Session and Query Cache.
  3. Locate the Sessions sections.

    The Sessions section at the top of the page shows how many users are currently signed in (Total Number of Sessions) and detailed information about these users.

  4. To monitor a particular user, select Filter Cursors by Session.

    Information for this user displays in the Cursor Cache table.

    Click Clear Filter to show information for all users.

  5. To change how messages are logged for a particular user, select a Log Level from the list.

    By default, logging is disabled.

Analyze SQL Queries and Logs

Administrators can examine the underlying SQL query requests that are run as people use the service.

  1. In the Home page, click the Navigator, and then click Console.
  2. Click Sessions and Query Cache.
  3. Locate the Cursor Cache section, and review the query information recorded there. See Query Information Recorded in the Cursor Cache Table.
  4. Optional: Click Close All Cursors to remove information in the Cursor Cache table.
  5. Optional: Click Cancel Running Requests to cancel all requests that are running for analyses.

Query Information Recorded in the Cursor Cache Table

Administrators can examine the underlying SQL query requests that are run as people use the service.

These options apply only to analyses and dashboards. They don't apply to data visualizations.

Field Description


A unique internal identifier that is assigned to each entry.


The name of the user who ran the analysis and last placed it into the cache.


The number of references to this entry since it was placed into the cache.


The status of the analysis that is using this cache entry:

  • Starting — The analysis is starting to run.

  • Waiting on Parent — A view in the analysis is waiting for data to be returned for the query.

  • Running — The analysis is currently running.

  • Finished — The analysis has finished.

  • Queued — The system is waiting for a thread to become available so the analysis can be processed.

  • Canceling — The application is in the process of canceling the analysis.

  • Error — An error occurred during the processing or running of the analysis. Look in the Statement column for information about the error.


The time taken to process and run the analysis, displayed in one-second increments. A value of 0s (zero seconds) indicates that the analysis took under 1 second to complete.


Links that you can click to affect the analysis:

  • Cancel — Terminates the analysis. Is displayed for in-progress analyses. The user running the analysis receives an informational message indicating that the analysis was canceled by an administrator.

  • Close — Clears the cache entry associated with this analysis. Is displayed for completed analyses.

  • View Log — Displays the log of a query run for this analysis.

  • Diagnostic — Displays an HTML page of diagnostic information that you can share with Oracle Customer Support.

Last Accessed

The time stamp of the last time the cache entry for this analysis was used to satisfy an analysis.


The logical SQL statement that was issued for the analysis; or if the analysis resulted in an error, information about the nature of the error.


Usage tracking information (for example, what analysis contained the query).


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).