Changes to daylight savings time (DST) in the U.S. and Canada affect IBM DB2 products

Technote (FAQ)


Question

In March 2007, the effective dates of Daylight Savings Time (DST) in the U.S. and Canada will change. You must take action to address this issue if you are using DB2® for Linux®, UNIX®, and Windows®, DB2 Universal Database™ (DB2 UDB), DB2 Connect™, DB2 Query Patroller, DB2 Control Center, and user-created Java™ applications.

Answer

Extended DST for the United States and Canada begins in March, 2007. The new DST start and end dates are:


Start date: Second Sunday of March
End date: First Sunday of November

DB2 Version 9 for Linux, UNIX, and Windows, DB2 UDB Versions 7 and 8, and DB2 Connect are affected by the change in DST because of their dependencies on the underlying operating system for time-related functions. You need to ensure the operating systems on which these products are installed are DST compatible. Links to DST-related information are provided by operating system vendors at the bottom of this document.

The DB2 Control Center, DB2 Query Patroller, and user-created Java applications are affected because of their dependency on the Java SDK. Refer to the Information Management Assessment below to determine if you are affected.

DB2 fix pack downloads
If the action you need to take (refer to the "Action required" in the charts below) includes the installation of a DB2 fix pack (or FixPak), you can find them on the DB2 fixes by version web page.

APARs
APAR IY91240 for DB2 has been opened to address the DST change for DB2 Version 9.
APAR IY90463 for DB2 has been opened to address the DST change for DB2 UDB Version 8.

Required actions
Ensure the operating systems on which DB2 Version 9 for Linux, UNIX, and Windows, DB2 UDB Versions 7 and 8, and DB2 Connect are installed are DST compatible.

If you are impacted based on the Information Management Assessment below, the actions you must take to ensure your DB2 environment is DST-compatible depend on the version of the DB2 database product that you are using, as shown in the following tables.

Note: The IBM Java Time Zone Update (JTZU) tool listed in the following tables will function only on SDKs and JREs that are made available by IBM. Before applying the patch with JTZU, you need to stop DB2. Refer to the JTZU utility for details.

DB2 Version 9 for Linux, UNIX, and Windows

Operating system Action required
Solaris SPARC Take one of the following actions:
  • Apply DB2 Version 9.1 Fix Pack 2 or later, which includes Java fixes for the DST change.
    * If you apply the fix pack, you obtain more than just the fixes for the DST change. Refer to the fix pack APAR list to see the full list of APAR fixes included in the fix pack.
    --or--
  • Upgrade to IBM® Java SDK 5 Service Release 3 for Solaris Sparc 64.
    * Use this method if you want to upgrade only the Java SDK.
    --or--
  • Apply the IBM Java SDK fix using the IBM Java Time Zone Update tool.
    * Use this method if you want to patch only the IBM Java Time Zone data. It allows you to make minimum changes to address the DST change.
Solaris x86-64 No action needed.
DB2 Version 9.1 for Solaris x86-64 ships IBM® Java SDK 5 Service Release 3 for Solaris AMD64/EM64T, which already contains the US and Canadian DST fix.
All other operating systems
(Windows, Linux, HP-UX, and AIX®)
Take one of the following actions:
  • Apply DB2 Version 9 Fix Pack 2 or later, which includes Java fixes for the DST change.
    * If you apply the fix pack, you obtain more than just the fixes for the DST change. Refer to the fix pack APAR list to see the full list of APAR fixes included in the fix pack.
    --or--
  • Apply the IBM Java SDK fix using the IBM Java Time Zone Update tool.
    * Use this method if you want to patch only the IBM Java Time Zone data. It allows you to make minimum changes to address the DST change.

