Re: Backout options after applying patches on 4 node production RAC

From: Bradd Piontek <piontekdd_at_gmail.com>
Date: Wed, 20 Feb 2008 16:36:43 -0600
Message-ID: <e9569ef30802201436q5a079abet9bdbad1a0a4eabe2@mail.gmail.com>


Another option would be to clone the home, patch it before and, and then just switch the database to use the new home.

I'm a little suprised to hear a patch take 10 hours to patch. Does this patch do something in the database with streams? I can generally apply an entire patchset in under an hour.

On Wed, Feb 20, 2008 at 12:36 PM, Anurag Verma <anuragdba_at_gmail.com> wrote:

>
> Hi All,
>
>
> One questions on patching on RAC database.
> We will be patching our 4 node production RAC this weekend.
>
> The database is in 10.2.0.3.0 and the patches are a couple of one-off
> streams patches and not any major patches. Only difficulty we found is that
> long time, it takes for applying each patches. (Total time around 10
> hours).
>
> I was thinking about various backout options.
>
> One is rolling back the applied patches, if something goes wrong.
>
> Also, another plan is to take a backup of ORacle home from the production
> RAC nodes.
>
> And if we need to backout, just untar the Oracle home backup tar file to
> the oracle home directory.
>
> Please let me know if you have any suggestions.
>
>
> Thanks,
>
> --
>
> Anurag Verma,
> Database Administrator
> ERCOT(Electric Reliability Council of Texas),
> Texas 76574

--
http://www.freelists.org/webpage/oracle-l
Received on Wed Feb 20 2008 - 16:36:43 CST

Original text of this message