RE: Doc.ID 756671.1 Oracle Recommended Patches
Date: Tue, 21 Apr 2009 18:35:26 +0200
I normally apply them when setting up a new environment or after upgrading an existing one, but I don't (yet) actively apply them on existing stable environments. Mainly because our customers often don't have an active patching policy and it's hard to convince them to patch a system which is not giving any problems (yet). Mind you that some of these bugs fixed are bugs that are quite nasty, like a bug in flashback database. If you hit that one, it's to late to patch.
Oracle Database Administrator
tel. +32 (0)3 451 23 82
From: oracle-l-bounce_at_freelists.org [oracle-l-bounce_at_freelists.org] On Behalf Of Laimutis.Nedzinskas_at_seb.lt [Laimutis.Nedzinskas_at_seb.lt] Sent: 21 April 2009 17:40
Subject: Doc.ID 756671.1 Oracle Recommended Patches
Is anyone patching database according to this:
Subject: Oracle Recommended Patches -- Oracle Database Doc ID: 756671.1 Type: ANNOUNCEMENT Modified Date : 15-APR-2009 Status: PUBLISHED
Beginning with release 10.2.0.3, Oracle releases Recommended Patches for
Oracle Database. For an introduction to Recommended Patches, see Note
Any positive experiences ?
Because I am working on a new project (some projects are still not canceled in these times) I am wondering about apply-all-recommended-patches approach.
It looks tempting to get rid of most of nasty bugs that manage to surface
Especially that we are beeing forced to use Oracle Streams which are somewhat outstanding with regard to Oracle recommended minimal patch list. Oracle Physical Standby (aka Data Guard) is on the list too.
Normally we go the way "wait until problem happens"(aka if it ain't broke don't fix it) and then try find workarround or patch but we have already encountered some bugs that could have been fixed by applying recommended patch bundles. Since it is a new project it looks to be an option.
What the others say about all those recommended patch bundles?
Thank you in advance,
Please consider the environment before printing this e-mailReceived on Tue Apr 21 2009 - 11:35:26 CDT