USA 2007 DST Changes: Frequently Asked Questions for Oracle Database Patches
(Doc ID 402742.1)
Last updated on FEBRUARY 17, 2024
Applies to:
Oracle Database - Personal Edition - Version 7.3.3.0 to 10.2.0.1 [Release 7.3.3 to 10.2]Oracle Database - Enterprise Edition - Version 7.3.0.0 to 10.2.0.1 [Release 7.3.0 to 10.2]
Oracle Database - Standard Edition - Version 7.3.0.0 to 10.2.0.1 [Release 7.3.0 to 10.2]
Information in this document applies to any platform.
Purpose
This is archived content made available during the USA DST 2007 update (DSTv3 and DSTv4).
If you are looking for information on applying DStv4 for upgrades to 10.2.0.4, 11.1.0.6 or 11.1.0.7 please see
<Note 553812.1> Actions for the DSTv4 update in the 10.2.0.4 patchset
<Note 829734.1> Actions for the DSTv4 update in the 11.1.0.6 base release
<Note 568125.1> Actions for the DSTv4 update in the 11.1.0.7 patchset
These notes are more effective and better to use for DST during upgrades.
For information about newer DST updates available, and which time zone definitions are updated, see the following note: <Note 412160.1> Updated Time Zones in Oracle Time Zone File patches
If you are looking for information on applying DStv4 for upgrades to 10.2.0.4, 11.1.0.6 or 11.1.0.7 please see
<Note 553812.1> Actions for the DSTv4 update in the 10.2.0.4 patchset
<Note 829734.1> Actions for the DSTv4 update in the 11.1.0.6 base release
<Note 568125.1> Actions for the DSTv4 update in the 11.1.0.7 patchset
These notes are more effective and better to use for DST during upgrades.
For information about newer DST updates available, and which time zone definitions are updated, see the following note: <Note 412160.1> Updated Time Zones in Oracle Time Zone File patches
Many notes exist which cover the availability of RDBMS patches for the daylight saving time changes in the USA from 2007 onwards. Despite that some questions might remain that hard hard to find in the notes, or there might be questions on how to interpret some of the information in these notes. This FAQ will provide answers and guidance for these issues.
Questions and Answers
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Purpose |
Questions and Answers |
SECTION 100 - GENERIC INFORMATION |
TOP TEN: 101. Which information exists to document this issue? |
101b. Do I need a patch? |
101c. Are any OS patches needed for the database? |
102. Is Oracle7 affected? |
TOP TEN: 103. Is Oracle8 affected? |
104. Is an Oracle8 client affected when connected to a Oracle9 or Oracle10 database? |
105. Is the TIMESTAMP datatype affected? Does TIMESTAMP use a default Time Zone? |
106. Are there any other "RDBMS" issues, like impact on ASM or the CRS? |
107. I'm using a Thin JDBC client, does this need to be updated? |
108. Is Oracle Express Edition affected? |
109. What about Canadian time zones? |
TOP TEN: 111. Are Time Zone file patches or the OJVM patches be included in a CPU |
111b. Are there any conflicts between the CPUs and DST patches? |
TOP TEN: 112. Are the time zone file patch and the OJVM patch linked? |
113. The Oracle10 Agent doesn't start, complains about time zones. |
114. Is there any dependency between the Oracle database and other patches, like the OS. |
121. How about the standalone HTTP server that ships with the Oracle Database? |
191. I don't want to do this again, how do I make my database DST-agnostic? |
SECTION 200 - TIME ZONE FILE PATCHES |
TOP TEN: 201. Is the time zone file patch applied correctly to the database? |
TOP TEN: 202. Is the time zone file patch applied correctly to the client? |
203. How do I test the "version-4" time zone files for Canadian time zones? |
211. What happens if I don't apply the time zone file patch? |
212. Do I patch databases or clients first? |
TOP TEN: 213. Do patches really have to be applied on servers and clients? and at the same time? |
214. Are there different patches for the database and clients? |
TOP TEN: 215. Which clients need the time zone patch? |
216. Why are certain patches being re-released? For example Solaris64bit 9.2.0.7 |
217. Why was the Solaris32 bit 9.2.0.7 patch re-released on 19 January? |
218. The Linux 32bit 9.2.0.7 and Solaris SPARC 64bit 9.2.0.7 patch readme mentions "version 2" files. |
TOP TEN: 221. Does the database need to be down before the time zone files or utltzuv2.sql script can be applied? |
222. Should the client software be exited before applying the patch on the client? |
223. Is any relinking needed after the patches are applied? |
224. Can the Time Zone files be applied as a rolling upgrade in RAC? |
225. Do the one-off patches need to be reapplied after a patchset is installed? |
226. Why is there a difference in file sizes of these patches between patch sets? |
227. Are pre- and post-install steps needed when a patchset containing TZ files is installed ? |
228. How can I recover from not using the pre- and post-install steps on applying new TZ files? |
TOP TEN: 229. I'm receiving ORA-1882 when I query old data after I have applied the time zone file patch |
229b. I'm still getting ORA-1882 after checking the data |
231. How does this issue affect standby databases? |
232. Is there any affect on inter-database communication? |
241. Do the updated Oracle Time Zone files know about the different rules before 2007 ? |
242. Which version of the time zone files is currently in place? |
251. How do I deal with the Oracle demo table ORDERS, which contains a TSTLZ column? |
261. My EST and MST data seems to no longer be affected by DST |
291. Will the utltzuv2.sql script be changed to look for data in the affected time-frame? |
292. Are any changes planned to the way that Oracle uses timestamp data |
TOP TEN: 293. utltzuv2.sql only searches for TSTZ data, how can I find other time zone use? |
SECTION 300 - Oracle JVM (OJVM) PATCHES |
SECTION 400 - OTHER PATCHES |
401. How does a O/S DST patch affect Oracle |
402. Which O/S patch needs to be applied |
411. Does the JDK/JRE in the Database Oracle Home need to be patched? |
412. Can the tzupdater tool be used to update existing JDKs, rather than applying a JDK patch? |
CHANGE LOG |
References |