Note: On DB2 Version 9.1 running on UNIX and Linux, you must use the IBM Java Time Zone Update tool to reapply the Java SDK fix for DST if you take one of the following actions:
  • Downgrade from DB2 Version 9.1 Fix Pack 2 to DB2 Version 9.1 without any fix packs or to DB2 Version 9.1 Fix Pack 1.
  • Apply the DST fix with IBM Java Time Zone Update and then reapply DB2 Version 9.1 without any fix packs or reapply DB2 Version 9.1 Fix Pack 1.

    DB2 Universal Database Version 8

    Operating system Action required
    AIX Take one of the following actions:
    • Ensure the operating system JDK is DST compatible.
      --or--
    • Apply the IBM Java SDK fix using the IBM Java Time Zone Update tool.
      * Use this method if you want to patch only the IBM Java Time Zone data. It allows you to make minimum changes to address the DST change.
    HP-UX Take one of the following actions:
    • Ensure the operating system JDK is DST compatible.
      --or--
    • For IBM Java SDK, apply the DST fix using the IBM Java Time Zone Update tool.
      * Use this method if you want to patch only the IBM Java Time Zone data. It allows you to make minimum changes to address the DST change.
      --or--
    • For HP JDK 1.3.1, upgrade to HP SDK 1.3.1.20.
      --or--
    • For HP JDK 1.3.1, apply the DST fix using the HP TZUPDATER131 tool.
      * Use this method if you want to patch only the HP Java Time Zone data. It allows you to make minimum changes to address the DST change.
    Linux Take one of the following actions:
    • Ensure the operating system JDK is DST compatible.
      --or--
    • Apply the IBM Java SDK fix using the IBM Java Time Zone Update tool.
      * Use this method if you want to patch only the IBM Java Time Zone data. It allows you to make minimum changes to address the DST change.
    Solaris Take one of the following actions:
    • Ensure the operating system JDK is DST compatible.
      --or--
    • For IBM Java SDK , apply the DST fix using the IBM Java Time Zone Update tool.
      * Use this method if you want to patch only the IBM Java Time Zone data. It allows you to make minimum changes to address the DST change.
      --or--
    • For SUN JDK 1.3.1, upgrade to Sun J2SE v1.3.1_20.
    Solaris x86-64 DB2 UDB Version 8.2 for Solaris x86-64 ships a SUN JDK 1.4.2 for the DB2 installer only and requires a 64-bit JDK 5 for building and running Java applications. Apply the DST fix to the SUN JDK(s) installed on your Solaris x86-64 system using the SUN tzupdater tool.
    Windows Take one of the following actions:
    • Apply DB2 UDB Version 8.1 FixPak 16 which includes Java fixes for the DST change.
      * If you apply the fix pack, you obtain more than just the fixes for the DST change. Refer to the fix pack APAR list to see the full list of APAR fixes included in the fix pack.
      --or--
    • Apply the IBM Java SDK fix using the IBM Java Time Zone Update tool.
      * Use this method if you want to patch only the IBM Java Time Zone data. It allows you to make minimum changes to address the DST change.

    DB2 Universal Database Version 7

    Operating system Action required
    Linux for S/390® only
    • Apply the DST fix using the IBM Java Time Zone Update tool.
      * This action will patch only the IBM Java Time Zone data. It allows you to make minimum changes to address the DST change.
    All other operating systems with IBM, SUN, or HP Java SDK


    IBM Java SDK 1.3.1 SR10 + ifix by platform can be found in the following links:

    IBM Java SDK 1.3.1 SR10 + ifix by platform Download URL Readme
    IBM Java SDK 32-bit for AIX SDK Package Readme
    IBM Java SDK 64-bit for AIX SDK Package Readme
    IBM Java SDK 32-bit for Linux on Intel SDK Package Readme
    IBM Java SDK 64-bit for Linux on Intel SDK Package Readme
    IBM Java SDK 32-bit for Linux on iSeries and pSeries SDK Package Readme
    IBM Java SDK 31-bit for Linux on zSeries SDK Package Readme
    IBM Java SDK 32-bit for Windows SDK Package Readme
    IBM Java SDK 64-bit for Windows SDK Package Readme


    DB2 Universal Database Version 6

    Operating system Action required
    All operating systems IBM Java SDK 1.1.8 is out of support and does not have the US or Canadian DST fix. If any one of the affected products is used, upgrade DB2 UDB Version 6 to DB2 UDB Version 8 or DB2 Version 9.


    Information Management Assessment

    The table below lists the product and the dependency it has with obtaining date and time information from the operating system or IBM Java SDK.

    Affected Products Dependency Comments
    DB2 database products for Linux, UNIX, and Windows

    DB2 Connect
    Operating system For retrieving date and time values for the database, the database system will make standard calls to the operating system. If you are in an affected time zone, you need to install the relevant operating system patches and restart your DB2 instances.
    DB2 Query Patroller Operating system and Java SDK Query Patroller uses Java and non-Java code working together. The Java code obtains time stamps from the Java SDK. The non-Java code obtains time stamps from the operating system. You must apply the DST fix on both the Java SDK and the operating system. Otherwise, Query Patroller might encounter unexpected problems such as a completion time that is before a start time for a given query.
    The Control Center Operating system and Java SDK The Control Center uses Java SDK classes (for example, Date and Calendar) to get the current time, time stamps, and formatting for time. Without the Java SDK patch, from March 11 through April 1 and from October 28 through November 4, the time value returned by the Java SDK will display an incorrect value that will either be an hour later or an hour earlier due to the change in DST for 4 weeks out of the year. This affects any tools that display time. For the Task Center specifically, scheduled jobs run with 1 hour difference.
    User-created Java applications Operating system and Java SDK For user-created Java applications and Java routines if they are affected, it is because of a dependency on the Java SDK, not on DB2.

    The IBM DB2 Driver for JDBC and SQLJ (Type 4 driver): Not impacted. The impact is only on applications that are dependent on the time values returned from the Java SDK.

    The DB2 JDBC Type 2 Driver: The problem affects JDBC client applications that are running in the affected time zones and use any of the following methods:
  • CallableStatement.getDate
  • CallableStatement.getTime
  • CallableStatement.getTimeStamp
  • PreparedStatement.setDate
  • PreparedStatement.setTime
  • PreparedStatement.setTimeStamp
  • ResultSet.getDate
  • ResultSet.getTime
  • ResultSet.getTimeStamp

    Updating your Java SDK with the time zone fix resolves the problem; that is, you don’t need to recompile applications after installing the Java SDK with the time zone fix.

    Java routines (Java stored procedures and Java user defined funtions): There is no direct impact on Java routines. From a routines perspective, no time stamps are used directly except to convert date and time values passed to the stored procedures as SQL objects. The code used for this conversion is java.sql.Time/Data/Timestamp.valueOf(). These functions do not rely on the strings that they receive to be in a specific time zone: therefore, the DB2 database product is unaffected.

    However, you might have written your own Java routines that rely on retrieving accurate time stamp information.

    Any applications using the Java SDK without the time zone fix that rely on the Java SDK for time stamps will have a problem. Since the database system gets the time from the operating system, the database and Java applications could be out of sync if the time zone changes are applied to the OS but not the Java SDK.


  • Operating system DST information
  • AIX operating system
  • HP operating system
  • HP-UX 11.23
  • HP-UX 11.11
  • HP-UX 11.0
  • Linux operating system
  • Novell SUSE
  • Red Hat
  • Microsoft Windows operating system
  • Sun Solaris operating system

    Recent Change History

    November 27, 2007
  • Updated v8 Windows info with fixpak 16 and removed New Brunswick and Quebec comment.

    March 6, 2007
  • Included DB2 UDB Version 8.2 for Solaris x86-64 DST information.

    March 1, 2007
  • Provided Sun JDK 1.3.1_20 stripped tar download.
  • Corrected that IBM JTZU will NOT detect Sun JDK shipped with DB2 UDB.

    Feb 15, 2007
  • Added new IBM JTZU and HP TZUPDATER131 information.

    Feb 9, 2007
  • Added IBM JDK 1.3.1 SR10 + ifix Readme links.

    Feb 8, 2007
  • Added comments for New Brunswick and Quebec Canadian time act.

    Feb 1, 2007
  • Clarified the IM assessment table that the DB2 Java GUI tools are OS and JDK dependent.

    Jan 24, 2007
  • Removed JDK 5 SR3 option from DB2 V9.1 for HP IPF.

    Jan 22, 2007
  • Added DB2 Version 9.1 for Solaris x86-64 support in the DB2 Version 9 table.
  • Removed JDK 5 SR3 option from DB2 Version 9.1 for HP PA RISC.
  • Clarified DST fix for DB2 UDB Version 7 with IBM, SUN, and HP JDK.
  • Provided HP 1.3.1.19 updated URL.

    Jan 17, 2007
  • Provided Red Hat operating system DST information.
  • Clarified that the IBM JTZU only functions SDKs and JREs that are made available by IBM.

  • Related information

    DB2 fixes by version
    Java time zone update tool
    IBM-wide product alerts
    Daylight saving time alert
    Location of JDK used by DB2

    Cross Reference information
    Segment Product Component Platform Version Edition
    Information Management DB2 Connect AIX, HP-UX, Linux, Solaris, Windows 2000 9, 8, 7, 6 All Editions
    Information Management DB2 Query Patroller AIX, HP-UX, Linux, Solaris, Windows
    Information Management DB2 Connect Unlimited Edition for iSeries All Versions All Editions

    Rate this page:

    (0 users)Average rating

    Add comments

    Document information


    More support for:

    DB2 for Linux, UNIX and Windows

    Software version:

    6, 7, 8, 9.1

    Operating system(s):

    AIX, HP-UX, Linux, Linux iSeries, Linux pSeries, Linux xSeries, Linux zSeries, Solaris, Windows

    Software edition:

    Enterprise Server, Express, Personal, Personal Developer's, Workgroup Server

    Reference #:

    1248542

    Modified date:

    2007-03-06

    Translate my page

    Machine Translation

    Content navigation