Re: 10204 RAC upgrade

Harel

I agree with you that rolling upgrade is done with Cluster up on all Nodes. The point I made is that you have to run root102.sh by taking CRS down. THis is last comment of successfull upgrade to stop Crs and then execute root102.sh. Here is the output. 

My point was to verify if two or more nodes can execute root102.sh simultaneously or we have to wait for one node to finish and then go to next node. The last part is doing some OCR Key creation which I want to see as if this conflict if two or more node are executing it. I really appreciate if you can comment as how these OCR key portion affect the OCR. Is it updating OCR that CRS is upgraded. Is any upgrade information is stored in the OCR also.

oracle_at_host1:> sudo /oracle/product/CRS/bin/crsctl stop crs
Stopping resources. This could take several minutes.
Error while stopping resources. Possible cause: CRSD is down.
 
oracle_at_host1:> sudo /oracle/product/CRS/install/root102.sh
Creating pre-patch directory for saving pre-patch clusterware files
Completed patching clusterware files to /oracle/product/CRS
Relinking some shared libraries.
Relinking of patched files is complete.
WARNING: directory '/oracle/product' is not owned by root
WARNING: directory '/oracle' is not owned by root
Preparing to recopy patched init and RC scripts.
Recopying init and RC scripts.
Startup will be queued to init within 30 seconds.
Starting up the CRS daemons.
Adding daemons to inittab
Waiting for the patched CRS daemons to start.
  This may take a while on some systems.
.
10204 patch successfully applied.
clscfg: EXISTING configuration version 3 detected.
clscfg: version 3 is 10G Release 2.
Successfully accumulated necessary OCR keys.
Using ports: CSS=49895 CRS=49896 EVMC=49898 and EVMR=49897.
node <nodenumber>: <nodename> <private interconnect name> <hostname>
node 1: host1 host1-rac host1
Creating OCR keys for user 'root', privgrp 'system'..
Operation successful.
clscfg -upgrade completed successfully

Tx
Sanjay



________________________________
From: Harel Safra <harel.safra_at_gmail.com>
To: Sanjay Mishra <smishra_97_at_yahoo.com>
Cc: "oracle-l_at_freelists.org" <oracle-l_at_freelists.org>
Sent: Mon, February 15, 2010 5:02:35 PM
Subject: Re: 10204 RAC upgrade


After installing several dozen clusters on redhat 4 and 5 I can tell you that at least with Linux this isn't the case. 
You run the installer (and the copy) with the cluster up on all the nodes and then run root102.sh one by one. 
Harel

ב-15/02/2010, בשעה 19:36, Sanjay Mishra <smishra_97_at_yahoo.com> כתב/ה:


Harel
>
>root102.sh is executed after bringing the CRS down and then root102.sh will bring the CRS up. Also  selecting more Node for Install require to bring the CRS down on all nodes and hence the Remote copy might surely have constraint to stop CRS otherwise any Library open might conflict especially on AIX where you need to run sliblclean at each steps to avoid the conflict
>
>Sanjay
>
>
>
________________________________
From: Harel Safra <harel.safra_at_gmail.com>
>To: smishra_97_at_yahoo.com
>Cc: oracle-l_at_freelists.org
>Sent: Mon, February 15, 2010 12:40:13 AM
>Subject: Re: 10204 RAC upgrade
>
>About 2, Since the installation and copy of the CRS is done with the CRS up an all the nodes, I believe you can do that before the down time window and then run root102.sh in the window.
>
>Harel Safra
>
>On 14/02/2010 23:07, Sanjay Mishra wrote: 
>Hi
>>
>>I had to upgrade one of the 8 Node RAC environment and it is running 5 Database with ASM and RDBMS with it own Home in 10.2.0.3 on AIX. We have only 2-3 hrs window and so want to have expert opinion on the following
>>	1. If I will upgrade CRS and it suggest at the end of successfull install to run root102.sh on all NODES Can I run on all node in parallel. It takes 10-15 minutes and so want to save some time. Not clear if it affect each other as anyway CRS is down at that time on that node
>>	2. Can I run the CRS upgrade indiviual on all node at the same time from few new putty session instead of initiating from one window and selecting all nodes. The reason is that it will take 15 Minutes to upgrade on Node 1 and then 15 minutes to copy to other nodes. If there are 7 more nodes, then it will take 15*7=100+ min. to copy to other nodes. So I f will run seperately from each nodes, it will be total of 15-20 minutes for Software and then 15 minutes for root102.sh.
>>	3. If CRS is upgraded and is down, Can I start the ASM and RDBMS upgrade at the same time or it will conflict due to /tmp/installer Lock files or any other issue can come. 
>>
>>TIA
>>Sanjay
>>
>


      

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