Oracle Database / Operations & Incident Response
Diagnose a Scheduler job running at the wrong local time
A calendar schedule can be correct for one timezone and unexpected after a daylight-saving transition or session change. Inspect the stored schedule and timestamps.
Environment and inputs: Oracle Database 19c baseline · SQL*Plus-compatible SQL unless RMAN, DGMGRL, ADRCI or a host shell is specified. Check release, patch level, edition and container first.
Start with this diagnostic
Use the stated SQL, RMAN, DGMGRL or host shell and replace sample names with approved targets. DBA and V$ views need authorized catalog access in the correct container. Do not grant broad privileges for an example.
SELECT owner, job_name, start_date, repeat_interval, next_run_date FROM dba_scheduler_jobs WHERE owner = 'APP_OWNER' AND job_name = 'APP_NIGHTLY_JOB';Read the result
Timestamp-with-time-zone values and the repeat expression describe schedule intent. Compare them with the business timezone rather than only the server's displayed clock.
Resolve and verify
Review timezone-region use and the documented calendaring semantics. Test the proposed schedule across daylight-saving boundaries before an approved change.
Operational precautions
Do not manually change the server clock or shift the database timezone to repair one job's schedule.