B How to Perform Oracle Clusterware Rolling Upgrades

This appendix describes how to perform Oracle Clusterware rolling upgrades. Because you must stop database processes before initiating an Oracle Clusterware process, it includes information about how to stop processes in Oracle Real Application Clusters (Oracle RAC) databases.

This appendix contains the following topics:

Note:

You can use the procedures in this chapter to prepare to perform rolling upgrades of Oracle Clusterware from any Oracle Clusterware 10g release 10.2 or Oracle Clusterware 11g installation to the latest patch update. For example, you can use these procedures to prepare to upgrade from Oracle Clusterware 10.2.0.1 to 10.2.0.3.

Back Up the Oracle Software Before Upgrades
Restrictions for Clusterware Upgrades to Oracle Clusterware 11g
Verify System Readiness for Patches and Upgrades
How to Stop Processes in an Existing Oracle Database
How to Perform Oracle Clusterware Rolling Upgrades for Patches
How to Perform Rolling Upgrades From an Earlier Release to 11g

B.1 Back Up the Oracle Software Before Upgrades

Before you make any changes to the Oracle software, whether you intend to upgrade or patch part of the database or clusterware, or all of your cluster installation, Oracle recommends that you create a backup of the Oracle software.

B.2 Restrictions for Clusterware Upgrades to Oracle Clusterware 11g

To upgrade existing Oracle Clusterware or Oracle Cluster Ready Services installations to Oracle Clusterware 11g, you must first upgrade the existing installations to the most recent patch update. The following sections provide information about Oracle Clusterware upgrades.

B.2.1 Upgrading from Oracle Clusterware 10g Release 2 to Oracle Clusterware 11g

Complete the following procedure to prepare an existing Oracle Clusterware release 10.2 for rolling upgrade to release 11g:

Upgrade the Oracle Clusterware home (or CRS home) to Oracle Clusterware release 10.2.0.3, or 10.2.0.2 with CRS Bundle Patch #2 (reference Bug 5256865). Upgrading the database Oracle home is not required.
Upgrade Oracle Clusterware from release 10.2.0.3 to release 11.1.

B.2.2 Upgrading from Oracle Cluster Ready Services 10g Release 1 to Oracle Clusterware 11g

Complete the following procedure to prepare an existing Oracle Cluster Ready Services release 10.1 for rolling upgrade to Oracle Clusterware release 11g:

Upgrade the Oracle Cluster Ready Services home (or CRS home) to release 10.1.0.3. Upgrading the database Oracle home is not required.
Upgrade Oracle Cluster Ready Services from release 10.1.0.3 to Oracle Clusterware release 11.1.

B.3 Verify System Readiness for Patches and Upgrades

If you are completing a patch update of your database or clusterware, then after you download the patch software, and before you start to patch or upgrade your database, review the Patch Set Release Notes that accompany the patch to determine if your system meets the system requirements for the operating system and the hardware platform.

Use the Cluster Verification Utility to assist you with system checks in preparation for starting a database patch or upgrade.

B.4 How to Stop Processes in an Existing Oracle Database

To stop process in an existing Oracle RAC database, where you want to shut down the entire database in preparation for an Oracle Clusterware upgrade, complete the following steps.

B.4.1 Shut Down Oracle RAC Databases

Shut down any existing Oracle Database instances on each node, with normal or immediate priority.If Automatic Storage Management (ASM) is running, then shut down all databases that use ASM, and then shut down the ASM instance on each node of the cluster.

Note:

To upgrade using Oracle Clusterware, you must shut down all Oracle Database instances on all cluster nodes before modifying the Oracle software. If you are performing a patch update, review the instructions in the Patch Set Notes for detailed instructions.

B.4.2 Stop All Oracle Processes

Stop all listener and other processes running in the Oracle home directories where you want to modify the database software.

Note:

If you shut down ASM instances, then you must first shut down all database instances that use ASM, even if these databases run from different Oracle homes.

B.4.2.1 Stop Oracle Clusterware Processes

If you are modifying an Oracle Clusterware installation, then shut down the following Oracle Database 10g services.

Note:

You must perform these steps in the order listed.

Shut down any processes in the Oracle home on each node that might be accessing a database; for example, shut down Oracle Enterprise Manager Database Control.

Note:
Before you shut down any processes that are monitored by Enterprise Manager Grid Control, set a blackout in Grid Control for the processes that you intend to shut down. This is necessary so that the availability records for these processes indicate that the shutdown was planned downtime, rather than an unplanned system outage.
Shut down all Oracle RAC instances on all nodes. To shut down all Oracle RAC instances for a database, enter the following command, where db_name is the name of the database:
```
$ oracle_home/bin/srvctl stop database -d db_name
```
Shut down all ASM instances on all nodes. To shut down an ASM instance, enter the following command, where node is the name of the node where the ASM instance is running:
```
$ oracle_home/bin/srvctl stop asm -n node
```
Stop all node applications on all nodes. To stop node applications running on a node, enter the following command, where node is the name of the node where the applications are running
```
$ oracle_home/bin/srvctl stop nodeapps -n node
```
Log in as the root user, and shut down the Oracle Clusterware process by entering the following command on all nodes:
```
# CRS_home/bin/crsctl stop crs
```

