Re: To patch or not to patch?

For any action (so also for patching) please find out the need/reason first. Is anything broken? (fix it)
Is there a corporate ruleset (like "apply all security patches within x days")? Either follow it or question it n a formal base - there should be change/review prozesses for such policies. There might be other reasons, just make sure they are defined before executed.

For Patching you can either create a new ORACLE_HOME for every new patset(s) you want to run (and change , or patch existing OHs. Both methods have (dis)advantages.

If you have several environments make soure you have any kind of revision vontrol sytem for your patch-bundles and document which Instances are running with them - otherwise it can lead to a big mess.

Just my ideas,
 Martin

On Fri, Aug 31, 2012 at 7:36 PM, Michael Dinh <mdinh235_at_gmail.com> wrote:
> Hello everyone,
> Will anyone please share your ideas on patching process? I have worked for
> company who seldom patch and then for company who patch everything.
>
> I am trying to find a happy medium and determine how people in the real
> word like you do this.
>
> Thanks so much.
>
> -Michaei.
>
>
> --
> http://www.freelists.org/webpage/oracle-l

--
http://www.freelists.org/webpage/oracle-l