Upgrading Cluster Ready Services to Release 2 Oracle Database Tips by Donald Burleson

Figure 11.1 demonstrates the OFAdirectory structure with three releases installed. Note that the CRS still has a directory of ?10.1.0? in its path. This is because only one $ORA_CRS_HOME can exist on a node. Thus, to install the software in an upgrade scenario like this one, it has to be installed into the current $ORA_CRS_HOME directory. There is a way to get around this and that is to use dbca to uninstall the software in $ORA_CRS_HOME, then to install the release 2 version into a more properly named directory. The following pages will demonstrate an upgrade install with no concern regarding the directory name.

The following table steps through the install of Oracle 10g Release 2 CRS:

1.      Ensure all databases and the ASM are shutdown and disabled or they will automatically restart when the 10g Clusterware install is finished.

2.      Use srvctl to stop the nodeapps on both nodes. If this command hangs, type ctl+c and run it a second time. Use the command srvctl status nodeapps ‑n <nodename> to ensure the listeners are not running.

Next, launch the netca program and delete the listeners.

3.      Backup these useful scripts because they will be overwritten by the release 2 install. Complete this step as oracle on each node.

4.      Insert the CD for 10g Release 2 Clusterware. There is a preupdate script that must be run as root. I have found that this script hangs. To prevent it from hanging, run the /etc/init.d/init.cssd stop script as shown. Eject the CD and complete this step on the next node.

The preupdate.sh script must complete without intervention on each node before the install.

Exit the root login.

5.      Insert the install CD on oracle1 again, and launch the installer with the ‑ignoreSysPrereqs switch.

6.      The software will find the current directory for $ORA_CRS_HOME and will use it. You cannot modify the directory in an upgrade install like this one.

7.      If you create this directory structure, remember to make root own the directories leading up to the final crs directory, with only root having write permission on those directories.

8.      Ensure oracle2 is checked and click next.

9.      The prerequisite page is self-explanatory. The first three checks will likely fail; just add a check to each checkbox. The final checkbox ?Checking Cluster Synchronization Services? must succeed on its own. If it does not, quit the install and rerun the preupdate.sh script on each node.

10.  With the release 2 installer, configuration script(s) appear in a table as seen above. Run the rootupgrade script as shown, first on oracle1, then on oracle2. Be patient. These scripts can take a few minutes to finish.

After the scripts have run and you have clicked through to the next step, the installer will check that everything worked, then exit.

Run crs_status command to verify the services gsd,  ons, and vip are online on each node. No other service should be online.
 

If you want to learn RAC at home, get the bestselling book "Personal Oracle Real Application Clusters" by Edward Stoever. You can buy it direct from the publisher for 30%-off and get instant access to the code depot of Oracle tuning scripts.