Recurring events off by 60 minutes after daylight saving time switch

I searched but didn't find this exact issue anywhere. Following this past weekend's switch to Daylight Saving Time (DST), iCal recurring events have been shifted one hour later. It is a problem that I encountered with my own web calendaring application, wherein the offset between UTC and a given time zone changes with the coming and going of DST. I am curious why Apple has never instituted a fix for this, especially considering that the fix is so simple. All that must be done is detect whether the original datetime is in DST or not. If it is not, and the given recurrence is, then you must subtract 60 minutes from the recurrence's datetime. Similarly, if the originating datetime is in DST, and the given recurrence is not, then you must add 60 minutes to the recurrence's datetime.

I have the same problem but much worse. Only 5 of my 18 recurring weekly events have shifted, so I didn't realize that anything was off until I missed one of my classes today. This seems weird....

Similar Messages

Converting unix timestamp to date after Daylight Saving Time change

Hello,
in one of the products we use the internal scheduler stores dates (and times) in an Unix-like format, that is seconds since 1st of January 1970. We have used this SQL to extract the actual date:
TO_CHAR(t.next_fire_time/(24*60*60*1000) +to_date('19700101020000','yyyymmddhh24miss'),'yyyymmddhh24miss')
Everything worked fine until the time has changed this weekend from UTC+2 to UTC+1 (we are located in Eastern Europe). Since then the query above returns one hour later than it should.
I.e. timestamp *1320067800000* is returned as *20111031153000* even thought correct is (and the actual time the event was scheduled) *31-OCT-11 02.30.16.000000 PM*
I found queries like this on different forums and no one seems to worry much about the daylight savings. Is this a configuration issue in the DB or is it a bug in our code?
I tried selecting the SESSIONTIMEZONE and DBTIMEZONE and both were +1.
Any help appreciated.