B.4.2.2 Stop Oracle Database 10g Processes Before Adding Products or Upgrading

This section provides an overview of what needs to be done before adding additional products to Oracle Database 11g release 1 (11.1). If you are performing a patch upgrade, then refer to the Database Patch Set Notes for the patch for additional instructions.

Note:

You must perform these steps in the order listed.

Shut down any processes in the Oracle home on each node that can access a database; for example, shut down Oracle Enterprise Manager Database Control.

Note:
Before you shut down any processes that are monitored by Enterprise Manager Grid Control, set a blackout in Grid Control for the processes that you intend to shut down. This is necessary so that the availability records for these processes indicate that the shutdown was planned downtime, rather than an unplanned system outage.
Shut down all Oracle RAC instances on all nodes. To shut down all Oracle RAC instances for a database, enter the following command, where db_name is the name of the database:
```
$ oracle_home/bin/srvctl stop database -d db_name
```
Shut down all ASM instances on all nodes. To shut down an ASM instance, enter the following command, where node is the name of the node where the ASM instance is running:
```
$ oracle_home/bin/srvctl stop asm -n node
```

B.5 How to Perform Oracle Clusterware Rolling Upgrades for Patches

To perform a rolling upgrade, complete all of the following steps in sequence.

Copy Patch Software to the Primary Upgrade Node
Shut Down Oracle RAC Instances on Upgrade Nodes
Stop All Oracle Processes on Upgrade Nodes
Start OUI and Complete Upgrade Processes on Upgrade Nodes

Note:

To perform rolling upgrades, the existing Oracle Clusterware home directory, sometimes referred to in Oracle documentation as CRS home, must be located on local directories on the node. You cannot perform rolling upgrades on a shared Oracle Clusterware home directory.

Also note that Oracle does not support attempting to add additional nodes to a cluster during a rolling upgrade.

B.5.1 Copy Patch Software to the Primary Upgrade Node

Download the patch software to the primary node on the cluster (the node where you performed initial Oracle Clusterware and Oracle Database installation). Review the patch set Readme to confirm that your system meets the system requirements for the patch set updates, and complete any special instructions for particular environments or configurations.

To download patches, or download the patch note Readme:

