Oracle DBA Scripts on Oracle Scripts

Oracle Scheduler Job Monitoring with DBA_SCHEDULER_RUNNING_JOBS

Tue, 09 Jun 2026 00:00:00 +0000

Oracle Scheduler Job Monitoring with DBA_SCHEDULER_RUNNING_JOBS

Purpose

Which Oracle Scheduler jobs are executing at this instant, and how long has each been running? DBA_SCHEDULER_RUNNING_JOBS answers that directly. It lists only the jobs that are active right now — not the full job catalog, not the run history, just the live set. Joining it to DBA_SCHEDULER_JOBS adds the job's owner, program, and schedule, so a single query turns "is anything stuck?" into a concrete list of names, session IDs, and elapsed times.

Oracle DBMS_SCHEDULER: Create and Manage Jobs with PL/SQL

Mon, 08 Jun 2026 00:00:00 +0000

Oracle DBMS_SCHEDULER: Create and Manage Jobs with PL/SQL

Purpose

Automating a recurring task — a nightly statistics gather, a log purge, an end-of-month rollup — is a standard part of running an Oracle database. DBMS_SCHEDULER.CREATE_JOB is the procedure that registers that task with the database so it runs on a calendar schedule without an external cron entry. The job, its action, and its schedule all live inside the database, which means they are backed up, replicated to a standby, and visible in the data dictionary.

Query Wait Events by Session with Oracle V$SESSION_WAIT

Sun, 07 Jun 2026 00:00:00 +0000

Query Wait Events by Session with Oracle V$SESSION_WAIT

Purpose

V$SESSION_WAIT is the real-time view that shows what each Oracle session is waiting on this very second. For every session it exposes the wait event name, how long the session has been in that wait, and three event-specific parameters (P1, P2, P3) that pinpoint the resource — a file and block number, a lock type, a latch address. It is the view to reach for when the database "feels slow right now" and you need the current state, not a post-mortem from AWR.

Oracle Index Rebuild and Coalesce with ALTER INDEX

Sat, 06 Jun 2026 00:00:00 +0000

Oracle Index Rebuild and Coalesce with ALTER INDEX

Purpose

Over months of heavy delete and update activity, a B-tree index can accumulate empty and half-full leaf blocks. The index keeps working, but it grows wider than the data it points to, so range scans read more blocks than they need and the segment holds space that is no longer doing useful work. ALTER INDEX ... REBUILD and ALTER INDEX ... COALESCE are the two commands that address this — one rebuilds the index from scratch, the other merges adjacent sparse leaf blocks in place.