Oracle-DB: Real-time monitoring dashboard in Panorama

In addition to various functions, the free performance analysis tool Panorama now also offers a browser dashboard for real-time monitoring of Oracle database performance.

This shows key indicators for active sessions by wait class as well as top sessions and top SQLs in considered time period.

Several values within this dashboard are presented as links which allow to dig in deeper using Panorama's  standard analysis workflows.

 Choose menu entry "DBA general"/"Dashboard", the time to cover until now and a refresh rate:




As long as gv$Active_Session_History has retrospective data it is shown in the graph for the chosen time period grouped by wait class.
At next refresh time only the delta since last refresh is transferred from gv$Active_Session_History to your browser instance.

Investigate a particular time period within the presented data

The top sessions and SQLs are related to the current time frame you can select within the chart.

If you select a particular time frame in the chart or drill down by the available links then the automatic refresh of the chart is suspended until you activate refreshing again.

There are several hyperlinks for further drill down into session and SQL details:



Clicking a wait class in the legend leads to detailed ASH analysis, at first grouped by wait events:


Clicking a session ID in the top session list leads to session details:

Clicking the SQL-ID in the top SQLs list leads to current SQL details in SGA:

What about using the dashboard with Standard Edition or without Diagnostics Pack?

This dashboard is based on AWR and ASH data which requires licensing of Diagnostics Pack in Enterprise Edition.

But you can use this dashboard also for Standard Edition or without Diagnostics Pack if alternative ASH/AWR gathering by Panorama-Sampler is activated in Panorama for this database instance.

Comments

Post a Comment

Popular posts from this blog

Oracle-DB: How to check for appropriate sequence caching

Image
A common pitfall while using sequences in Oracle-DB is forgetting to define sequence caching. The default for sequences is cache size = 0. That means, every sequence.nextval operation triggers a single write operation on dictionary table sys.SEQ$. Especially if frequently calling sequence.nextval uncached sequences may cause significant performance degradation. Frequently calling sequence.nextval in parallel sessions may lead to ramdom lock scenarios in library cache. Setting a cache size for a sequence may heavy increase performance of nextval-operations. There's a minimal memory overhead for caching a sequence because all that's needed is a counter to increase in SGA memory and a upper limit. If this limit is reached with the counter, the upper limit is increased by cache size and the new upper limit is written down once to SEQ$. The possible drawback for sequence caching is that you loose all your values between the current value and the highest cached value if yo...
Read more

Common pitfalls using SQL*Net via Firewalls

It's very common that firewalls are terminating idle TCP sessions after a limited time, often after approximately one hour. Possible problem If you have a long running SQL or PL/SQL program and the firewall terminates your apparently idle TCP session this may lead to the following scenario: the database is not able to send result to client. After reaching the TCP-timeout the database server terminates the DB-Session the client program stays in socket read forever waiting for the database response Oracle's full solution: SQLNET.EXPIRE_TIME=x in sqlnet.ora Oracle's solution for this problem is setting parameter SQLNET.EXPIRE_TIME=x in sqlnet.ora where x are the minutes between keep alive packets on idle sessions that inform the firewall that this session is always alive. SQLNET.EXPIRE_TIME hast to be set in the sqlnet.ora of your RDBMS' ORACLE_HOME. Normally $ORACLE_HOME/network/admin. If you have a grid infrastructure setting SQLNET.EXPIRE_TIME in sqlnet...
Read more

Oracle-DB: Identify excessive logon/logoff operations with short-running sessions

Image
Creating and destroying database sessions in loop may lead to significant database load. This blog post contains more about quantifying this load. Applications should use connection pooling at client or database side to prevent excessive session creation. But how can I identify the client processes causing this sessions? Scan DBA_Audit_Trail to identify context info If auditing logon/logoff-operations is activated for your database, scan DBA_Audit_Trail. You can do this by 2 was: Alternative 1: Use my tool "Panorama" to evaluate audit trail Panorama is available here. Go to menu "DBA general" / "Audit Trail": Select start and end time for selection Filter column "Action" for "LOGON" Set "Grouping" to "Minute" Execute selection via button "Show audit trail" Add columns of your choice to diagram by context menu (right mouse button) This way you can identify the machine, DB-user ...
Read more