RE: Oracle and DST changes
- From: "Mercadante, Thomas F \(LABOR\)" <Thomas.Mercadante@xxxxxxxxxxxxxxxxx>
- To: "Allen, Brandon" <Brandon.Allen@xxxxxxxxxxx>, <oracle-l@xxxxxxxxxxxxx>
- Date: Wed, 24 Jan 2007 07:57:54 -0500
Brandon,
Shutting down all instances before applying patches is the SOP. I agree
with you in this one instance - there is no need to shut down the
instances to copy the files the way you did. The only problem is that
the Oracle inventory on your machine does not know about the patch that
you manually installed. Again, for this one patch, it may not matter
much. But I will be running OPatch on my 10.2 instance to install the
patch just for this reason.
The other thing that I read was that the Oracle databases need to be
restarted to make these changes sticky within the database. I think I
saw that these files are read at instance startup time only. So that is
also a good reason to have the DB's shut down.
Tom
--------------------------------------------------------
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: Allen, Brandon [mailto:Brandon.Allen@xxxxxxxxxxx]
Sent: Tuesday, January 23, 2007 5:51 PM
To: Mercadante, Thomas F (LABOR); oracle-l@xxxxxxxxxxxxx
Subject: RE: Oracle and DST changes
I hope I'm not beating this subject to death, but it seems a lot of
people are interested in it so here is another thing I found
interesting. The 10.2 patch (5601428) for installing the new
utltzuv2.sql and timezdif.csv files (which are just for checking to see
if you have affected data, not for actually fixing it) says the
following in the README.TXT file:
# Patch Special Instructions:
# ---------------------------
# Make sure all instances running under the ORACLE_HOME being patched
# are cleanly shutdown before installing this patch. Also ensure that
# the tool used to terminate the instance(s) has exited cleanly.
Now, why would you have to shutdown your instance just to install this
SQL script and CSV file? Of course I didn't want to shutdown my
instance, so I just extracted the .sql and .csv files and put them in
the correct directories ($ORACLE_HOME/rdbms/admin &
$ORACLE_HOME/oracore/zoneinfo, repectively) and then I ran the script
and it worked just fine - returning no affected data, as expected.
I don't have a lot of experience with patching, so maybe I'm missing
something here. Can someone please tell me if there is some reason why
I should install this patch instead of just manually extracting the
files, and if so, why this simple patch would require the instance to be
shutdown, or is that just standard procedure that you have to shutdown
for all patches, even if it's not really necessary?
Thanks,
Brandon
________________________________
From: Mercadante, Thomas F (LABOR)
[mailto:Thomas.Mercadante@xxxxxxxxxxxxxxxxx
<mailto:Thomas.Mercadante@xxxxxxxxxxxxxxxxx> ]
I saw that and reran the utltzuv2.sql file against my 10g database
(10.2.0.2) and it reports nothing to be concerned about.
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: