Our strategy is to not apply them and migrate to 9iR2 instead.  At least
that's the plan for now, until we find out something won't work with 9i.
It's probably cheaper to do in the long run, and it'll be supported thru
2005, unlike 8.1.7, which "expires" at the end of this year.

Rich

Rich Jesse                           System/Database Administrator
[EMAIL PROTECTED]                  Quad/Tech Inc, Sussex, WI USA


> -----Original Message-----
> From: Mandar A. Ghosalkar [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, July 29, 2003 5:55 PM
> To: Multiple recipients of list ORACLE-L
> Subject: 8.1.7.4 interim patch management strategy
> 
> 
> Hello All,
> 
> There are 188 interim patches after 8.1.7.4 patchset. I know that
> 8.1.7.4 is the last patchset.
> 
> 1. What methods/strategy do you'll have for installing patches on a
> 8.1.7.4 64 bit hp-ux 11.11 database?
> 2. Is there opatch for 8.1.7.4? AFAIK opatch is only for 9i.
> 3. Should one install all the applicable patches (around 180 
> individual
> patches)?
> pessimistic (wait for the bug to hit and db to crash)
> optimistic (install applicable patches)
> 4. How to manage the interdependencies between these 180 individual
> patches?
> 5. Can we create a hp unix patch depot like "thing" for all 
> these oracle
> patches? 
> 
> pls dont advise putting an enhancement request and upgrading to 9i/10i
> :-)
> 
> Thanks,
> Mandar
-- 
Please see the official ORACLE-L FAQ: http://www.orafaq.net
-- 
Author: Jesse, Rich
  INET: [EMAIL PROTECTED]

Fat City Network Services    -- 858-538-5051 http://www.fatcity.com
San Diego, California        -- Mailing list and web hosting services
---------------------------------------------------------------------
To REMOVE yourself from this mailing list, send an E-Mail message
to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in
the message BODY, include a line containing: UNSUB ORACLE-L
(or the name of mailing list you want to be removed from).  You may
also send the HELP command for other information (like subscribing).

Reply via email to