Oracle 11.2.0.1 SE-One
Oracle Linux 5.6 x86-64
So, my primary developer comes around today and says 'by the way, last spring we had an issue when daylight savings time started. some jobs ran an hour early or late, I don't remember which, and it seems like some may have run twice. The jobs did correct themselves after the first run after the time change.
Great.
SQL> select * from dba_scheduler_global_attribute;
MAX_JOB_SLAVE_PROCESSES
LOG_HISTORY 30
DEFAULT_TIMEZONE CST6CDT
EMAIL_SERVER
EMAIL_SENDER
LAST_OBSERVED_EVENT
EVENT_EXPIRY_TIME
FILE_WATCHER_COUNT 0
CURRENT_OPEN_WINDOW
9 rows selected.
SQL> select * from v$timezone_file;
timezlrg_11.dat 11
The above timezone is correct, we are in US Central.
selecting dba_scheduler_jobs, here is a typical entry:
JOB_SUMMARY_MARGIN_MONTHLY
Start Date: 06-JUL-12 07.00.00.000000 AM -05:00
repeat interval: MONTHLY(.292,6)
next run date: 06-NOV-12 07.00.29.000000 AM -05:00
Interesting to also note that some jobs owned by SYS show a start/next dates as 'PST8PDT' and jobs owned by EXFSYS and ORACLE_OCM with time zones expressed as '-07:00'. I just notes those as a curiosity .. looks like they were set up using the time in Redwood Shores.
My concern is what does it look like I'm seeing for our home-grown jobs and is there anything I can/need to do to head off any issues come Sunday morning.