Your problem is hard-coded 2hour offset:
to_date('19700101<font size=5 color=red>02</font>0000','yyyymmddhh24miss')You need to calculate current offset to adjust it to current DST situation:
with sample_table as (
                      select date '1970-01-01' + 1320067800000 / 1000 / 3600 / 24 dt_utc from dual
select dt_utc,
        dt_utc +
        extract(
                     timezone_hour
                from
                     from_tz(cast(dt_utc as timestamp),'utc') at time zone 'Europe/Prague'
               ) / 24 dt_prague,
        extract(
                     timezone_hour
                from
                     from_tz(cast(dt_utc as timestamp),'utc') at time zone 'Europe/Prague'
               ) tz_offset
from sample_table
DT_UTC              DT_PRAGUE            TZ_OFFSET
2011-10-31 13:30:00 2011-10-31 14:30:00          1
SQL> SY.

Exchange Active Sync UTC Daylight Saving Time

Color me a bit confused. I am attempting to write an IOS client application to communicate with Exchange ActiveSync and display calendar information. But I am seeing some conflicting information in the protocol docs when compared to what I am getting from
Exchange. Either that or I am somehow misinterpreting one or the other.
My intent is to save an appointment in my local database in Coordinated Universal Time and then have the UI read in the information and display it as appropriate to the local timezone. In this way an recurring appointment created before daylight saving time
for Noon will still be at the same time of day in local time as an appointment created during daylight saving time for noon. But they are not.
My understanding of the documentation is as such:
In MS-ASCAL pdf section 2.2.2.40 (roughly page 34) it says for Start Time that : ...the value of this element is a dateTime data type as specified in MS-ASDTYPE section 2.3.
Moving to MS-ASDTYPE section 2.3 (roughly page 7) the dateTime value is specified in the format of ISO-8601 and all dates are given in Coordinated Universal Time (UTC)
Looking up coordinated universal time I see that UTC does not changed with the seasons as local or civil time does and therefore DOES NOT support daylight saving time. This makes sense, as DST is decidedly local and is ignored by many areas. You cannot know
from the perspective of UTC whether or not to apply a DST offset without knowing what timezone and area the time represents, therefore no daylight saving time can be supported. Based on this information I should be able to just slap the dates into my database
as they are and merely have the UI adjust itself to display them properly.
However, as a tested I began seeing a divergence of an hour between the two appointments in the database before the UI has even read them. To confirm this I created two recurring appointments representing Lunch at 12 noon local time. One that starts on March
1st 2014 (Standard Time) and one that starts on March 10th 2014 (daylight saving time) in the eastern timezone. This should be March X 2014 at 1700 hours in both cases should it not?
In the WBXML/XML that I am receiving I am getting two different times. The appointment that starts during standard time gives me a start time of 20140301T170000Z. The appointment that starts after daylight saving time is in effect locally gives me 20140301T160000Z.
The difference between the two times is 1 hour, which is the daylight saving time offset. It is my perception based on everything that I have read both in the microsoft protocol documentation and outside it that these two times should be the same and that whatever
client that gets to display them should be the one putting the offset in place as needed. Noon local time is noon local time but local time is the province of the local municipality/timezone, not that of UTC.
So my question is what exactly is going on here? Are the start/stop/date stamp date times in UTC or not. If they are in UTC, then why are they offset by an hour instead of being at the same time? Obviously outlook displays these correctly for local time,
because both appear at noon. But in my case my database contains locally adjusted times instead of the UTC times I thought I was getting which is throwing off when those appointments appear in the UI.
Can someone please clarify what's going on here and what I should be seeing?
Thanks.
E

Thanks for the reply, however after doing what is said the problem still remains. I did not try the manual approach, because of the time that would take with calendars that change at least daily.
I am running the latest update of ICal and IPod, you would think this would have been addressed with one of the updates to allow the sync to work correctly with 5th generation IPods.
I am going to try and turn off day light savings time set the clock to a Central Time zone and see if that works, I do not cross time zones much, anymore.
MacBook Mac OS X (10.4.9)

TimerThreads and daylight saving time

I have this task that I need to do everyday at 0:00 AM.
I am using the ScheduleAtFixedRate method to perform this starting it at 0:00 AM and running it again every 24 hours. It is very important to run at 0:00 because it involves money a a reconciliation file.
According to the API documentation:
Fixed-rate execution is appropriate for recurring activities that are sensitive to absolute time, such as ringing a chime every hour on the hour, or running scheduled maintenance every day at a particular time.
My question is what about daylight-saving time ? What happens to such a task that is supposed to run every day at 0:00 ?
Thanks
Luis Cordeiro

My guess, and it is just a guess, is that the task will run every 24 hours, and therefore after a daylight saving time switch you will find it running at 01:00 or at 23:00. But I would suggest you test for yourself. Set up a test program that schedules a task every 3 hours, change your system's date and time to be 5 hours before the end (or start) of DST, and see what happens after it runs for 6 hours.

ICal event times changed when my mac updated time to daylight saving time

When my mac updated its time automatically to daylight saving time, the timed events in iCal all had an hour added to them. Time zone support is off in iCal. I tried changing my time zone from the system preferences (just to see what happens) and the iCal times also change. Is there any way to turn off this ridiculous and useless (to me) feature? I travel quite a bit and all iCal events are always added in local time scheduling. So there is no need for the event times to change when I change time zone!
Thanks!

I am having the same problem but it's only some of the appointments that were changed. I think some were entered after the update and perhaps those weren't changed. Very confusing.

Multiple instances spawned after daylight savings time change

This is a known issue and there is an SAP Knowledge Base Article created on this issue:
1448881 - Multiple instances spawned after daylight savings time change
Below is the information from the SAP Knowledge Base Article:
Symptom
Scheduled reports that are supposed to run once a day, run multiple times.
Duplicate instances are being created.
Environment
BusinessObjects Enterprise XIR2 SP5
BusinessObjects Enterprise XIR2 SP5 + FP5.x
Reproducing the Issue
A report is scheduled to be run on a daily basis - this is a Recurring schedule.
Normally the report runs once a day, at a particular time.
After Daylight Savings Time change, the report runs at the specified time, but immediately after the successful instance, another instance is spawned.
Many more instances spawn after each instance completes.
Cause
This is a known issue: ADAPT01318487. This issue is because of DST and how our code handles this change.
Resolution
There is currently no known fix for this issue. There is however a script that can quickly resolve the problem.
The issue it seems is related to Daily recurring schedules.
What this script will do:
it will run a query to display all your DAILY Recurring jobs
you will have the option to choose your jobs and reschedule them by 1 hour
you will then highlight the same job and change them back by 1 hour
by modifying the schedule times, you are modifying the schedule itself and this will keep the issue of duplicate instances from occurring.
Exact Steps to Complete:
Stop the Job Servers.
Double click on the .hta file.
Change the System Name to that of your CMS name.
Add the Administrator's password.
Click Logon.
Click List All Recurring Instances.
Select All.
Make note of what it says in: Schedule Selected Recurring Instances: Should be 1 hr earlier.
Click Reschedule Selected Recurring Instances.
Choose All instances again and change Schedule Selected Recurring Instances to 1 hour Later.
Click Reschedule Selected Recurring Instances.
Now start your Job Servers.
The issue should not occur again.
The Script is attached here, but please review the SAP Knowledge Base article 1448881 as well

Hi Nicola,
- The multiple spawned instances issue ONLY affects XI3 SP3+ only. For XI3 SP1 and SP2 all Fix Pack levels this is not an issue as it was introduced as a problem in SP3.
- 1568239 notes the Java version and can apply to all O/S environments and is updated to reflect that.
If you are located in Europe you can also apply the patches in advance of the DST change to avoid the problem. If you are in Americas at this point utilizing the clean up scripts for this year is the approach needed to clean up the spawned instances and reschedule the existing schedules.
Thanks,
Chris

So the left side of my iPhone isn't working at all and I even tried turning it off for 5 minutes about 10 million times but nothing is working. Any suggestions on what to do I need help like ASAP!?

So the left side of my iPhone isn't working at all and I even tried turning it off for 5 minutes about 10 million times but nothing is working. Any suggestions on what to do I need help like ASAP!?

Have you performed a reset? Tap and hold the Home button and the On/Off button for approximately 10-15 seconds, until the Apple logo appears. Release both buttons and await restart.

What is the best way to switch off Daylight Saving Time?

What is the best way to switch off Daylight Saving Time for a DST enabled timezone?

I've been looking through the related classes and can't seem to find a way to disable DST in any timezone. Probably because they couldn't think of a good reason to want to know what the non-DST time was during DST.
However, you could easily compute the time without DST if that's what you need.

Dreamweaver CS3 crashes after Daylight Savings Time ends

In Windows XP x64, Dreamweaver CS3 crashes after
Daylight Savings Time ends. There is a technote that seems to
describe the situation exactly.
http://kb.adobe.com/selfservice/viewContent.do?externalId=kb402776&sliceId=1
However...
1) The technote says this happens only with ASP and PHP code.
I'm using ColdFusion. (That's a minor point.)
2) The technote says...
Delete the WinFileCache-AD76BB20.dat file from the
Dreamweaver user configuration folder. Note that on Windows, the
Application Data and AppData folders are hidden by default, so
verify that your Windows Explorer folder options are set to View
Hidden Folders. The location of this file is as follows:
Dreamweaver CS3 on Windows Vista:
C:\Users\[username]\AppData\Roaming\Adobe\Dreamweaver
9\Configuration
Dreamweaver CS3 on Windows XP:
C:\Documents and Settings\[username]\Application
Data\Adobe\Dreamweaver 9\Configuration
However, I coudn't find WinFileCache-AD76BB20.dat in
Documents and Settings or in Program Files (86)\Adobe. (The 86 is
because this is a 32-bit program on a 64-bit machine, but all the
rest is the same.) I then searched both directories for *.dat and
there was no file that looked anything like
WinFileCache-AD76BB20.dat.
.Can anybody help me?
Thanks!

