How to perform an In-place upgrade of an Oracle RAC Database from 11.2.0.2 to 11.2.0.3

How to perform an In-place upgrade of an Oracle RAC Database from 11.2.0.2 to 11.2.0.3


In-order to upgrade a RAC Database from 11.2.0.2 to 11.2.0.3 you need to upgrade
  1. The grid infrastructure first.
  2. Then, the Oracle Database.
Environment /Setup Details:-

+ 2 Node RAC on Red Hat Linux 5.6 with Dell PowerEdge Servers (R710).

+ Applies to any storage.

Latest OPatch

It is recommended to we use the Latest Version of OPatch. Unzip the zip file and copy OPatch folder to $ORACLE_HOME And $GI_HOME by renaming the earlier OPatch directory. You can refer to how to download and Install OPatch [Metalink ID 274526.1]

Pre- Requisite Patch

First, let’s discuss about the mandatory patches required before upgrading to 11.2.0.3. PSU 12419353& Patch 1253900 is mandatory and downloadable from http://www.metalink.oracle.com/ for information on PSU 12419353, refer to Metalink article ID 12419353.8

Download the patch and unzip it to a stage directory (it can be any directory), once you unzip the downloaded patch, 2 folders will be created. In this example I have unzipped the patch to /patches directory.

Now, let’s see how to patch the $GI_HOME with Patch 12419353.

Before the patch is installed, we need to perform a pre-req check. Let’s see how to do this.

1] [root@rac1 patches]# su – oracle

2] [oracle@rac1 ~]$ cd /opt/app/oracle/product/11.2.0/dbhome_1/OPatch/

3] [oracle@rac1 OPatch]$ ./opatch prereq CheckConflictAgainstOHWithDetail -phBaseDir /patches

Invoking OPatch 11.2.0.1.6

Oracle Interim Patch Installer version 11.2.0.1.6

Copyright (c) 2011, Oracle Corporation. All rights reserved.

PREREQ session

Oracle Home : /opt/app/oracle/product/11.2.0/dbhome_1

Central Inventory : /opt/app/oraInventory

from : /etc/oraInst.loc

OPatch version : 11.2.0.1.6

OUI version : 11.2.0.1.0

Log file location : /opt/app/oracle/product/11.2.0/dbhome_1/cfgtoollogs/opatch/opatch2011-08-16_19-36-09PM.log

Invoking prereq "checkconflictagainstohwithdetail"

Prereq "checkConflictAgainstOHWithDetail" passed.

OPatch succeeded.

Patching the $GI_HOME

1] Stop the Instance running on Node1

srvctl stop instance -d upgrade -i upgrade1

2] As root User run the opatch auto from the $GI_HOME

./opatch auto /patches

Note: The Opatch auto takes care of the patching of both the Grid infrastructure Home and the Oracle Home with the mandatory patch .

Once the patching is done on Node1, start the instance on Node1

3] Starting the Instance on Node1

srvctl start instance -d upgrade -i upgrade1

Note: Repeat the process of pre-req and patching on Node2

Once the mandatory patch is applied, we can proceed with the upgrade of the grid infrastructure home.

Patches required: The software/Patch can be downloaded from My Oracle support: patch 10404530. Select p10404530_112030_Linux-x86-64_3of7.zip for grid infrastructure download. Once downloaded, unzip them.

Upgrading Grid Infrastructure

Unzip the patches downloaded and invoke run Installer from the unzipped grid folder. You will be taken to the welcome screen.

Choose Skip Software updates

oracle grid
Figure 1: Skip software update

Choose Upgrade Gird Infrastructure or Oracle ASM

oracle grid
Figure 2
: Oracle ASM

Choose the Language
oracle grid
Figure 3: Oracle ASM

The Nodes present are selected by default, Click Next.
oracle grid
Figure 4: Click Next

Leave the OS groups to Defaults
oracle grid
Figure 5: OS group

Choose the New Location where the Grid Infrastructure should be installed
oracle grid
Figure 6: New Location

The Pre-Requisite checks are performed, click next
oracle grid
Figure 7: Pre-Requiste

The summary screen appears click next
oracle grid
Figure 8: Summary

Click on Install
oracle grid
Figure 9: Install

Run rootupgrade.sh on both the nodes as specified in the screenshot
oracle grid
Figure 10: Rootupgrade

You can verify if the Clusterware has been upgraded successfully, by the following commands.

To determine software version (binary version of the software on a particular cluster node) use

$crsctl query crs softwareversion

Oracle Clusterware version on node [prod01] is [11.2.0.3.0]

For checking active version on cluster, use

$ crsctl query crs activeversion

Oracle Clusterware active version on the cluster is [11.2.0.3.0]

Upgrading the Database via In-place upgrade

Patches Required:

