Latest Updates for US 2007 Daylight Saving Time

We held three more webcasts on the US 2007 Daylight Saving Time changes and their impacts on E-Business Suite environments.  Recorded versions of these webcasts are available online.

US Dept of Transportation Logo:

In response to ongoing questions raised on that webcast and Service Requests logged with Oracle Support, we've further clarified the core E-Business Suite DST documentation in a number of areas.  The latest version is dated "February 26, 2007" and includes the following updates to accommodate late-breaking changes in Canadian and Australian timezone participation status:
  • Updated Section 3, Patches Required for E-Business Suite Environments:
    • Added new DST Timezone V4 reference to Step 3.2.2
    • Replaced Patch 5445721 with new Patch 5699501 in Step 3.3.2
  • Added Appendix D, Updates for New Time Zones.
If you haven't already started on your DST 2007 upgrade process, I urge you to review this documentation at your earliest convenience.

Getting Support

If you have any questions about this documentation, please log a Service Request with Oracle Support, using the following information to ensure that the correct Support group is engaged:

Metalink SR entry screen #1:
  • Product:  Oracle Applications Technology Stack
Metalink SR entry screen #2:
  • Type of Problem:  Technology Stack Issues


Jay,I hear you.  I don't have the background myself to comment authoritatively, but here's what I've been able to glean so far.  And, as a tip of the hat to anyone from Oracle Legal, please bear in mind this this is my opinion only, based on loose inductive reasoning, and may have only partial resemblance to what actually led us to this current situation.Oracle froze its Version 3 timezone definitions using authoritative US sources on timezones such as the US Naval Observatory.  It appears that there may have been timing issues (no pun intended) between when those sources reflected Canada's decision to adopt the US 2007 DST changes.  I suspect that those external sources changed after Oracle froze its timezone definitions in Version 3, but that's just my theory. Regards,Steven

Posted by Steven Chan on February 27, 2007 at 06:38 AM PST #

Perhaps I'm off base here, but it appears Oracle essentially missed most (Mountain, Pacific, Newfoundland, Yukon) of the country of does that get by testing?

How about those good DBAs who already patched up their systems who don't read this blog and religiously reload metalink notes for issues they believe resolved?

Posted by jay Weinshenker on February 27, 2007 at 07:15 AM PST #

Jay,Thanks for your comments.  I don't really have visibility into the changes to patch 5865568, since it's a database patch (and I'm part of the Applications Division, which doesn't control database patches).  My *opinion* is that the IT industry -- as a whole -- may have underestimated the degree of work required to gear up for these DST changes.  Here in Oracle, there are a number of questions being raised right now about how our processes can be improved, so that the next regulatory-driven change like this doesn't engender a similar set of fire drills.Good luck with your changeover this weekend.Regards,Steven 

Posted by Steven Chan on March 09, 2007 at 04:36 AM PST #

I appreciate your opinion update on this - to all lawyers, I definitely realize he is speaking personally and not for Oracle.

Here's another one I've gotta complain about. Here, it's Friday at 2.04pm, the last few hours of the work week before DST hits. I just happened to notice (thanks to another Apps DBA) that patch 5865568 (the JVM patch) for 9207 got RELOADED yesterday. On NO documentation (359145.1, 403311.1, etc) is this reloading mentioned at all. No email from Oracle about a patch being reloaded. No explanation on why this patch is 2 TIMES the size of the original (12411591 vs 24840485 bytes)

I mean, sure, there's poorly managing a situation, and then there's POORLY managing a situation.

Please, what gives?

Posted by jay Weinshenker on March 09, 2007 at 06:09 AM PST #

turns out they decided to include stuff for VMS in the patch (as it's a generic). So it doesn't effect my systems. But I'm still a bit miffed that Oracle isn't even following it's own in place systems (for reloaded patches) with something as important as this.

Posted by jay Weinshenker on March 09, 2007 at 06:12 AM PST #

Post a Comment:
  • HTML Syntax: NOT allowed


« July 2016