RE: 10.2.0.1 DST patchset
- From: <Joel.Patterson@xxxxxxxxxxx>
- To: <sbootsma@xxxxxxxxxxxxxx>, <premjhere@xxxxxxxxx>, <oracle-l@xxxxxxxxxxxxx>
- Date: Wed, 7 Feb 2007 13:14:11 -0500
Yes, for my version, I have printed out 10 notes, and looked at more.
My summary instructions are better listed in original post. One of the
reasons I posted it was in all the reading, as the facts unravel, I
found to be true that you come away with the impression that you might
not even check for the 4689959 patch because of note 359145.1.
I'm still confused and I have only one of six 10.2.0.1 databases left
(of 3 servers). I figure I've done so much stuff, most if it doesn't
really affect anything, (I only have scheduler data), that I'll just
finish and forget it.
P.S. Don't forget about the editing you have to do to utltzuv2.sql if
JAVA is not installed.
Joel Patterson
Database Administrator
joel.patterson@xxxxxxxxxxx
x72546
904 727-2546
________________________________
From: Sam Bootsma [mailto:sbootsma@xxxxxxxxxxxxxx]
Sent: Wednesday, February 07, 2007 12:29 PM
To: premjhere@xxxxxxxxx; Patterson, Joel; oracle-l
Subject: RE: 10.2.0.1 DST patchset
I concur. I applied my first patch (a CPU) to a 10gAS a couple months
back. As I recall, one of the earlier instructions in the readme was to
contact Oracle Support if another one-off patch was already installed.
This was true for us, so I dutifully set up a SR. After a lot of going
back-and-forth I was told they can not be 100% sure that applying the
CPU will not impact the patch that is already there. I tried applying
the patch in our test environment and discovered that applying the patch
rolled back the one-off patch that was already installed. Then
re-applying the one-off patch rolled back the CPU I was trying to
install.
Why couldn't Oracle Support tell me that right away? Or why couldn't
that it be mentioned in the readme that came with the CPU that existing
patches may be rolled back (instead of telling me to set up an SR)?
I find the same problem with the DST ... just wading through a lot of
metalink notes that continually point to other metalink notes. There
must be an implementation that makes it easier for DBAs to apply these
patches.
Sam Bootsma
Oracle Database Administrator
Information Technology Services
George Brown College
Phone: 416-415-5000 x4933
Fax: 416-415-4836
E-mail: sbootsma@xxxxxxxxxxxxxx <mailto:sbootsma@xxxxxxxxxxxxxx>
________________________________
From: oracle-l-bounce@xxxxxxxxxxxxx
[mailto:oracle-l-bounce@xxxxxxxxxxxxx] On Behalf Of Prem
Sent: February 7, 2007 12:11 PM
To: Joel.Patterson@xxxxxxxxxxx; oracle-l
Subject: RE: 10.2.0.1 DST patchset
The most horrible patch I have ever applied . Applying a patch
cannot be made more complex than this. Oracle has did that.
Understanding "what/how to do" for this DST patch is itself a
herculean task . I wonder why can't oracle have a single, clear
document for each patch. They seem to generate work.
Jp.
Other related posts:
