D How to Perform Oracle Clusterware Rolling Upgrades

This appendix describes how to perform Oracle Clusterware rolling upgrades. A rolling upgrade process allows one or more nodes in the cluster to have a different software version than the other nodes in the cluster for a short period of time. During the time period where cluster nodes have different software versions, the cluster is fully functional, but some administrative functions are disabled until the upgrade has completed, for example, adding new cluster resources. Once the rolling upgrade process starts, the time it takes to complete the upgrade of all the nodes in the cluster should not exceed 24 hours.

Because you must stop database processes before initiating an Oracle Clusterware process, this chapter also includes information about how to stop processes in Oracle Real Application Clusters (Oracle RAC) databases.

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 that version. For example, you can use these procedures to prepare to upgrade from Oracle Clusterware 10.2.0.1 to 10.2.0.3.

This appendix contains the following topics:

D.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.

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

To upgrade existing Oracle Clusterware 10g release 2 or Oracle Cluster Ready Services 10g release 1 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.

D.2.1 Overview of 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 Oracle Clusterware release 11g:

  1. Upgrade the Oracle Clusterware home (or CRS home) to the latest patch set for Oracle Clusterware release 10.2 (for example, 10.2.0.3 or higher). Upgrading the database Oracle home is not required.

    If you attempt a rolling upgrade to Oracle Clusterware 11g release 1 (11.1) and your current Oracle Clusterware installation has not been upgraded to at least Oracle Clusterware 10g release 10.2.0.3, then a prerequisite check failure is reported by the installer.

    If you are not using the rolling upgrade method to upgrade Oracle Clusterware to release 11.1, then you can use any Oracle Clusterware 10g release 10.2 version.

  2. Review the release notes for Oracle Clusterware 11g and support notes for any additional requirements or patches.

  3. Upgrade Oracle Clusterware from release 10.2 to release 11.1.

D.2.2 Overview of 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:

  1. Upgrade the Oracle Cluster Ready Services 10g release 1 home (or CRS home) to release 10.1.0.3 or higher. Upgrading the database Oracle home is not required.

  2. Review the release notes for Oracle Clusterware 11g and support notes for any additional requirements or patches.

  3. Upgrade Oracle Cluster Ready Services 10g release 1 to Oracle Clusterware 11g release 1 (11.1).

D.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.

See Also:

Oracle Database Upgrade Guide

D.4 How to Perform Oracle Clusterware Rolling Upgrades for Patches

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

Note:

To perform rolling upgrades, the existing Oracle Clusterware home directory, sometimes referred to as the 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.

D.4.1 Copy Patch Software to the Primary Upgrade Node

Download the patch software to the primary node in the cluster (the node where you performed the 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:

  1. Log in to My Oracle Support (https://support.oracle.com)

  2. Click the Patches & Updates tab.

  3. Search for the patch that you want to install.

  4. 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.

  5. 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

  6. Extract the patch set installation archive

D.4.2 Stop All Oracle Processes on Upgrade Nodes

During the rolling upgrade process, the CRS stack is shut down on each node. On each node on which you want to perform a rolling upgrade, before you upgrade Oracle Clusterware, you must shut down all other processes that use Oracle Clusterware, such as the Oracle RAC database instances and the Oracle ASM instances.

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. To specify a group of nodes, use a node list with the -n parameter instead of a single node name.

Complete the following steps:

Note:

You must perform these steps in the order listed.
  1. On each node you intend to upgrade, stop all listener and other processes, such as Oracle Enterprise Manager Database Control, that are managed by Oracle Clusterware or Oracle Cluster Ready Services or that access the Oracle Databases managed by Oracle Clusterware. These are the same processes that you must stop before adding additional products to Oracle Database 11g release 1 (11.1). However, when upgrading Oracle Clusterware or Oracle Cluster Ready Services, you must stop these processes regardless of whether you plan to modify the software in the associated Oracle Database home directories.

    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.
  2. 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:

    C:>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.

    To shut down all Oracle RAC instances for a database, enter the following command, where db_name is the name of the database:

    C:>oracle_home\BIN\srvctl stop database -d db_name
    
  3. Shut down all Oracle 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:

    C:>oracle_home\BIN\srvctl stop asm -n node
    
  4. Stop all Oracle Clusterware or Oracle Cluster Ready Services 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:

    C:>oracle_home\BIN\srvctl stop nodeapps -n node
    
  5. Log in as the Windows Administrator user and shut down the Oracle Clusterware process on each node on which you intend to perform the rolling upgrade by entering the following command:

    C:>CRS_home\BIN\crsctl stop crs
    
  6. Stop the Oracle ASM, Oracle Database, and CRS services from the Service Control Manager window.

D.4.3 Start OUI and Complete the Upgrade Processes on Upgrade Nodes

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

Complete the following steps:

  1. Start the patch set OUI. At the Product Selection Page, click Next.

  2. On the Specify Home Details window, select the Oracle Clusterware home directory, and click Next.

  3. On the Specify Hardware Cluster Installation Nodes window, select the nodes where you want to perform the upgrade, and click Next.

  4. Follow further instructions as directed from the OUI windows.

Repeat these steps for each node or group of nodes on which you are performing a rolling upgrade.

D.5 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.
  1. Load the Oracle Clusterware 11g release 1 (11.1) installation media into a CD or DVD ROM drive, or stage locally on disk.

  2. 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).

  3. 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".

  4. After you have completed any necessary patch upgrades, shut down processes on the nodes you intend to upgrade, as described in the preceding section, "Stop All Oracle Processes on Upgrade Nodes".

  5. Ensure that you are logged in as the Windows Administrator user before running OUI. After you start OUI, provide information as prompted.

    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.

  6. On a node that has not already been upgraded, repeat Steps 4 and 5 for the second and subsequent installs of a rolling upgrade.

  7. Ensure that the Oracle Process Monitor service (OPMD) starts when upgrading from Oracle Database 10.x to Oracle Database 11.1. To ensure this, after the installation is complete, run the following command from the CRSHOME/bin subdirectory:

    opmd -install
    

    Note:

    it is possible that the OPMD has already been installed on the node. If that is the case you may see the error OpmdInstall: OPM service is already installed, please uninstall first. You can ignore this error, it indicates that no further work needs to be performed.
  8. After completing the Oracle Clusterware upgrade, if you intend to upgrade Oracle Automatic Storage Management, or the Oracle Database software, complete preinstallation procedures for installing Oracle Database or Oracle RAC, as described in the Oracle Database Installation Guide for Microsoft Windows or Oracle Real Application Clusters Installation Guide for Microsoft Windows.

    See Also:

    Oracle Database Upgrade Guide for additional information about completing database upgrades