The software/Patch can be downloaded from My Oracle support: patch 10404530. Select p10404530_112030_Linux-x86-64_1of7.zip and p10404530_112030_Linux-x86-64_2of7.zip for database patch/software download. Once downloaded, unzip them.

In-Place upgrades (Things to do before performing and In-place upgrade)

When performing an in-place upgrade, which uses the same Oracle home location, an error messages appears stating that the installer detects Oracle Database software in the location that you specified.

Message: The installer has detected that the software location you have specified contains Oracle Database software release 11.2.0.2. Oracle recommends that when upgrading to 11.2.0.3, you perform an out-of-place installation of the software into a new Oracle home and then upgrade the database using the new software binaries.

Cause: The installer has detected that the software location you have specified contains Oracle Database software release 11.2.0.2.

Action: Either perform an in-place upgrade (Steps provided in this section), or perform an out-of-place upgrade

Performing an In-Place Upgrade for an Oracle RAC Database

To perform an in-place upgrade for Oracle RAC Database instances:

1. Back up the configuration data by backing up the following directories on all cluster nodes:
  • ORACLE_HOME/dbs
  • ORACLE_HOME/network/admin
  • ORACLE_HOME/hostname_dbname
  • ORACLE_HOME/oc4j/j2ee/OC4J_DBConsole_hostname_dbname
2. Run the following command on each of the nodes to detach the 11.2.0.2.0 Oracle RAC ORACLE_HOME:

ORACLE_HOME/oui/bin/runInstaller -detachHome ORACLE_HOME=11.2.0.2.0 software location

3. Rename the 11.2.0.2.0 Oracle RAC ORACLE_HOME directory on all the nodes to a temporary name.

4. Install release 11.2.0.3 Software Only on all nodes.

From the unzipped folder, invoke the run Installer from the database folder.

The welcome screen appears, uncheck the security updates and click next

oracle grid
Figure 11: Security updates

Choose Skip Software Updates
oracle grid
Figure 12: Skip Sofware Updates

Select Install Database Software Only and click next
oracle grid
Figure 12: DB software Updates

Choose Oracle Real Application Clusters DB Installation and Select the Nodes and click next
oracle grid
Figure 13: Oracle Real Application cluster

Choose the Language and click next
oracle grid
Figure 14: Language

Select Enterprise Edition and click next
oracle grid
Figure 15: Enterprise Edition

Specify the location of the old home, and click next
oracle grid
Figure 16: Location old Home

Provide the Operating System groups and click next
oracle grid
Figure 17: OS

Once the Pre-requisite checks are performed, click next
oracle grid
Figure 18: Pre-Requisite

The summary screen appears, verify the settings and click next
oracle grid
Figure 19: Summary

The installation proceeds
oracle grid
Figure 20: Installation proceed

Once the installation is done, run Root.sh on both the nodes as instructed and click ok.
oracle grid
Figure 21: Root.sh

Now, on all nodes, restore into the 11.2.0.3 ORACLE_HOME software location the backed up configuration data files (from the backups you made of /dbs and network/admin), and also restore the following two directories: /hostname_dbname and /oc4j/j2ee/OC4J_DBConsole_hostname_dbname. Specify the actual name for hostname_dbname.

Database Upgrade using DBUA

Run DBUA from the 11.2.0.3 ORACLE_HOME/bin directory on the local node and select the 11.2.0.2.0 Oracle RAC database instance to upgrade it to release 11.2.0.3.0.

The welcome screen appears once you invoke the DBUA, click next to proceed

oracle grid
Figure 22: DBUA

DBUA Lists the databases that can be upgraded, select the one that you would like to upgrade
oracle grid
Figure 23: upgrade

You can choose the Degree of parallelism and upgrading the time zone version and click next
oracle grid
Figure 24: Degree of parallelism

Skip this screen by clicking next
oracle grid
Figure 25: Skip screen

The summary screen appears, click on finish for the upgrade to proceed, and the upgrade proceeds.

Once the upgrade is completed a summary of all the components that was upgraded will be displayed.
NOTE: The only time one should use this method (in-place upgrade) is when you lack space on your server. However, you can use this method for your test and development environments to save space. Since this method was the traditional method of doing things

Since this method is available, I thought it’s worth checking how it works in 11gR2. During the entire upgrade process, I never ran into any issues, apart from the slightly higher downtime in comparison to the out-of place upgrade. However, oracle doesn’t recommend this method. You can refer to the following metalink note 1291682.1.




Article ID: SLN310466

Last Date Modified: 08/14/2018 03:42 AM


Rate this article

Accurate
Useful
Easy to understand
Was this article helpful?
Yes No
Send us feedback
Comments cannot contain these special characters: <>()\
Sorry, our feedback system is currently down. Please try again later.

Thank you for your feedback.