Oracle FAQ Your Portal to the Oracle Knowledge Grid

Home -> Community -> Mailing Lists -> Oracle-L -> DST Strategy

DST Strategy

From: Parvez Bashir <>
Date: Wed, 21 Feb 2007 22:51:02 -0500
Message-ID: <BAY131-F36120F55B4BE26C5A9AACCBC8F0@phx.gbl>

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.

  1. Oracle 8i DST Patches

No action required by Oracle. None taken. We have no 8i databases with JVM installed.

2. Oracle 9i TimeZone DST Patches

We have no time zone columns in database and no PL/SQL code with time zone types. No action taken.

3. Oracle 10g TimeZone DST Patches

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).

4. Oracle 9i OJVM DST Patches

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.

5. Oracle 10g OJVM DST Patches

We are applying OJVM DST patches across the board for all 10g databases with JVM installed.

6. Grid Control

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?


Find a local pizza place, movie theater, and more….then map the best route!
Received on Wed Feb 21 2007 - 21:51:02 CST

Original text of this message