Skip to Content
author's profile photo Former Member
Former Member

Daylight Savings Problem

Version 11.5 MII

I have a quick question about a Daylight savings problem we are experiencing since yesterday. All of the MII queries that have "Date between [SD] and [ED]" are displaying the ED as one earlier which is causing problems for people. I looked on the servers to see if I just had to adjust the time, but everything looked good.

It was recommended that I download the Java Timezone patch to fix this problem ( We installed this on our DEV server and it did not solve the problem so we are running out of options. What should we do?

Add a comment
10|10000 characters needed characters exceeded

Related questions

1 Answer

  • Posted on Oct 28, 2008 at 07:33 PM

    Hi Chip,

    You may also want to google the OS DST patches available. They should have addressed it last year, but perhaps not.

    Good luck,


    Edited by: Michael Appleby on Oct 28, 2008 8:34 PM

    Add a comment
    10|10000 characters needed characters exceeded

    • Chip,

      This username and password is the same one you would use to download the SAP MII software or enter a support ticket. You may not have a login to this as your administrator may. It is something your SAP Super Administrator must create for you.

      Here is basically what the note is saying I believe you found the answer already thought with the TZUpdater.

      Sun has proposed two workarounds to address these issues

      1. Apply the tzupdater tool with the -bc (backward compatibility) flag. If the tool has not been previously run this will update your installation to the latest available time zone data but will not add data for the EST, MST and HST IDs. If the tool has been previously run or your time zone data is already up to date you can run the tool with the -f (force) and -bc flags. This causes the data for the EST, MST and HST IDs to be removed from your installation. For more details on the tzupdater tool, please refer to

      2. Manually remove the three time zone data files, EST, MST, and HST in the <JDK_HOME>/jre/lib/zi directory (or <JRE_HOME>/lib/zi).

      Both workarounds have the effect of removing the data files for EST, MST and HST. When the system can't find the data files for EST, MST or HST it will fall back to using America/New_York for EST, America/Denver for MST, and Pacific/Honolulu for HST. These alternates observe daylight savings time and are thus compatible with the JDK's traditional behavior.

      Note that by applying the above workarounds you choose compatibility with the JDK's traditional behavior over compatibility with the Olson time zone standard for the EST, MST and HST time zone IDs. Because the Olson definition for these three IDs is fairly recent (late 2005) and the availability of this data in a Java SE release is even more recent (mid 2006) Sun expects few current applications will require strict Olson compatibility.

      According to the following SUN Java Bug links:

      There are issues with the "tzupdater" tool that updates the timezone information for certain JDKs.

      Your best bet is to upgrade to Java 1.4.2_13 or greater JDK/JRE 5.0u8 and above.

      This note applies for all versions of Java.

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.