dbDBKraftDocs
Documentation/DBA modules
Chapter 25

Session Browser

Monitor and manage the sessions connected to your database. Available as a module and as a bottom-dock panel.

#25.1Summary tiles

TileCounts
Total SessionsAll sessions in the list.
ActiveStatus ACTIVE or RUNNING.
WaitingSessions in a real wait — idle SQL*Net waits are excluded, so this number means something.
BlockedSessions waiting on a lock held by another session.
BlockersSessions holding a lock that someone is waiting on.

#25.2Auto-refresh

The Refresh dropdown offers Off (default), Every 2s, 5s, 10s, 30s and Every 1m. Your choice is remembered. The manual Refresh button works at any time, and the header shows when the list was last updated.

#25.3All Sessions view

A full table: SID · Username · Status · OS User · Program · Machine · Logon Time · Wait Event · Blocked By · CPU (s) · I/O Reads · PGA (MB) · SQL Text · Actions.

  • Blocked sessions are tinted red; real waits show an amber warning triangle.
  • DBKraft’s own monitoring session is tinted blue and tagged this tool so you never mistake it for a user session.
  • Search sessions… matches username, program, machine, SQL text or SID.
  • Hide Inactive Sessions and Hide this tool’s session are two independent checkboxes.

Per-row actions: 👁 view details and ⊗ terminate.

#25.4Blocking Tree view

Switch to Blocking Tree (the button carries a badge with the blocked count) to see lock contention as a hierarchy:

  • Roots are the ultimate blockers, marked with a red shield icon.
  • Children are the sessions they block, marked with an amber ban icon, nested to any depth — A blocks B blocks C.
  • Each blocked node shows how long it has been waiting and on which event; each blocker shows how many sessions it is blocking.
  • Sessions whose blocker is not in the list are still shown, so nothing is hidden.

When nothing is blocked, the panel says No blocking chains — all clear.

#25.5Session details

The 👁 button opens a dialog listing every attribute the database reports for that session, plus the full Current SQL in a scrollable block.

#25.6Terminating a session

This ends someone’s work. The ⊗ button opens a confirmation dialog naming the session (SID,serial) and the user, and stating plainly that the session’s current transaction will be rolled back and that a DBA account (ALTER SYSTEM) is required.

Choose a Method:

MethodStatementEffect
Kill SessionALTER SYSTEM KILL SESSIONMarks the session KILLED and rolls it back. The session may linger in KILLED state until the client notices.
DisconnectALTER SYSTEM DISCONNECT SESSIONAlso kills the underlying server process.

The Immediate checkbox (on by default) tells Oracle not to wait for the session’s current call to finish.

If the session you are about to kill is blocking others, the dialog warns you and notes that terminating it should release the waiters.

After a successful termination the row disappears and the list refreshes shortly after to show the true state.