|
Academic Computing and Communications Center | |||||||||
|
|
|
|
|
|
|
|
|
|
|
|
|
||||||||||||||
Daylight Savings Time Problem: Applications and Middleware |
||||||||||||||
| None of the application software listed below can possibly function correctly, unless you first update the Daylight Time rules in the underlying operating system. | ||||||||||||||
| Java Applications | ||||||||||||||
If any of your Java applications running in a JRE older than version
1.4.2 SR 6 use time functions, they may report incorrect time during
the extended period of daylight savings time starting in March 2007.
|
||||||||||||||
| UICalendar | ||||||||||||||
|
The Oracle Calendar software on the UICalendar server has been updated to observe the new Daylight Savings Time change dates, so everything you enter now will be fine. Important: However, events that you entered earlier that are scheduled to occur in the extended times of March 11, 2007 to April 1, 2007 or October 28, 2007 to November 4, 2007, may or may not be wrong by one hour. See Daylight Savings Time Problem: UICalendar for important information about what you need to do to correct this. See below. The Oracle Connector for Outlook Connector does not, itself, contain any Daylight Time issues, although it is connecting between two things which both do. |
||||||||||||||
| Microsoft Outlook | ||||||||||||||
|
You need to make sure that the underlying operating system is
updated for the change, and then you need to update Outlook itself.
Calendar events created during the extended periods of Daylight Time
may appear at the wrong times.
Microsoft has provided a tool to fix these problems. !!!Oracle recommends you do not run the Outlook Timezone Update Tool if you are using Oracle Connector for Outlook to connect to UICalendar. Also, if you use Outlook to access a Microsoft Exchange Server, we recommend you contact your Exchange administrators before running the tool. Microsoft advises that users "should minimize the time lag between applying updates to operating systems and running the Time Zone Data Update Tool." This means that you should wait before updating Windows, until you have the Outlook Time Zone Update Tool downloaded, installed, and ready to run.
|
||||||||||||||
| Microsoft Exchange Server | ||||||||||||||
|
Microsoft Exchange Server needs updates in order to function properly after March 11, 2007. These updates are described here: Microsoft Windows: Preparing for daylight saving time changes in 2007 Exchange system managers will also need to run the Outlook Time Zone Data Update Tool, described above with Outlook. |
||||||||||||||
| Novell Netware (ACCC Server Services) | ||||||||||||||
|
OES/NetWare servers in affected United States and Canada time zones
should be updated with DSTShift.nlm, a Novell provided utility. TID 3397648 - Daylight Savings Time Adjustment Tool for Netware Servers
The Novell Client gets its time from the Novell Netware Server. and then synchronizes the time setting on your computer with the Netware Server. Therefore, if your client computer's operating system is not patched or upgraded as specified in this document, the result could be confusion and unintended time changes when your Novell Client connects to the Novell Server and synchronizes. Novell Netware can also run as a Java application. It uses Sun Java. See the section on Java. Also see 3980430: Daylight Saving Time (DST) defaults changing in 2007 and the impact on the NetWare Java Runtime Environment (JRE) Links: |
||||||||||||||
| Novell Groupwise | ||||||||||||||
| Both the server and clients are affected for Novell Groupwise. | ||||||||||||||
| Blackboard Learning System | ||||||||||||||
|
Blackboard depends on the underlying operating system and on Sun Java.
Blackboard suggests running the Sun Java Updater Tool,
listed above under Java Applications.
Blackboard Support Bulletin: Timestamps do not reflect daylight savings time |
||||||||||||||
| Oracle Database | ||||||||||||||
There are two articles of interest.
You must have a current, paid, Oracle support contract to view these, at https://metalink.oracle.com/
|
||||||||||||||
| IBM DB2 Database | ||||||||||||||
|
The DB2 Database system mostly relies on the underlying Operating System
for time services. However, there are significant dependencies involving
Java. These are discussed here: Changes to daylight savings time (DST) in the U.S. and Canada affect IBM DB2 products |
||||||||||||||
| MySQL Database | ||||||||||||||
|
The MySQL database system contains time zone tables, which are populated from
the system time zone data.
Therefore, after you update the base operating system tables,
you should then re-populate the database tables from the operating system.
5.11.8. MySQL Server Time Zone Support AIX MySQL users should pay particular attention to the IBM APARs that update the Zoneinfo data files on AIX. |
||||||||||||||
| Tivoli Storage Manager (ADSM) | ||||||||||||||
| Though there are no Daylight Savings Time dependencies in the TSM server or client programs per se, you must insure that your own client computer's operating system is updated or patched. Failure to do that will result in session failure due to unsynchronized clocks between client and server, or time-warp errors attempting to back up files created in the future, or restore recently backed-up files which might have been backed up in the future. We have found that TSM is tolerant of a client system clock being a few minutes off, but a whole hour is too much. | ||||||||||||||
| Lotus Notes, Other Lotus Software | ||||||||||||||
Lotus Notes has several problems with this change:
|
||||||||||||||
| DST Problem | Previous: 5. PDAs | Next: 7. UICalendar |
| 2007-3-6 ACCC documentation |
|