Alan, thanks for the suggestion.
I did the search found the file, deleted it, opened
Dreamweaver CS3, selected the same text -- and it crashed as
before.
THEN I REBOOTED and tried again - NO CRASH. So it seems that
a reboot is an essential part of the fix.
BTW: My situation fit the Technote description exactly. (1)
The crash happened when selecting -- in design or code view --
certain text in a context of HTML intermingled with ColdFusion
code; (2) I had no problem with these files before Daylight Savings
ended; (3) even after that I had no problem with them in Macromedia
Dreamweaver 8 on another machine -- the problem was only on CS3.
So the Technote is correct as far as it goes, but should be
amended as follows:
1) ColdFusion should be included in the types of code that
can be associated with the problem.
2) Instead of deleting WinFileCache-AD76BB20.dat, one should
delete WinFileCache-[whatever].dat.
3) A reboot after the deletion may be required.
Anyway, problem solved.
Thank you!

Switch from daylight saving time to winter time

Hello,
Can somebody describe why it is recommended (note 7417) to shut down the system for a little over two hours? Why is is not enough to deactivate the system 5 minutes before last daylight saving time hour has started and activate it when the winter time is started? Why should we wait until the first hour of winter time has ended?
Note 7417 gives the following example:
'If the hour from 2:00 to 3:00 occurs twice when you change to standard time, you must deactivate the system from 01:55:00 AM until 3:05 AM"
It is not clear, why the system cannot be activated at 2:05 AM after the time is switched...
Thanks in advance,
Yelena

