Re: Rolling upgrades and client connection

From: hrishy <hrishys_at_yahoo.co.uk>
Date: Sun, 5 Jul 2009 05:29:57 +0000 (GMT)
Message-ID: <804374.84989.qm_at_web23708.mail.ird.yahoo.com>

Hi
 

Yes thanks that was my exact question.
 

regards
Hrishy

• On Fri, 3/7/09, Harel Safra <harel.safra_at_gmail.com> wrote:

From: Harel Safra <harel.safra_at_gmail.com> Subject: Re: Rolling upgrades and client connection To: hrishys_at_yahoo.co.uk
Cc: oracle-l_at_freelists.org
Date: Friday, 3 July, 2009, 9:04 AM

If I understand you question correctly, these are the steps to follow for a rolling patch install:

1. Stop the instance in node 1 and all other relevant processes (asm if running from the same home, listener, em...)
2. Install the patch with the OPatch option -local
3. Restart services from step 1
3. Repeat for other nodes.

All that is under the assumption that the patch can be installed in a rolling fashion.

Harel Safra 

hrishy wrote:

Hi
 

I have a question on rolling upgrades of 2 node RAC databases.
 

I understand while performing a rolling upgrade i need to stage the patch to a directory and just launch Opatch from that directory and Opatch would roll over the patch to the remote node and apply it there .
 

My question is what happens to the existing and new user connections as the database is not stopped what happens when the patch is being applied to node 1
 

a)Users are already connectted to node 1 b) new users connection who are attempting to connect to node 1
 
 

regards
Hrishy

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

Received on Sun Jul 05 2009 - 00:29:57 CDT