Oracle Activity shows live session and workload information for a monitored Oracle server. Use it to identify busy sessions, long-running SQL, and blocking symptoms.
The Oracle Activity page includes the Mini DBA Time Range selector. Use Live to watch current sessions, waits, users, programs, and SQL, or switch to Last Hour, Last 12 Hours, Last Day, Last Week, or Custom to review captured session history. Mini DBA loads and caches the selected historical activity dataset for the current console session and server context, so reviewing the loaded historical sessions and moving between related views stays quick. Use Back to Live to resume live updates, then choose another historical range when you need a different incident window.
Oracle Activity is the starting point for live Oracle performance triage. It shows what sessions are doing now, which users and programs are involved, and which SQL or wait symptoms are visible. Use it when a business application is slow, a batch job is overrunning, or a database appears busy without a clear cause.
Start with long-running active sessions and sessions that appear to be blocking other work. Then group activity by user, program, machine, service, or SQL text where available. A single expensive SQL statement may need tuning, while many sessions waiting on the same event may indicate a broader contention, I/O, memory, or application concurrency issue.
Use Oracle Waits to understand what sessions are waiting for and Oracle Queries to identify repeated expensive SQL. If the activity spike started after a deployment, capture the time, program, user, and SQL pattern so developers can compare it with release changes.
When plan detail is available, use the Oracle plan modal to review plan text, operator cost, rows, bytes, access predicates, and filter predicates. The AI Assistant can explain the selected plan and help create a safe tuning checklist.
Inactive sessions are connected but not currently running work. They can be normal in pooled applications, but too many sessions may still consume resources.
Prioritize blocking sessions, long-running active SQL, and sessions linked to the affected business application.
Oracle version, account permissions, database configuration, and available dynamic performance views can affect what Mini DBA can display.