Hi Yelena,
Check the note 102088, it's clearly mentioned about 'double hour' and why it need's to be shout down?.
Regards,
Hari.
PS: Award points if helpful.

UC560 Daylight Saving Time

Hello,
We have a UC560. Once Daylight Saving Time (DST) was initiated we updated the time in CCA to the correct time - one hour ahead.
The problem: The messages being sent to our PC's when a caller leaves a voice message is 1 hour ahead of the actual time.
Please let us know if you may have a solution for this problem.
Thank you,
Dawn

Okay, I ran the update... Two problems here.
1. Now my calendar events between March 11 and March 31st 2007 are off by an hour (although they show the correct time when you open the event to view it).
It doesn't work to delete the event and create a new one... It still shows as the wrong time. the only way I found to fix the time problem is to set each event for the incorrect time zone (I'm in Pacific and have to set it to Arizona).
2. Each "all day event" I scheduled into my calendar show up the day before the actual event date, yet when I open the event they show the correct date. Example - If I scheduled an all day event for April 19th, it appears on my calendar on April 18th. Yet, when I open the event to view the details, it does say "April 19".
The only way I've found to fix the birthday events to the correct day is to delete each one and re-schedule.
I find this highly inconvenient and and huge time waster. My business depends on my calendar being accurrate and I don't have time to adjust hundreds of entries.
If other folks are having this issue, speak up. It would be great if other folks knew they should wait to install this until a fix is issued.
If it's just me... Well, I guess that *****.
What now?

Conversion mapping is losing time zone data during daylight saving time