Log in to OracleMetaLink (https://metalink.oracle.com)
Click the Patches & Updates tab.
Search for the patch that you want to install.
Click the patch number to open the patch page

From this location, you can download the patch binary, download the patch Readme, and obtain other information regarding the patch update.
Download the patch set installation archive to a directory inside the Oracle base directory that meets the following requirements:
- It is not the existing Oracle home directory, or Oracle Clusterware home directory
- It is not under an existing Oracle home directory, or Oracle Clusterware home directory
Extract the patch set installation archive

B.5.2 Shut Down Oracle RAC Instances on Upgrade Nodes

On each node on which you want to perform a rolling upgrade, shut down the Oracle Database instance, with normal or immediate priority. If Automatic Storage Management (ASM) is running, then for each node that you intend to perform a rolling upgrade, shut down the database that uses ASM, and then shut down the ASM instance on the node.

Note:

To upgrade Oracle Clusterware, you must shut down all Oracle Database instances on all cluster nodes that you intend to upgrade before modifying the Oracle software. If you are performing a patch update, review the instructions in the Patch Set Notes for detailed instructions.

You can use this procedure to shut down one node, and perform upgrades one node at a time, or to shut down groups of nodes, and upgrade groups of nodes at the same time.

B.5.3 Stop All Oracle Processes on Upgrade Nodes

On each node on which you want to perform a rolling upgrade, before you upgrade Oracle Clusterware, you must shut down Oracle Database services that use clusterware processes.

Complete the following steps:

Note:

You must perform these steps in the order listed.

Shut down any processes on each node you intend to upgrade that might be accessing a database, such as Oracle Enterprise Manager Database Control.

Note:
Before you shut down any processes that are monitored by Enterprise Manager Grid Control, set a blackout in Grid Control for the processes that you intend to shut down. This is necessary so that the availability records for these processes indicate that the shutdown was planned downtime, rather than an unplanned system outage.
Shut down all Oracle RAC instances on each node you intend to upgrade. To shut down Oracle RAC instances on individual nodes in the database, enter the following command, where db_name is the name of the database, and instance_name is the name of the instance:
```
$ oracle_home/bin/srvctl stop instance -d db_name -i instance_name
```
Repeat this process on each node of the cluster on which you intend to perform the rolling upgrade.
Shut down ASM instances on each node on which you intend to perform the rolling upgrade.

Note:
If you shut down ASM instances, then you must first shut down all database instances on the nodes you intend to upgrade that use ASM, even if these databases run from different Oracle homes.

To shut down an ASM instance, enter the following command, where node is the name of the node where the ASM instance is running:
```
$ oracle_home/bin/srvctl stop asm -n node
```
Stop all node applications on each node on which you intend to perform the rolling upgrade. To stop node applications running on a node, enter the following command, where node is the name of the node where the applications are running
```
$ oracle_home/bin/srvctl stop nodeapps -n node
```
On each node where you intend to perform the rolling upgrade, Initiate the upgrade state by using the following command as the root user:
```
# preupdate.sh -crshome CRS_home -crsuser crs_user
```
In the preceding syntax example, the variable CRS_home is the location of the Oracle Clusterware home, and the variable crs_user is the Oracle Clusterware installation owner, typically crs in Oracle documentation. For example, if the Oracle Clusterware home is /u01/app/crs, and the Oracle Clusterware software owner is crs, then enter the following command:
```
# preupdate.sh -crshome /u01/app/crs -crsuser crs
```

B.5.4 Start OUI and Complete Upgrade Processes on Upgrade Nodes

To complete the patch upgrade, use the Oracle Universal Installer (OUI) downloaded with the patch update.

Complete the following steps:

Start the patch set OUI. At the Welcome window, click Next.
On the Specify Home Details window, select the Oracle Clusterware home directory, and click Next.
On the Specify Hardware Cluster Installation Nodes window, select the nodes where you want to perform the upgrade, and click Next.
Follow further instructions as directed from the OUI windows.
At the end of the install, OUI instructs you to run the script preupdate.sh.

Open a terminal window, log in as the root user, and run the script as directed.

Wait for the response that the shutdown request has completed successfully.
From the terminal window you opened in the previous step, enter a command similar to the following:
```
# CRS_home/install/rootupgrade.sh
```
When the install script completes, it displays text similar to the following, where patch_version displays the patch version you are installing:
```
patch_version patch successfully applied.
clscfg -upgrade completed successfully
```
This indicates that the upgrade process is complete. The upgraded Oracle Clusterware stack and AUTOSTART resources are started on the node.

Repeat steps 4 and 5 for each node on which you are performing a rolling upgrade.

B.6 How to Perform Rolling Upgrades From an Earlier Release to 11g

Use the following procedure to upgrade Oracle Clusterware from an earlier release to a later release:

Note:

You cannot change the owner of the Oracle Clusterware home during an upgrade. You must use the same Oracle software owner that owns the existing Oracle Clusterware home.

Mount the Oracle Clusterware 11g release 1 (11.1) installation media.
Complete operating system prerequisite checks on each of the nodes that you intend to upgrade, to ensure that they meet the system prerequisites for Oracle Clusterware 11g release 1 (11.1).
If necessary, perform patch upgrades of the previous release Oracle Clusterware or Oracle Cluster Ready Services software to the most recent patch version, as described in the preceding section, "How to Perform Oracle Clusterware Rolling Upgrades for Patches". When you have completed patch upgrades, shut down processes on the nodes you intend to upgrade, as described in the preceding section, "How to Stop Processes in an Existing Oracle Database".
From the Oracle Clusterware home, run the following script:
```
mountpoint/clusterware/upgrade/preupdate.sh
```
This script shuts down the Oracle Clusterware software stack, and unlocks the Oracle Clusterware home (CRS home) for upgrading.

Run this script on each node in the cluster that you want to upgrade.
Ensure that you are logged in as the user that you want to own the Oracle Clusterware installation, and run the Oracle Clusterware installation. For example, if the owner you want to use for Oracle Clusterware is crs, and the mountpoint for Oracle Clusterware 11g release 1 (11.1) is /shiphome/clusterware, then you could use the following command:
```
$ whoami
  crs
$ /shiphome/clusterware/runInstaller
```
Provide information as prompted by the Installer.
Note:
You can upgrade one node, a subset of nodes, or all nodes, depending on your upgrade plan. However, note the following information about starting upgrades with OUI:
- If this is the initial upgrade, then the node where OUI is running must be one of the set of nodes that is being upgraded.
- If this is the second or subsequent upgrade, then the node where OUI is running must be on a node that has not been upgraded.
When prompted, in a separate terminal session, log in as root, and run the rootupgrade script.

Note:
You must install Oracle Clusterware into the existing Oracle Clusterware home on the local and remote node subset. When you run the root script, it starts the Oracle Clusterware 11g release 1 (11.1) stack on the subset cluster nodes, but lists it as an inactive version.
Start the second and subsequent installs of a rolling upgrade from a node that hasn't already been upgraded.
After installing the Oracle Clusterware upgrade, if you intend to upgrade Automatic Storage Management, or the Oracle Database software, complete preinstallation procedures for installing Oracle Database or Oracle RAC, as described in Oracle Database Installation Guide for your platform, or in this guide (for Oracle RAC preinstallation checks).

See Also:
Oracle Database Upgrade Guide for additional information about completing database upgrades