Re: DBMS Scheduler runs jobs an hour late
- From: Niall Litchfield <niall.litchfield@xxxxxxxxx>
- To: howard.latham@xxxxxxxxx
- Date: Mon, 1 Jun 2009 14:22:36 +0100
OK I've now dug up my client notes when we discovered a similar issue with
one of our clients. Note that there is a scheduler attribute that specifies
the timezone.
Item 6 on the list referred to an issue with scheduled jobs using
dbms_scheduler – these are created in TOAD, and use the new scheduling
functionality. It had been observed by the client that jobs did not follow
the DST time changes correctly, and had to be scheduled using an offset of
one hour following the time change. We observed that the db servers were
setup at the OS level in a US timezones. There were a number of oracle bugs
in 10g following the US government changing DST in 2007. Consequently we
checked the database for timezone problems using Oracle’s tzdetect.sql
script. However this found no issues.
We then adjusted the locale of the operating system also with no effect.
Finally we discovered that the default timezone attribute of the scheduler
was set to Europe/Lisbon. Setting this back to the correct value
Europe/London resolved the issue and jobs can now be scheduled using the
expected run time rather than at a 1 hour offset.
On Mon, Jun 1, 2009 at 2:19 PM, Niall Litchfield <niall.litchfield@xxxxxxxxx
> wrote:
> Check the 'scheduler' timezone and any offset specified (by default
> usually)when the jobs were created (in DBA_SCHEDULER_JOBS).
>
> Niall Litchfield
> http://www.orawin.info
>
> On Mon, Jun 1, 2009 at 2:14 PM, Howard Latham
> <howard.latham@xxxxxxxxx>wrote:
>
>> Oracle 10g on Redhat Linux
>>
>> Although our time zone is Europe/London and the Database seems to know we
>> are in GMT+1
>> our manually run jobs run an hour late - any ideas?
>>
>> --
>> Howard A. Latham
>>
>>
>>
>
>
> --
> Niall Litchfield
> Oracle DBA
> http://www.orawin.info
>
--
Niall Litchfield
Oracle DBA
http://www.orawin.info
Other related posts:
