Skip to content

ASH Viewer provides a graphical view of active session history data within the Oracle and PostgreSQL DB

License

Notifications You must be signed in to change notification settings

Kengson/ASH-Viewer

 
 

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

73 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

ASH Viewer

ASH Viewer provides graphical view of active session history data within the database.

Supported databases: Oracle, PostgreSQL

ASHViewerMainPage

Table of contents

Quick start

  • Download the latest binary file.
  • Download JDBC driver for your database (Oracle, PostgreSQL)
  • Unpack the binary archive and run ASH-Viewer.jar
  • Open connection dialog and populate them with data (URL for Oracle database: jdbc:oracle:thin:@host:port:SID)

ASHViewerConnectionDialog

  • Press Connect button and start to monitor your system

ASHViewerTop

  • Review Raw data interface to gain a deep insight into active session history

ASHViewerRaw

  • Double click on Top sql & sessions interface to get window with ASH details by sql or session ID
"Top sql & sessions"

ASHViewerSql

ASHViewerSession

How it works

Active Session History (ASH) is a view in Oracle database that maps a circular buffer in the SGA. The name of the view is V$ACTIVE_SESSION_HISTORY. This view is populated every second and will only contain data for 'active' sessions, which are defined as sessions waiting on a non-idle event or on a CPU.

ASH Viewer provides graphical Top Activity, similar Top Activity analysis and Drilldown of Oracle Enterprise Manager performance page. ASH Viewer store ASH data locally using embedded database Oracle Berkeley DB Java Edition.

For Oracle standard edition and PostgreSQL, ASH Viewer emulate ASH, storing active session data on local storage.

** Please note that v$active_session_history is a part of the Oracle Diagnostic Pack and requires a purchase of the ODP license.**

Security

Passwords are stored in configuration file in encrypted form with secret key (computer name or hostname). So, when you run copied configuration on another host, you need to change password with a new secret key. This is a minimal foolproof and for maximum protection it is necessary to store sensitive data using filesystem-level encryption or another way.

Bugs and feature requests

Have a bug or a feature request? Please open an issue

Downloads

Based on

License

GPLv3 license

Code released under the GNU General Public License v3.0

Contact

Created by @akardapolov - feel free to contact me!

About

ASH Viewer provides a graphical view of active session history data within the Oracle and PostgreSQL DB

Resources

License

Stars

Watchers

Forks

Packages

No packages published

Languages

  • Java 99.9%
  • HTML 0.1%