Sundial Updated for Daylight Saving Time
On this page:
Background Information
Beginning in 2007, Daylight Saving Time (DST) starts three weeks earlier and ends one week later than in previous years as a result of the Energy Policy Act of 2005. This change impacts many systems and applications, including the Oracle Calendar (Sundial).
The Oracle Calendar server has been patched to include the new Daylight Saving Time rules. The Oracle-issued patch caused previously scheduled meetings to display one hour later than expected during the affected weeks (March 11th to April 1st and October 28th to November 4th). Meetings already scheduled for 2008 and beyond during the affected four weeks are also displayed one hour earlier.
IT Services developed a script to go with the Oracle Calendar server patch. The script automatically moved most meetings during the revised Daylight Saving period back to their correct time. Meetings that were successfully moved are identified with a “DST-” prefix added to the meeting title.
Starting on Tuesday, February 20th, Sundial meeting owners or designates for meeting owners need to verify that their meetings are scheduled for the correct times. If a meeting time is incorrect, the owner or designate for the meeting owner will need to manually move the meeting back to the originally scheduled time. All Sundial users need to accept the meeting invitations for meetings that were moved.
Meetings added to Sundial after server update on February 20 will show the correct start and stop times.
| Year | Affected Dates | Recommended Action |
|---|---|---|
| 2007 | Spring: March 11–March 17 March 18–March 24 March 25–March 31 April 1 Fall: October 28–November 3 November 4 |
|
| 2008 | Spring: March 16 –April 6 Fall: October 26–November 2 |
|
| 2009 | Spring: March 15 –April 5 Fall: October 25–November 1 |
|
Moving Meetings Back to Originally Scheduled Times
Note: Only meeting owners or designates for meeting owners can change meeting times.
For reference, a copy of your original meeting schedule will be available on a separate server from February 20 to March 11. You can view your original meeting schedule (or the schedule of someone for whom you are a designate) on the web at http://sundial-pre2.stanford.edu/ . The calendar on this server is provided for reference only; do not make any changes to it.
- Point your web browser to http://sundial-pre2.stanford.edu/ to access your reference calendar.
Note: You may see a message that says there is a problem with the web site's security certificate. Choose the option that lets you continue to this web site. (Your choices vary depending on the browser that you are using.)
- On your reference calendar, navigate to the affected dates. Click the Week View icon
to set the agenda to the Weekly View.
- To print a copy of the reference calendar, go to your browser's File menu and click Print to print out your agenda for the three affected weeks in spring (Mar. 11–Apr. 1) and one affected week in the fall (Oct. 28–Nov. 4).
- Access your current Sundial agenda. You can use either the desktop client or the Sundial Calendar web site at http://sundial.stanford.edu. Set your agenda to the Week View.
- Compare your current agenda with your reference calendar. Meetings that were moved automatically to the correct time have a "DST-" prefix added to the meeting title. Meetings that have not moved automatically need to be adjusted manually. Correct any meetings to match the proper start time by dragging them to the correct time or opening them and changing the start time.
Note: Resources in Sundial, such as conference rooms, will also need to be manually adjusted for meetings that were not moved automatically. Meeting owners may encounter resource conflicts when trying to reschedule a meeting that includes a resource that is already in use for a prior meeting because of the time change.
Known Issues
- The reply status of all invitees is lost for all meetings. Meeting attendees need to reconfirm their attendance at these moved meetings.
- The reminders for recurring meetings default back to the default reminder setting of the invitee. Users may wish to go back and adjust this for important meetings.
- The access level for all Public meetings changed to Normal. The meeting owner or the designate of the meeting owner may want to change the access level back to Public.
- Some PDA users have had difficulty synching with the moved meetings.
Additional Information
Additional support is available by submitting a HelpSU request.


