RE: ALERT - Potentially Serious Problem with DST Patches for PST8PDT Timezone
- From: "Mercadante, Thomas F \(LABOR\)" <Thomas.Mercadante@xxxxxxxxxxxxxxxxx>
- To: <Brandon.Allen@xxxxxxxxxxx>, "oracle-l-freelists" <oracle-l@xxxxxxxxxxxxx>
- Date: Thu, 1 Feb 2007 08:08:45 -0500
I don't know about anyone else.
But I'm shocked that something like this could happen. Oracle *always*
tests everything that they release.
You must have done something wrong Allen.
--------------------------------------------------------
This transmission may contain confidential, proprietary, or privileged
information which is intended solely for use by the individual or entity to
whom it is addressed. If you are not the intended recipient, you are hereby
notified that any disclosure, dissemination, copying or distribution of this
transmission or its attachments is strictly prohibited. In addition,
unauthorized access to this transmission may violate federal or State law,
including the Electronic Communications Privacy Act of 1985. If you have
received this transmission in error, please notify the sender immediately by
return e-mail and delete the transmission and its attachments.
________________________________
From: oracle-l-bounce@xxxxxxxxxxxxx
[mailto:oracle-l-bounce@xxxxxxxxxxxxx] On Behalf Of Allen, Brandon
Sent: Wednesday, January 31, 2007 3:35 PM
To: oracle-l-freelists
Subject: ALERT - Potentially Serious Problem with DST Patches for
PST8PDT Timezone
Oracle-l list,
I just got confirmation from Oracle Support of a new problem I found
with the timezone patches. I've been told a note/alert will be released
on Metalink within a few days once they've worked out the details, but
here is what I think I know so far:
DISCLAIMER: This is for informational purposes only - act on it at your
own risk. I recommend waiting for official instructions from Oracle
before taking any action.
In the v3 and v4 timezone files that have been released recently, the
PST8PDT timezone has been added as a "real" timezone as opposed to just
an alias for another timezone as it was in v2. This means that Oracle
stores the internal timezone ID differently. The timezdif.csv files
that were shipped with the updated utltzuv2.sql scripts erroneously
omitted PST8PDT and the other v2 aliased timezones in the list of
affected timezones to check for. The net result is that if you have any
TSTZ data with the PST8PDT timezone or any of the other newly added v3
timezones*, then you need to back it up (copy to varchar2 column) before
installing the new timezone files and then restore afterwards and this
is regardless of the timeframe.
I haven't done any testing yet to find out exactly what happens with
these timezones if you don't backup/restore them before & after the
patch, but I plan to do that soon and will post my findings. I will
also post an update with the Metalink note number as soon as they tell
me about it.
Regards,
Brandon
*New timezones added in v3:
EST
MST
HST
EST5EDT
CST6CDT
MST7MDT
PST8PDT
America/Indiana/Vincennes
America/Indiana/Petersburg
Privileged/Confidential Information may be contained in this message or
attachments hereto. Please advise immediately if you or your employer do
not consent to Internet email for messages of this kind. Opinions,
conclusions and other information in this message that do not relate to
the official business of this company shall be understood as neither
given nor endorsed by it.
Other related posts:
