Hi,
i thought such problems are things of the past but after the clock change last saturday to sunday all our DBMS_SCHEDULER-Jobs started one hour to late.
System: Microsoft Windows Server 2003 R2 Enterprise x64 Edition, Oracle Database 10g Release 2 Standard Edition One 10.2.0.4.0 Patch 8609347 (July 2009).
Here in Germany we live in the UTC/GMT + 1 timezone. The DB-Server-Time (right time and timezone gmt+1) an the SYSDATE of the DB are right (i think).
-->
SQL> select to_char(sysdate, 'YYYY-MM-DD HH24:MI:SS') Time from dual;
TIME
-------------------
2011-03-29 09:58:27 -- correct time
SQL> select dbtimezone from dual;
DBTIME
------
+01:00
SQL> select to_char(systimestamp, 'YYYY-MM-DD HH24:MI:SS TZR') sys_time_stamp from dual;
SYS_TIME_STAMP
----------------------------------------------------
2011-03-29 09:48:45 +02:00
I am really confused now, because i read that the "summer-time" here in germany is gmt+2 because we putted our clock one hour forward.
It is a little bit crazy:
For example a Job with repeat interval "FREQ=DAILY; BYHOUR=21; BYMINUTE=0"
have "Last Start Date" --> *2011/03/28 21:00:00.108000 +01:00*
and the "Next Run Date" --> *2011/03/29 21:00:00.000000 +01:00*
But it started to late last night. (in the "Run Log" of this job i find a "Log Date" --> *2011/03/28 22:02:01.267000 +02:00* )
I have no idea what to do now. I am really unsure with this offsets.
I think i a modern software there must be a solution without changing the clock or some timezone offsets every half year.
I know changing the clock between summer- and winter-time is a stupid but we have to live with this and the jobs also have to.
Perhaps anyone can help me to solve this problem.
Edited by: MaLau on 29.03.2011 11:25