As per WLA AE, DST came early for some [the "Azores" was one, ah, give me those sunny climes!]
Apparently there is a bug in TZ in which DST rolls over as pre-Dubya.
Till now, the workaround is to [a] change the affected job start times OR [b] update the TZ table.
It is my understanding that there is an official hotfix coming down the road, possibly this ones updates the reference file under the 'dbobj" dir.
Were any of you affected by this early change?
The following zone entries are confirmed incorrect...
Atlantic/Azores - ACT1ACTDST,M3.5.0/01:00:00,M9.5.0 CentralEurope-West - MET-1METDST,M3.5.0/01:00:00,M9.5.0 EasternEurope-Mid - EET-2EETDST,M3.5.0,M9.5.0/03:00:00 EET - EET-2EETDST,M3.5.0/03:00:00,M9.5.0/04:00:00 WET - WET+0WETDST,M3.5.0,M9.5.0/03:00:00
All of these need to have "M9.5.0" changed to "M10.5.0"
There are also 5 alias/city entries that map back to these zones...
Azores Europe/Warsaw Europe/Athens Europe/Helsinki EasternEurope
I don't have any ETA for the fix yet, but you can update the ujo_timezones table with these database queries:
update ujo_timezones set zone='ACT1ACTDST,M3.5.0/01:00:00,M10.5.0' where name='Atlantic/Azores'; update ujo_timezones set zone='MET-1METDST,M3.5.0/01:00:00,M10.5.0' where name='CentralEurope-West'; update ujo_timezones set zone='EET-2EETDST,M3.5.0,M10.5.0/03:00:00' where name='EasternEurope-Mid'; update ujo_timezones set zone='EET-2EETDST,M3.5.0/03:00:00,M10.5.0/04:00:00' where name='EET'; update ujo_timezones set zone='WET+0WETDST,M3.5.0,M10.5.0/03:00:00' where name='WET';
After these updates are performed, you will need to run an update_job through jil for each impacted job.
I also found back Patch RO67562 ( 2014) for WAAE 11.3.6 to correct the following time zones
This patch updated this below file
seed_timezones.adb 15430 THU FEB 13 15:01:18 2014
Thank you Jean Paul for taking the time to research the issue and then share your findings.
I am assuming that the seed_timezones.adb file is not a normally editable file, may I know the location of this file?
What is weird about this issue, is that it has been around since earlier days and no one has noticed it!
Your help is much appreciated
As you know, from time to time, DST changes in different countries. Some are no longer using it since a few years, others continues to use it.
We are checking all timezones having wrong DST rules
Based on that, we will come up with the patch delivery vehicle for it.
But in case of any urgency, you can update table ujo_timezones for any given DST with new settings