We have a problem with conversion of Calendars to timestamp with timezone for the last hour of Daylight Saving Time (e.g. 01:00 EDT - 01:59 EDT) where it is being interpreted as Standard Time which is in reality 60 minutes later.
We've written a JUnit test case that runs directly against TopLink to avoid any issues with WAS and its connection pooling.
The Calendar theDateTime comes from an object called TimeEntry which is mapped to a TIMESTAMP WITH TIMEZONE field using conversion mapping with Data Type TIMESTAMPTZ (oracle.sql) and Attribute Type Calendar (java.util).
We are using:
Oracle TopLink - 10g Release 3 (10.1.3.0.0) (Build Patch for Bugs 5145690 and 5156075)
Oracle9i Enterprise Edition Release 9.2.0.7.0 - 64bit Production
Oracle JDBC driver Version: 10.2.0.1.0
platform=>Oracle9Platform
Execute this Java:
SimpleDateFormat format = new SimpleDateFormat("MM/dd/yyyy HH:mm z");
TimeZone tzEasternRegion = TimeZone.getTimeZone("US/Eastern");
Calendar theDateTime = Calendar.getInstance(tzEasternRegion);
theDateTime.setTime(format.parse("10/29/2006 01:00 EDT"));
Persist to the database and execute this SQL:
SELECT the_date_time, EXTRACT(TIMEZONE_REGION FROM the_date_time), EXTRACT(TIMEZONE_ABBR FROM the_date_time), EXTRACT(TIMEZONE_HOUR FROM the_date_time)
FROM time_table WHERE time_table_id=1
This provides the following results:
THE_DATE_TIME EXTRACT(TIMEZONE_REGION FROM the_date_time) EXTRACT(TIMEZONE_ABBR FROM the_date_time) EXTRACT(TIMEZONE_HOUR FROM the_date_time)
29-OCT-06 01.00.00.000000 AM US/EASTERN US/Eastern EST -5
The wrong time zone is in the database. It should be EDT -4. Let's test the SQL that should be generated by TopLink. It should look like the following.
Execute this SQL:
UPDATE time_table SET the_date_time = TO_TIMESTAMP_TZ('10/29/2006 01:00 US/Eastern','mm/dd/yyyy HH24:MI TZR') WHERE (time_table_id=1)
SELECT the_date_time, EXTRACT(TIMEZONE_REGION FROM the_date_time), EXTRACT(TIMEZONE_ABBR FROM the_date_time), EXTRACT(TIMEZONE_HOUR FROM the_date_time)
FROM time_table WHERE time_table_id=1
This provides the same results:
THE_DATE_TIME EXTRACT(TIMEZONE_REGION FROM the_date_time) EXTRACT(TIMEZONE_ABBR FROM the_date_time) EXTRACT(TIMEZONE_HOUR FROM the_date_time)
29-OCT-06 01.00.00.000000 AM US/EASTERN US/Eastern EST -5
Now, execute this SQL:
UPDATE time_table SET the_date_time = TO_TIMESTAMP_TZ('10/29/2006 01:00 EDT US/Eastern','mm/dd/yyyy HH24:MI TZD TZR') WHERE (time_table_id=1)
SELECT the_date_time, EXTRACT(TIMEZONE_REGION FROM the_date_time), EXTRACT(TIMEZONE_ABBR FROM the_date_time), EXTRACT(TIMEZONE_HOUR FROM the_date_time)
FROM time_table WHERE time_table_id=1
This provides better results:
THE_DATE_TIME EXTRACT(TIMEZONE_REGION FROM the_date_time) EXTRACT(TIMEZONE_ABBR FROM the_date_time) EXTRACT(TIMEZONE_HOUR FROM the_date_time)
29-OCT-06 01.00.00.000000 AM US/EASTERN US/Eastern EDT -4
The correct time zone is now in the database. Let's test reading this with the following Java:
System.out.println("cal= " + theDateTime);
System.out.println("date= " + theDateTime.getTime());
System.out.println("millis= " + theDateTime.getTimeInMillis());
System.out.println("zone= " + theDateTime.getTimeZone());
This provides the following results:
cal= java.util.GregorianCalendar[...]
date= Sun Oct 29 01:00:00 EST 2006
millis= 1162101600000
zone= sun.util.calendar.ZoneInfo[id="US/Eastern",...]
The TimeZone object is correct since we are using the US/Eastern regional time zone, but the millis are wrong which makes the time EST instead of EDT. The millis should be 1162098000000.
The conversion from java.util.Calendar to TIMESTAMPTZ loses the actual offset when setting to a regional time zone. It can maintain this info by specifying it explicitly.
The conversion from TIMSTAMPTZ to java.util.Calendar also loses the actual offset even if the correct offset is in the database.
Has anyone else encountered this conversion problem? It appears to be a conversion problem in both directions. I know that the Calendar is lenient by default and will assume Standard Time if time is entered during the repeated 1 o'clock hour at the end of Daylight Saving Time, but the Calendars we are using are explicit in their time, so this would be classified as data corruption.
Nik

