A new patchset for Oracle 11.2 has been released. This patchset is a full installation of the Oracle Database software. So you don’t need to install 11.2.0.1 before installing 11.2.0.3. You can read the complete list of new features of 11.2.0.3 from here:
http://download.oracle.com/docs/cd/E11882_01/server.112/e22487/chapter1_11203.htm
I downloaded the patchset and wanted to upgrade my 2-node RAC database. It’s just a test database running on VirtualBox. Latest PSU and GI PSU (12419331 and 12419353) are already applied. Before I upgrade the database, I have also applied patch 12539000. Installer checks if this patch is applied. It seems it’s an important patch because it fixes a bug directly related with upgrade process (Bug 12539000 – 11203:ASM UPGRADE FAILED ON FIRST NODE WITH ORA-03113).
The patchset contains 7 zip files but we need only the first 3 zip files to upgrade our grid and database.
|
1 2 3 4 5 |
ls -lh *.zip -rw-r--r-- 1 oracle oinstall 1.3G Sep 24 15:31 p10404530_112030_LINUX_1of7.zip -rw-r--r-- 1 oracle oinstall 1.1G Sep 24 17:19 p10404530_112030_LINUX_2of7.zip -rw-r--r-- 1 oracle oinstall 917M Sep 24 15:45 p10404530_112030_LINUX_3of7.zip |
First I’ll upgrade the grid infrastructure, then I’ll update the DB. Before you upgrade your database, I recommend you to read “Master Note For Oracle Database Upgrades and Migrations” MOS ID 1152016.1.
As you know, starting from oracle 11gR2, the Oracle DB and grid upgrades are done via the “out of place upgrade”. So I switch to root user, create a new directory for the Oracle software:
|
1 2 3 4 |
su - mkdir /u02 chown oracle:oinstall /u02 exit |
Then I switch back to oracle and unzip the file (it creates folder named “grid”). Then I start the installer by oracle user:
|
1 2 3 |
unzip p10404530_112030_LINUX_3of7.zip cd grid ./runInstaller |
I’ll use graphical interface during the upgrade process.
My RAC has no internet connection so I select “skip software updates” and click next.
I’ll upgrade my grid and ASM.
Select the language you product will run and click next.
You can test SSH connectivity but because it’s an already working grid, just click next.
The installer will probably select the correct groups, check them, select according to your system and click next.
Enter the software location, click next. If you satisfied all prerequisites, the installer should advance to the summary screen.
Click “install” button to continue.
Wait until the installer ask you to run the root scripts…
You have to run the root script on first node and wait until it completed successfully before running it on other nodes. After you run the root scripts on all nodes, click OK to continue.
Wait until installer updated the Oracle inventory and check the report of the cluster verify utility. Let’s check the version of Grid:
|
1 2 3 4 5 6 7 |
/u01/11.2.0/grid/bin/crsctl query crs activeversion Oracle Clusterware active version on the cluster is [11.2.0.3.0] /u02/11.2.0/grid/bin/crsctl query crs activeversion Oracle Clusterware active version on the cluster is [11.2.0.3.0] |
Now we’re ready for upgrading the database. I’ll install the new database in “/u02″ but Grid controller changed the ownership of this folder, so I’ll create a folder in /u02 by root user and then give its ownership to oracle. I highly recommend you not to do it! Use separate folders for grid and database installations!
|
1 2 3 |
su - mkdir /u02/oracle chown oracle:oinstall /u02/oracle |
Let’s unzip the files and run the installer:
|
1 2 3 4 |
unzip p10404530_112030_LINUX_1of7.zip unzip p10404530_112030_LINUX_2of7.zip cd database ./runInstaller |
The security comes first, but as I said there’s no internet connection, so I just leave them blank and click next.
I will skip the software updates.
Select upgrade an existing DB, and click next.
Select the RAC DB, make sure all nodes selected and click next.
Select the product language and click next
Select the correct edition for your DB, then click next.
Enter the installation folder, click next.
Select the OS groups, and click next.
Click “install” button to continue.
Execute the root scripts on each node.
Now the installer will run DBUA (database upgrade assistant) to upgrade our database.
Select the database which will be upgraded.
Read the warning, gather data dictionary statistics if you haven’t done yet then click next.
I recommend you to mark the “turn off archiving” option and set the parallel degree according to the total number of processors in the cluster. I wanted to go with archiving to see how much redo will be generated. Upgrade process generated about 1.7G archivelogs for my RAC database. It’s an Enterprise version with default options.
Set the size of flash recovery area and click next.
This is the last step. DBUA will now restart the database and start upgrading. The DB will not be available for general use. Check the summary page and click “finish” when you are ready.
Wait until upgrade process completed.
Upgrading DB is completed, check the report. Now your DB is ready for general use. Do not forget to update your bash profile to use new Oracle Home.
It was a very smooth process. DBUA did its job well as expected.
13 Responses to “Upgrading Oracle RAC Database 11.2.0.2 to 11.2.0.3 (Grid + DB)”
Something I’m not clear on. Is this example a rolling upgrade? We have a similar 2 node setup but need to ensure minimal downtime. Does this example just apply to one node?
Paul, no it’s not a rolling upgrade. You may want to check how to use a Data Guard Physical Standby Database for Database Rolling Upgrades.
http://www.oracle.com/technetwork/database/features/availability/maa-wp-11g-upgrades-made-easy-131972.pdf
Any idea how much time it will take to upgrade Cluster & ASM of 10 database on 2 Node RAC. Please advice.
Forget to add from 11.2.0.2 to 11.2.0.3.
thank you!
It depends very much on the performance of the storage system, an educated guess would be about 1 hour.
Thank you so much for your inputs.
The post is very informative. I have the following queries. Please clarify -
1. Do we have to run any SQL scripts after opening the database for the first time post upgrade?
2. Do we have to shutdown the database during the entire activity. If not, please specify till which step we can leave it running.
3. Is it necessary to backup ORACLE_HOME directory if you’re installing on a separate directory, just in case.
4. I need to upgrade a single instance running on 11.2.0.2 to 11.2.0.3 with ASM. Do I still need to apply the Patch 12539000?
Thanks in advance!
1) No we don’t.
2) DBUA (database upgrade assistant) will shutdown and open the database, you don’t need to shutdown database.
3) It’s an out of place upgrade, so you don’t need to backup ORACLE_HOME directory but be sure that you backup your database!
4) Patching is good!
I’m trying to do the same with a 11.2.0.2 rac on Windows 2008 to 11.2.0.3, any considerations? couldn’t find anything on metalink.
I don’t install/run Oracle on Windows but the process should be very similar.
Did you have to unset environment variables (ORACLE_HOME, ORACLE_SID, LD_LIBRARY_PATH, ORA_CRS_HOME, etc) for grid user before running grid installer? I have read this as a prerequisite in other how to upgrade articles.
Also, is this actually a rolling upgrade? From oracle docs,
“In contrast with releases prior to Oracle Clusterware 11g release 2, all upgrades are rolling upgrades, even if you select all nodes for the upgrade.”
http://docs.oracle.com/cd/E11882_01/install.112/e24616/procstop.htm#CEGFBJHE
Thank you!
Sal, I use oraenv to set environment variables. I do not use profile scripts to set them automatically. So when I open a terminal, these environment variables are not set.
In this post, I described how to upgrade both clusterware and database. Clusterware upgrade is a rolling upgrade, but the database upgrade is not.
It’s a really nice article.
Have you done upgrade with 2 different RAC databases on the same cluster using DBUA? Or any thoughts?
Another question: do we have the option to set new Oracle_Base and Oracle_Home for 11gR2 when doing upgrade from 11gR1?
Thanks in advance.