| Oracle FAQ | Your Portal to the Oracle Knowledge Grid | |
 |
 | |||
| Oracle FAQ | Your Portal to the Oracle Knowledge Grid | |
|
| |||
Home -> Community -> Mailing Lists -> Oracle-L -> RE: DST Strategy
Looks good. On the database side database restartability is not an
issue since it doesn't have to be shut down in the first place. On the
java side I cannot comment.
I would go straight to version 4 and get it overwith, or eventually you will do analogously the same thing again. (which is what I am doing).
The reason is that someone somewhere may decide to experiment with these data types, and it can be confusing enough as it is before receiving the wrong answers. Then of course you need to update.
While your at it, check your DBTIMEZONE is what you want, not that it makes a whole lot of difference, especially if you always use format masks, but for the most part it is best that it is consistent, and it is easy now. It is for timestamp with local time zone. But once using the datatype, changing DBTIMEZONE is hardly practical.
Joel Patterson
Database Administrator
joel.patterson_at_crowley.com
x72546
904 727-2546
-----Original Message-----
From: oracle-l-bounce_at_freelists.org
[mailto:oracle-l-bounce_at_freelists.org] On Behalf Of Parvez Bashir
Sent: Wednesday, February 21, 2007 10:51 PM
To: oracle-l_at_freelists.org
Subject: DST Strategy
Hi all,
Our DB team came up with the following DST strategy in an attempt to
balance
risk with patch application resource costs for a target space of 73
dev/test
and 55 production databases (2 8i, 35 9i, 18 10g).
This includes Solaris, Aix, and Linux servers.
Note: OS DST TZ patches have been applied across the board by SA's. We
are
currently on an active migration path from Oracle 9i to Oracle 10g.
No action required by Oracle. None taken. We have no 8i databases with
JVM
installed.
We have no time zone columns in database and no PL/SQL code with time
zone
types. No action taken.
We have no time zone columns (outside of the dictionary) in the
database. We
applied TZ patches to all Oracle 10g databases. However, we did not
alter
any data in the data dictionary after the utlzuv2.sql output (after
evaluating a metalink note).
We have several databases with OJVM is installed. Only two of these
databases contain java objects. One of the databases with the Java
objects
does not reference time. The other uses java time but not time zone. We
are
planning to apply the patch in the later DB.
We are applying OJVM DST patches across the board for all 10g databases
with
JVM installed.
We are evaluating the patch/work around.
Any comments on the above strategy? Are we on a relatively safe path?
What
is the worst that can happen if a DST patch (TZ or JVM) is not applied?
Are
there any potential issues with database restartability?
Parvez
-- http://www.freelists.org/webpage/oracle-l -- http://www.freelists.org/webpage/oracle-lReceived on Thu Feb 22 2007 - 07:54:02 CST
 |
 |