Opened an SR. Looks like there is a problem with conversion either in TopLink or in JDBC.

BO-XI R2 daylight saving time

The time in infoview has not changed to accommodate the daylight saving time change.
Version: 11.5.8.8265
Tried to install xir2 edst patch (CHF15_DST), when doing so I get a message stating "MHF1 is needed as prerequisite"...when I try to install MHF1, receive message "No supported XIR2 products detected"
Please advice, thank you.

Symptom
The Integration Kit for Baan driver displays incorrect time data in reports. The time is off by an hour between the dates marking the old Daylight Saving Time (DST) and the new DST change.
Cause
DST has been changed to occur earlier in the year. The Integration Kit for Baan does not pick the new settings up.
Resolution
There are files called ZONEFILES on the BAAN Server. These files must be already updated on the Baan server side.
The Integration Kit for Baan installs our own version of these files in the following folder:
\Baan\Native\lib\ZONEINFO
on the hard drive where the Integration Kit is installed.
Back up these files on the Crystal Reports/Business Objects XI computer, then put a copy of the ZONEFILES from the Baan Server to the computer where the Integration Kit for Baan is installed.

DST Daylight Saving Time

I am using Solaris 9 on Sun hardware. I have set the Time Zone as Asia/Karachi. I dont know how the Daylight Saving Time is enabled with this setting. I just want DST to Trun Off. How can I disable DST for my zone?

Thank you for all the reply. Finally, I've solved the problem. For Tunisia there is no DST according to this page: http://www.timeanddate.com/worldclock/timezone.html?n=253&syear=2010
So, I did the followings:
# vi /usr/share/lib/zoneinfo/src/africa
I modified the rules according to the following:
Rule Tunisia 2006 2008 - Mar lastSun 2:00s 1:00 S
Rule Tunisia 2006 2008 - Oct lastSun 2:00s 0 -
Finally I run the following command:
# zic /usr/share/lib/zoneinfo/src/africa
It is solved my problem!
BR,
Gyorgy

No daylight-saving time auto-adjust?

Using a Lumia 800 in the UK and (believe it or not) only just realised that it hasn't auto-corrected for daylight-saving time. Can't see an option for it either - am I just missing a really obvious setting somewhere? Time/date has many place options but no DST - is that correct?
Solved!
Go to Solution.

I think my experience may help.
I have had hours and hours of frustration with syncing my phone with Outlook calendar because of the way the date and time settings are described on my Nokia phone.
My Timezone is GMT+10 regardless of whether my location is currently in Daylight Saving. The automatic Daylight Saving settings on my computer adjust the time setting by plus 1 hour when Daylight Saving starts.
On the phone, however, setting the time works in a totally weird way. To get the right time on calendar events synced from my computer, I have to set up the phone according to the actual GMT time difference on the day I do the settings. Right now I'm in Daylight Saving so I have to put my Timezone as GMT+11. If I was doing the settings in mid-winter I would have to set the Timezone as GMT+10.
I just discovered this solution today! What a relief. My calendar events now appear at the same time on my phone as on the computer!
However, the whole Nokia time setup arrangement is quite incorrect and that explains the extremely long sequence of complaints on these discussion pages - going back to at least 2004.
It's very straightforward. My Timezone is GMT+10: it's GMT+10 in midsummer and it's GMT+10 in midwinter. A Daylight Saving adjustment doesn't ever change anyone's Timezone.
If Nokia used the correct meaning of Timezone, no-one would be having any problems with syncing events from their computer to their phone.
I have contacted Nokia separately about their serious error in misunderstanding the meaning of Timezone.

Recurring events off by 60 minutes after daylight saving time switch

Similar Messages

Maybe you are looking for