Use the Blocking Sessions health check in Mini DBA to review Oracle configuration, metadata, and monitoring signals before they become active alerts.
This health check looks for session and transaction conditions that can hold locks, consume resources, or leave application work waiting longer than expected.
Long-lived or blocking sessions can hold locks, delay maintenance, and turn one application transaction into a wider performance incident. This check keeps the session evidence visible while the cause can still be traced.
Identify the lead session, transaction, SQL, wait, login, host, and application. Correct the transaction or query pattern, and cancel a session only after comparing user impact with rollback and recovery risk.
Keep the session identifiers, transaction age, SQL text, waits, blocking chain, login, host, application, and action taken so the application owner can correct the transaction lifecycle.
Prioritize it according to workload criticality and trend. A one-off warning may be scheduled maintenance, but repeated failures usually deserve an owner and target date.
Prevent repeat failures by assigning an owner, documenting the expected configuration, and reviewing the check after upgrades, migrations, or major application releases.
Add this page to the operational runbook for Oracle environments where the check repeatedly fails. Record local thresholds, approved exceptions, escalation contacts, and the expected review interval so the next administrator can act quickly without rediscovering the same context.