https://www.oraclescripts.com/tags/failed-jobs/Recent content in Failed Jobs on Oracle ScriptsHugo -- gohugo.ioenOracleScripts.comWed, 26 Aug 2026 00:00:00 +0000https://www.oraclescripts.com/post/review-scheduler-job-run-history-with-dba-scheduler-job-run-details/Wed, 26 Aug 2026 00:00:00 +0000https://www.oraclescripts.com/post/review-scheduler-job-run-history-with-dba-scheduler-job-run-details/ <h2 id="review-job-run-history-with-dba_scheduler_job_run_details">Review Job Run History with DBA_SCHEDULER_JOB_RUN_DETAILS</h2> <h2 id="purpose">Purpose</h2> <p>A stuck job that fails silently overnight rarely announces itself. The next morning's dependent process just doesn't have the data it expected, and by then the only trace of what actually happened lives in the Scheduler's own run log. <strong><a href="https://docs.oracle.com/en/database/oracle/oracle-database/19/refrn/ALL_SCHEDULER_JOB_RUN_DETAILS.html">DBA_SCHEDULER_JOB_RUN_DETAILS</a></strong> is that run log — a record of every completed execution the Scheduler has kept, covering every job in the database rather than only the current user's own jobs. It is a different question from &quot;what is running right now&quot;: that question belongs to <code>DBA_SCHEDULER_RUNNING_JOBS</code>, a live snapshot of in-flight jobs that disappears the moment a job finishes. <code>DBA_SCHEDULER_JOB_RUN_DETAILS</code> is the after-the-fact history, and it is the only place <code>STATUS</code>, <code>ERROR#</code>, <code>ACTUAL_START_DATE</code>, and <code>RUN_DURATION</code> can be reviewed together for a run that has already ended.</p>