Re: Policy on Oracle Versions and Patches

On 10 okt, 09:29, ca111..._at_gmail.com wrote:
> What would be your policy on Oracle versions and patches in an
> environment
> with 500 - 1000 databases and 20 - 50 databases per DBA?
>
> Let me clarify the question. Oracle states that Patch Sets include
> only
> bug fixes and no new functionality. However reality is a bit
> different.
> For example:
> 9.2.0.1 contains new functionality, fixes for 9.0.1 bugs, and new bugs
> 9.2.0.2 contain some new functionality that didn't make it into
> 9.2.0.1 (for example related to Streams),
> new "behaviour", more bug fixes, and a few new bugs
> ...
> 9.2.0.8 (terminal patch set) mostly has bug fixes, although some bugs
> are fixed only in 10g
>
> So the questions are:
> 1. What version/patch level should be used for implementing brand-new
> application assuming that:
> - Is it critical
> - Application vendor didn't provide any recommendation regarding
> version
> - Schema is simple, it does not use any advanced features
> - Main priority is stability and absence of unplanned outages
>
> It seems to me that the safest option would be to use version that has
> a terminal
> patch set which is 9.2.0.8. Yes I know that it is "unsupported" but
> does it really matter?
> When you have "supported" hardware HP/Sun/IBM/EMC will replace broken
> part typically withing 24h. For "supported" version Oracle may produce
> patch in a month or two.
>
> 2. Let's say you implemented new application using 10.2.0.3 as per
> vendor recommendations.
> During implementation the application functionality has been
> extensively tested.
> Would you automatically apply 10.2.0.4 even if nothing seems broken?
> Extensive
> application testing isn't possible.
>
> 3. Let's say you are running 10.2.0.3 and your database is hitting
> specific bug causing instance crash. Oracle Support tells you that
> there is one-off patch for this bug
> and it is included in 10.2.0.4 Patch Set. You are not able to conduct
> extensive application testing.
> Your ORACLE_HOME does not have any other one-off patches.
> Would you apply one-off patch or Patch Set?

First of all, with that number of databases one runs Grid Control and automates patch download and patch installation using this product. Too many Oracle users, who can't be bothered to investigate new features, stick to paleolithic procedures and don't implement timesavers provided by Oracle.

1 At least 10gR2, patch 3, so 10.2.0.4

2 I would implement 10.2.0.4 as Oracle would instruct me to do so with my next SR anyway.
The mantra is you should always be on the latest patchset. If you don't trust Oracle Q&A procedures and don't have time to read the patch release notes to see whether there is danger (ie you are using a patched feature), by all means never upgrade and loose support.

3 This is basically the same question. You don't seem to have time to do anything.
You should consider whether you want 2 outages to implement the one- off and the patch set for a subsequent problem without an one-off, or 1 outage to implement the patchset.
But then, as you don't have time to read release notes, you probably also don't have time to answer this question.

--
Sybrand Bakker
Senior Oracle DBA