skip navigation

The New Daylight Savings Time and Oracle Calendar

CITES > calendaring > Oracle Calendar > new DST rules

On This Page:

• Summary
• Procedure
• FAQ
• For More Information

Summary

Because of the U.S. government's recent expansion of Daylight Savings Time (DST), we need to update the Oracle Calendar server so that it knows when the new DST begins and ends.

• Instead of starting on April 1 this year, DST will start on March 11 (three weeks earlier).
• Instead of ending on October 28 this year, DST will end on November 4 (one week later).

After we perform the server update, each user of Oracle Calendar will need to manually adjust any meetings or events that fall within the expanded DST periods. The upgrade patch provided by Oracle does not automatically correct individual users' schedules. Unless users manually change their Calendar entries, they will appear one hour later than the time for which they were originally scheduled.

This applies to any meetings or events scheduled between March 11 and April 1, and between October 28 and November 4. Meetings scheduled outside of these periods should remain unaffected.

To avoid confusion, we recommend that you wait until we update the Oracle Calendar server on Saturday, February 24, 2007, before you start adjusting your Calendar entries.

On Saturday, February 24, 2007, you will receive a notification e-mail confirming that the server has been updated. You should then go into Calendar and adjust the meetings and events in the affected new DST periods (March 11-April 1 and October 28-November 4).

Additional information is provided below. For assistance, contact the CITES Help Desk.

 

Procedure

To reduce potential confusion, please do not adjust your DST meeting times until after we have applied the Oracle Calendar patch to the system on Saturday, February 24, 2007.

All that is required is that you manually move every meeting in the new DST periods back 1 hour.

To further minimize potential confusion, we recommend including meeting times in meeting titles for the new DST weeks.

As a help in this process, we will temporarily maintain a secondary, pre-patched version of the Oracle Calendar database, so that you can check your meeting corrections against the pre-updated version.

To see the pre-patched version of your calendar, go to dst-calendar.cites.uiuc.edu, log in, and navigate to the weeks of the DST change. We recommend that you print these weeks so that you can refer to them when you update your live calendar.

 

FAQ

Can't this be done automatically?

The vendor has not provided us with a way to do this automatically.

Why did you wait so long to apply the patch?

We needed to test the patch extensively before applying it. In addition, we thought it would be easier to manage the changeover and the manual time corrections closer to the actual date of the new DST.

I can't change the times of some of the meetings on my calendar. What's wrong?

You can move only those meetings that you created. If someone else created a meeting on your schedule, only that person can move the meeting. You might want to send them an email to remind them.

How can I tell who added a meeting to my calendar?

Open the meeting. In the upper-left corner, you will see Proposed by: and the name of the person who created the meeting.

Will I have to do this every year?

No. This change is necessary because of the change in Daylight Savings Time. Of course, if the U.S Government changed the rules again next year, then yes, we would all need to adjust again.

If I usually have a designate take care of my calendar, can the designate make all these changes, or do I need to do it myself?

The designate can make the changes as usual.

 

For More Information

From the University of California at Irvine: Oracle Calendar and 2007's new Daylight Saving Time

From Wikipedia: Daylight saving time

From the Calendaring and Scheduling Consortium: Extended Daylight Saving Time Review and Considerations