Re: OS upgrade for RAC

From: Mark J. Bobak <mark_at_bobak.net>
Date: Tue, 02 Jun 2015 15:56:13 +0000
Message-ID: <CAFQ5AC++aeLXGkjACAdo1X-C=nWf9jWv6S=Vgj7xPzJGf_+giA_at_mail.gmail.com>

1-2 days seems pretty arbitrary to me. What, exactly, will break on day 3, that didn't break on day 1 or day 2?

Obviously, probably shouldn't run that way indefinitely, but doing one node per weekend for 4 weekends seems reasonable to me.

-Mark

On Tue, Jun 2, 2015, 11:20 AM Anton <djeday84_at_gmail.com> wrote:

> it is linux, but because of bugs we had to work with
>
> [root_at_pk7db01 ~]# cat /etc/issue
> Red Hat Enterprise Linux Server release 5.11 (Tikanga)
> Kernel \r on an \m
>
> [oracle_at_pk7db02 /home/oracle]$cat /etc/issue
> Red Hat Enterprise Linux Server release 5.8 (Tikanga)
> Kernel \r on an \m
>
> seems to work fine, at least this week.
>
>
>
>
> On 06/02/2015 05:05 PM, Hameed, Amir wrote:
>
> We are running a four-node RAC (both Grid and RDBMS are 11.2.0.4) on
> Solaris 10 update 10. We need to upgrade our database and grid to 12c and
> that requires the OS to be at a minimum of Solaris 10 Update 11. What I
> would like to find out is that if we do a rolling OS upgrade where we
> upgrade one RAC node at a time from *Solaris10/Update10* to
> *Solaris10/Update11*, for how long can these RAC nodes stay out of synch
> in terms of the OS revision level? Is it possible to upgrade OS on one node
> every week and spread the entire process over four weeks? Oracle’s response
> was that the maximum these hosts can stay out of synch is 1-2 days but I
> would like to validate it from the list.
>
>
>

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

Received on Tue Jun 02 2015 - 17:56:13 CEST