Skip Headers
Oracle® Grid Infrastructure Installation Guide
12c Release 1 (12.1) for Microsoft Windows x64 (64-Bit)

E17618-07
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Index
Index
Go to Master Index
Master Index
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
PDF · Mobi · ePub

D How to Upgrade to Oracle Grid Infrastructure 12c Release 1

This appendix describes how to perform Oracle Clusterware and Oracle Automatic Storage Management (Oracle ASM) upgrades.

This appendix contains the following topics:

D.1 Back Up the Oracle Software Before Upgrades

Before you make any changes to the Oracle software, Oracle recommends that you create a backup of the Oracle software and databases. For Oracle software running on Windows operating systems, you must also take a backup of the Windows registry. Without a registry backup, you will not be able to restore the Oracle software to a working state if the upgrade of Oracle Grid Infrastructure or Oracle Database fails and you want to revert to the previous software installation.

D.2 About Oracle ASM and Oracle Grid Infrastructure Installation and Upgrade

You can upgrade Oracle Grid Infrastructure either by bringing the cluster down and upgrading the complete cluster, or upgrading individual nodes without stopping Oracle Grid Infrastructure on other nodes in the cluster, which is called performing a rolling upgrade. An upgrade is always a temporary option, because some services are disabled when one or more nodes are in the process of being upgraded. All upgrades are out-of-place upgrades, meaning that the software executable files are placed in a different Grid home from the Grid home used for the prior release.

You can downgrade from Oracle Grid Infrastructure 12c Release 1 (12.1) to prior releases of Oracle Grid Infrastructure. Be aware that if you downgrade to a prior release, then your cluster must conform with the configuration requirements for that prior release, and the features available for the cluster consist only of the features available for that prior release of Oracle Clusterware and Oracle ASM.

If you have an existing Oracle ASM instance, then you can either upgrade it at the time that you install Oracle Grid Infrastructure, or you can upgrade it after the installation, using Oracle ASM Configuration Assistant (ASMCA). Note that a number of Oracle ASM features are disabled until you upgrade Oracle ASM. Also, Oracle Clusterware management of Oracle ASM does not function correctly until Oracle ASM is upgraded, because Oracle Clusterware only manages Oracle ASM when it is running in the Oracle Grid Infrastructure home. For this reason, Oracle recommends that if you do not upgrade Oracle ASM at the same time as you upgrade Oracle Clusterware, then you should upgrade Oracle ASM immediately afterward.

You can perform out-of-place upgrades to an Oracle ASM instance using ASMCA. In addition to running ASMCA using the graphical user interface (GUI), you can run ASMCA in non-interactive (silent) mode.

Note:

If you are currently using OCFS for Windows as your shared storage, then you must migrate to using Oracle ASM during the upgrade of Oracle Database and Oracle Grid Infrastructure.

Note:

You must complete an upgrade before attempting to use cluster backup files. You cannot use backups for a cluster that has not completed upgrade.

See Also:

Oracle Database Upgrade Guide and Oracle Automatic Storage Management Administrator's Guide for additional information about upgrading existing Oracle ASM installations

D.3 Options for Clusterware and Oracle ASM Upgrades and Downgrades

Upgrade options from Oracle Grid Infrastructure 11g to Oracle Grid Infrastructure 12c include the following:

  • Oracle Grid Infrastructure rolling upgrades, with OCR and voting files on Oracle ASM

  • Oracle Grid Infrastructure complete cluster (downtime, non-rolling), with OCR and voting files on Oracle ASM

  • Oracle Grid Infrastructure rolling upgrades with OCR and voting files on storage other than Oracle ASM

  • Oracle Grid Infrastructure complete cluster (downtime, non-rolling), with OCR and voting files on storage other than Oracle ASM

Upgrade options from releases before Oracle Grid Infrastructure 11g Release 2 (11.2) to Oracle Grid Infrastructure 12c include the following:

  • Oracle Grid Infrastructure rolling upgrades, with OCR and voting files on storage other than Oracle ASM

  • Oracle Grid Infrastructure complete cluster (downtime, non-rolling), with OCR and voting files on storage other than Oracle ASM

Downgrade options from Oracle Grid Infrastructure 12c to earlier releases include the following:

  • Oracle Grid Infrastructure downgrade to Oracle Grid Infrastructure 11g Release 2 (11.2)

D.4 Restrictions for Oracle Clusterware and Oracle ASM Upgrades

Oracle recommends that you use CVU to check if there are any patches required for upgrading your existing Oracle Grid Infrastructure 11g Release 2 or Oracle RAC 11g Release 2 installations.

Be aware of the following restrictions and changes for upgrades to Oracle Grid Infrastructure installations, which consists of Oracle Clusterware and Oracle ASM:

  • If the OCR and Voting File locations for your current installation are on raw devices, then you must migrate them to Oracle ASM disk groups or shared file systems before upgrading to Oracle Grid Infrastructure 12c Release 1 (12.1).

  • To upgrade existing Oracle Clusterware installations to Oracle Grid Infrastructure 12c Release 1 (12.1), your current release must be Oracle Grid Infrastructure 11g Release 2.

  • On the Windows platform, to upgrade Oracle Clusterware from releases 10.2.0.5 and 11.1.0.7 to Oracle Grid Infrastructre release 12.1, you must perform an interim upgrade to Oracle Grid Infrastructre 11g Release 2 for Oracle Clusterware. After upgrading Oracle Clusterware to Oracle Grid Infrastructre 11g Release 2, you must move the Oracle Cluster Registry (OCR) and voting files to Oracle ASM. You can then upgrade Oracle Grid Infrastructre 11g Release 2 to Oracle Grid Infrastructure release 12.1.

  • If you are upgrading an Oracle Database release 10.2.0.5 or Oracle Database release 11.1.0.7 environment that stores Oracle Clusterware files on OCFS for Windows or RAW devices, then you cannot directly upgrade to Oracle Database 12c. See Oracle Database Upgrade Guide.

  • To upgrade existing Oracle ASM installations to Oracle Grid Infrastructure 12c Release 1 (12.1), in a Standard configuration, your release must be greater than or equal to 10.1.0.5, 10.2.0.3, 11.1.0.6, or 11.2.

  • To upgrade existing Oracle Grid Infrastructure installations to Oracle Grid Infrastructure, you must first verify if you need to apply any mandatory patches for upgrade to succeed. To upgrade Oracle Grid Infrastructure installations from 11.2.0.2 to a later release, you must install the latest bundle for the cumulative patches for Oracle Grid Infrastructure (Patch 11 bundle or higher). See Section D.7, "Using CVU to Validate Readiness for Oracle Clusterware Upgrades" for steps to check readiness.

    See Also:

    Oracle 12c Upgrade Companion (My Oracle Support Note 1462240.1):

    https://support.oracle.com/oip/faces/secure/km/DocumentDisplay.jspx?id=1462240.1

  • If you have Oracle ACFS file systems on Oracle Grid Infrastructure 11g Release 2 (11.2.0.1), you upgrade Oracle Grid Infrastructure to any later release, and you take advantage of Redundant Interconnect Usage and add one or more additional private interfaces to the private network, then you must restart the Oracle ASM instance on each upgraded cluster member node.

  • Do not delete directories in the Grid home. For example, do not delete Grid_home\Opatch. If you delete the directory, then the Oracle Installation User for Oracle Grid Infrastructure cannot use Opatch to patch the Grid home, and Opatch displays the error "checkdir error: cannot create Grid_home\OPatch"

  • Oracle Clusterware and Oracle ASM upgrades are always out-of-place upgrades. With Oracle Grid Infrastructure 12c Release 1 (12.1), you cannot perform an in-place upgrade of Oracle Clusterware and Oracle ASM to existing homes.

  • With Oracle Clusterware 11g Release 2 (11.2) and later, you can perform upgrades on a shared Oracle Clusterware home.

  • You must use an Administrator user to perform the Oracle Grid Infrastructure 12c Release 1 (12.1) upgrade.

  • Oracle ASM and Oracle Clusterware both run in the Oracle Grid Infrastructure home.

  • During a major release upgrade to Oracle Clusterware 12c Release 1 (12.1), the software in the Grid home for Oracle Grid Infrastructure 12c Release 1 (12.1) is not fully functional until the upgrade is completed. Running the Server Control Utility (SRVCTL), crsctl, and other commands from the 12c Release 1 (12.1) Grid home is not supported until the upgrade is complete across all nodes.

    To manage databases using earlier releases (release 10.x, 11.1, or 11.2) of Oracle Database software during the Oracle Grid Infrastructure upgrade, use SRVCTL in the existing database homes.

  • During Oracle Clusterware installation, if there is a single instance Oracle ASM release on the local node, then it is converted to a clustered Oracle ASM 12c Release 1 (12.1) installation, and Oracle ASM runs in the Oracle Grid Infrastructure home on all nodes.

  • If a single instance (non-clustered) Oracle ASM installation is on a remote node, which is a node other than the local node (the node on which the Oracle Grid Infrastructure installation is being performed), then it will remain a single instance Oracle ASM installation. However, during installation, if you select to place the Oracle Cluster Registry (OCR) and voting files on Oracle ASM, then a clustered Oracle ASM installation is created on all nodes in the cluster, and the single instance Oracle ASM installation on the remote node will become nonfunctional.

D.5 Understanding Out-of-Place and Rolling Upgrades

Rolling Upgrades

You can upgrade Oracle Grid Infrastructure either by bringing the cluster down and upgrading the complete cluster, or upgrading individual nodes without stopping Oracle Grid Infrastructure on other nodes in the cluster, which is called performing a rolling upgrade. If you upgrade a subset of nodes, then a software-only installation is performed on the existing cluster nodes that you do not select for upgrade. Rolling upgrades avoid downtime and ensure continuous availability while the software is upgraded to a new release.

Note:

In contrast with releases prior to Oracle Clusterware 11g Release 2, Oracle Universal Installer (OUI) always performs rolling upgrades, even if you select all nodes for the upgrade.

Out-of-Place Upgrades

During an out-of-place upgrade, the installer installs the newer release in a separate Oracle Clusterware home. Both releases of Oracle Clusterware are on each cluster member node, but only one release is active. By contrast, an in-place upgrade overwrites the software in the current Oracle Clusterware home.

To perform an out-of-place upgrade, you must create new Oracle Grid Infrastructure homes on each node. Then you can perform an out-of-place rolling upgrade, so that some nodes run Oracle Clusterware from the original Oracle Clusterware home, and other nodes run Oracle Clusterware from the new Oracle Grid Infrastructure home.

If you have an existing Oracle Clusterware installation, then you upgrade your existing cluster by performing an out-of-place upgrade. An in-place upgrade of Oracle Clusterware is not supported.

See Also:

"Performing Rolling Upgrades of Oracle Grid Infrastructure" for instructions on completing rolling upgrades

D.6 Preparing to Upgrade an Existing Oracle Clusterware Installation

If you have an existing Oracle Clusterware installation, then you upgrade your existing cluster by performing an out-of-place upgrade. You cannot perform an in-place upgrade.

The following sections describe the tasks you should complete before starting an upgrade:

D.6.1 Verify System Readiness for Patches and Upgrades

If you are completing a patch update of Oracle Clusterware or Oracle ASM, then after you download the patch software and before you start to patch or upgrade your software installation, 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.

Use the Cluster Verification Utility (CVU) to assist you with system checks in preparation for patching or upgrading. You can run CVU before starting the upgrade, however, the installer runs the appropriate CVU checks automatically, and prompts you to fix problems before proceeding with the upgrade.

D.6.2 Gather the Necessary System Information

Ensure that you have the information you will need when installing Oracle Grid Infrastructure into a new home directory, including the following:

  • The Oracle base location for Oracle Clusterware

  • An Oracle Grid Infrastructure home location that is different from your existing Oracle Clusterware home (or Grid home) location

  • SCAN name and addresses, and other network addresses, as described in Chapter 4

  • Privileged user operating system groups, as described in Section 5.1, "Creating Groups and Users for Oracle Grid Infrastructure and Oracle RAC"

  • Local Administrator user access, or access as the user who performed the previous Oracle Clusterware installation

D.6.3 Upgrade to the Minimum Required Oracle Clusterware Release

To upgrade existing Oracle Clusterware installations to a standard configuration Oracle Grid Infrastructure 12c cluster, your release must be greater than or equal to Oracle Clusterware 10g Release 1 (10.1.0.5), Oracle Clusterware 10g Release 2 (10.2.0.3), Oracle Grid Infrastructure 11g Release 1 (11.1.0.6), or Oracle Grid Infrastructure 11g Release 2 (11.2.0.2). If your current Oracle Clusterware installation is not currently running at least the minimum supported release, then a prerequisite check failure is reported.

You must upgrade your current Oracle Clusterware installation to at least the minimum supported release before upgrading. For example, if you plan to upgrade your Oracle Clusterware 11g Release 1 installation to Oracle Clusterware 12c Release 1 (12.1) and your current Oracle Clusterware installation is release 11.1.0.2, then you must upgrade your current Oracle Clusterware installation to release 11.1.0.6 or higher before starting the upgrade

D.6.4 Unset Environment Variables Used By Oracle Software

If you have had an existing installation on your system, and you are using the same user account to install Oracle Grid Infrastructure 12c Release 1 (12.1), then unset the following environment variables, and any other environment variable set for the Oracle installation user that is connected with Oracle software homes.

  • ORACLE_BASE

  • ORACLE_HOME

  • ORACLE_SID

  • ORA_NLS10

  • TNS_ADMIN

  • ORA_CRS_HOME

If you have set ORA_CRS_HOME as an environment variable, following instructions from Oracle Support, then unset it before starting an installation or upgrade. You should never use ORA_CRS_HOME as an environment variable except under explicit direction from Oracle Support.

To remove the environment variable settings for all sessions, from the Start menu, right click My Computer and select Properties. In the System Properties window, select Advanced, then click the Environment Variables button.

Also, check to ensure that the user profile for the Oracle Installation User does not set any of these environment variables.

D.7 Using CVU to Validate Readiness for Oracle Clusterware Upgrades

You can use Cluster Verification Utility (CVU) to assist you with system checks in preparation for starting an upgrade. CVU runs the appropriate system checks automatically, and prompts you to fix problems before proceeding with the upgrade.

This section contains the following topics:

D.7.1 About the CVU Grid Upgrade Validation Command Options

You can run upgrade validations in one of two ways:

  • Run OUI, and allow the CVU validation built into OUI to perform system checks

  • Run the CVU manual script cluvfy.bat script to perform system checks

To use OUI to perform pre-install checks, run the installation as you normally would. OUI starts CVU, and performs system checks as part of the installation process. Selecting OUI to perform these checks is particularly appropriate if you think you have completed preinstallation checks, and you want to confirm that your system configuration meets minimum requirements for installation.

To use the cluvfy.bat command-line script for CVU, navigate to the staging area for the upgrade, where the runcluvfy.bat command is located, and run the following command to check the readiness of your Oracle Clusterware installation for upgrades.

Navigate to the staging area for the upgrade, where the runcluvfy.bat command is located, and run the following command to check the readiness of your Oracle Clusterware installation for upgrades:

runcluvfy.bat stage -pre crsinst -upgrade

Running runcluvfy.bat with the -pre crsinst -upgrade options performs system checks to confirm if the cluster is in a correct state for upgrading from an existing clusterware installation.

The runcluvfy command uses the following syntax, where variable content is indicated by italics:

runcluvfy.bat stage -pre crsinst -upgrade [-rolling] -src_crshome 
src_Gridhome -dest_crshome dest_Gridhome -dest_version dest_version
[-verbose]

The options are:

  • -rolling

    Use this flag to verify readiness for rolling upgrades.

  • -src_crshome src_Gridhome

    Use this flag to indicate the location of the source Oracle Clusterware or Grid home that you are upgrading, where src_Gridhome is the path to the home to upgrade.

  • -dest_crshome dest_Gridhome

    Use this flag to indicate the location of the upgrade Grid home, where dest_ Gridhome is the path to the Grid home.

  • -dest_version dest_version

    Use the dest_version flag to indicate the release number of the upgrade, including any patchset. The release number must include the five digits designating the release to the level of the platform-specific patch. For example: 12.1.0.1.0.

  • -verbose

    Use the -verbose flag to produce detailed output of individual checks

D.7.2 Example of Verifying System Upgrade Readiness for Grid Infrastructure

You can verify that the permissions required for installing Oracle Clusterware have been configured by running the following command:

C:\> runcluvfy.bat stage -pre crsinst -upgrade -rolling 
-src_crshome C:\app\11.2.0.3\grid -dest_crshome C:\app\12.1.0\grid
-dest_version 12.1.0.0.0 -verbose

D.8 Understanding Rolling Upgrades Using Batches

Upgrades from earlier releases require that you upgrade the entire cluster You cannot select or de-select individual nodes for upgrade. Oracle does not support attempting to add additional nodes to a cluster during a rolling upgrade.

Oracle recommends that you leave Oracle RAC instances running when upgrading Oracle Clusterware. When you start the upgrade process on each node, the upgrade scripts shut down the database instances and then start the instances again. If you upgrade from Oracle Grid Infrastructure 11g Release 11.2.0.1 and later to any later release of Oracle Grid Infrastructure, then all nodes are selected for upgrade by default.

When performing the upgrade, you can divide the nodes into groups, or batches, and start upgrades of these node batches. Between batches, you can move services from nodes running the previous release to the upgraded nodes, so that services are not affected by the upgrade.

D.9 Performing Rolling Upgrades of Oracle Grid Infrastructure

This section contains the following topics:

D.9.1 Performing a Standard Upgrade from an Earlier Release

Use the following procedure to upgrade Oracle Clusterware or Oracle Automatic Storage Management (Oracle ASM) from an earlier release to a later release.

Note:

When you upgrade to Oracle Clusterware 12c Release 1 (12.1), Oracle Automatic Storage Management (Oracle ASM) is installed in the same home as Oracle Clusterware. In Oracle documentation, this home is called the Oracle Grid Infrastructure home, or Grid home. Also note that Oracle does not support attempting to add additional nodes to a cluster during a rolling upgrade.
  1. If there are non-clustered, or single-instance, Oracle databases that use Oracle ASM running on any of the nodes in the cluster, they must be shut down before you start the upgrade. Listeners associated with those databases do not have to be shut down.

    Note:

    Oracle recommends that you leave Oracle Real Application Clusters (Oracle RAC) instances running during the Oracle Clusterware upgrade. During the upgrade process, the database instances on the node being upgraded are stopped and started automatically during the upgrade process.
  2. Start the installer, and select the option to upgrade an existing Oracle Clusterware and Oracle ASM installation.

  3. On the node selection page, select all nodes.

    Note:

    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. If you are upgrading from Oracle Clusterware 11g, then all nodes are selected by default. You cannot select or de-select the nodes.
  4. Select installation options as prompted.

  5. Confirm your selections, and then the upgrade scripts are run automatically..

    Note:

    If you receive an error indicating the server must be restarted before the installation completes, see Section A.12.1, "Completing Failed or Interrupted Upgrades,"
  6. After the Oracle Clusterware upgrade completes, if you are upgrading from a release earlier than Oracle ASM 11g Release 2 (11.2.0.1), and you left the check box for ASM Configuration Assistant (ASMCA) selected, as is the default, then the installer starts ASMCA to upgrade Oracle ASM. If you unchecked the box on the interview stage of the upgrade, then ASMCA is not run automatically.

    If an earlier release of Oracle ASM is installed, then the installer starts ASMCA to upgrade Oracle ASM to 12c Release 1 (12.1). You can upgrade Oracle ASM at this time, or upgrade it later.

    Oracle recommends that you upgrade Oracle ASM at the same time that you upgrade Oracle Clusterware. Until Oracle ASM is upgraded, Oracle databases that use Oracle ASM cannot be created and the Oracle ASM management tools in the Oracle Grid Infrastructure 12c Release 1 (12.1) home (for example, srvctl) do not work.

    Note:

    After the upgrade, if you set the Oracle Cluster Registry (OCR) backup location manually to the earlier release Oracle Clusterware home (CRS home), then you must change the OCR backup location to the Oracle Grid Infrastructure home (Grid home). If you did not set the OCR backup location manually, then this issue does not concern you.

    Because upgrades of Oracle Clusterware are out-of-place upgrades, the Oracle Clusterware home for the earlier release cannot be the location of the OCR backups. Backups in the old Oracle Clusterware home could be deleted.

  7. Because the Oracle Grid Infrastructure home is in a different location than the former Oracle Clusterware and Oracle ASM homes, update any scripts or applications that use utilities or other files that reside in the Oracle Clusterware and Oracle ASM homes.

See Also:

Section A.12, "Failed or Incomplete Installations and Upgrades" for information about completing interrupted upgrades

D.9.2 Completing an Oracle Clusterware Upgrade when Nodes Become Unreachable

If some nodes become unreachable in the middle of an upgrade, then you cannot complete the upgrade, because the upgrade did not complete succesfully on the unreachable nodes. Because the upgrade is incomplete, Oracle Clusterware remains in the previous release. You can confirm that the upgrade is incomplete by entering the command crsctl query crs activeversion.

To resolve this problem, run the rootupgrade.bat command with the -force flag using the following syntax:

Grid_home/rootupgrade -force

For example, as the Oracle Installation User for Oracle Grid Infrastructure, run the following command:

C:\> C:\app\12.1.0\grid\rootupgrade -force

This command forces the upgrade to complete. Verify that the upgrade has completed by using the command crsctl query crs activeversion. The active release should be the upgrade release.

The force cluster upgrade has the following limitations:

  • All active nodes must be upgraded to the newer release

  • All inactive nodes (accessible or inaccessible) may be either upgraded or not upgraded

  • For inaccessible nodes, after patch set upgrades, you can delete the node from the cluster. If the node becomes accessible later, and the patch version upgrade path is supported, then you can upgrade it to the new patch version.

D.9.3 Upgrading Inaccessible Nodes After Forcing an Upgrade

Starting with Oracle Grid Infrastructure 12c, after you complete a force cluster upgrade command, you can join inaccessible nodes to the cluster as an alternative to deleting the nodes, which was required in earlier releases. To use this option, Oracle Grid Infrastructure 12c Release 1 (12.1) software must already be installed on the nodes.

To complete the upgrade of inaccessible or unreachable nodes:

  1. Log in as the Oracle Installation User for Oracle Grid Infrastructure on one of the nodes that is a member of the cluster.

  2. Change directory to the crs\install directory in the Oracle Grid Infrastructure 12c Release 1 (12.1) Grid home. For example:

    C:\> cd app\12.1.0\grid\crs\install
    
  3. Run the following PERL command, where existing_node is the node in the cluster on which you run the command, and upgraded_node is the inaccessible or unreachable node that you want to join to the cluster:

    C:\..\install> rootcrs.pl -join -existingNode upgraded_node
    

D.10 Performing Rolling Upgrades of Oracle ASM

After you have completed the Oracle Clusterware portion of Oracle Grid Infrastructure 12c Release 1 (12.1) upgrade, you may need to upgrade Oracle ASM separately if the Oracle ASM portion of the Oracle Grid Infrastructure upgrade failed, or for some other reason Automatic Storage Management Configuration assistant (asmca) did not run

You can use asmca to complete the upgrade separately, but you should do it soon after you upgrade Oracle Clusterware, as Oracle ASM management tools such as srvctl do not work until Oracle ASM is upgraded.

Note:

ASMCA performs a rolling upgrade only if the earlier release of Oracle ASM is either 11.1.0.6 or 11.1.0.7. Otherwise, ASMCA performs a non-rolling upgrade, during which ASMCA shuts down all Oracle ASM instances on all nodes of the cluster, and then starts an Oracle ASM instance on each node from the new Oracle Grid Infrastructure home.

After you have upgraded Oracle ASM to Oracle Grid Infrastructure 12c Release 1, you can install individual patches for Oracle ASM by downloading them from the Oracle Automated Release Update site. See Section D.10.1, "Preparing to Complete a Separate Upgrade of Oracle ASM" for steps to upgrade Oracle ASM separately from Oracle Grid Infrastructure.

D.10.1 Preparing to Complete a Separate Upgrade of Oracle ASM

If you must complete upgrade of Oracle ASM separately, then note the following requirements:

  • The active release of Oracle Clusterware must be 12c Release 1 (12.1). To determine the active release, enter the following command from the Grid home:

    C:\..\bin> crsctl query crs activeversion
    
  • You can upgrade a single instance Oracle ASM installation to a clustered Oracle ASM installation. However, you can only upgrade an existing single instance Oracle ASM installation if you run the installation from the node on which Oracle ASM is installed. You cannot upgrade a single instance Oracle ASM installation on a remote node.

  • You must ensure that any rebalance operations on your existing Oracle ASM installation are completed before starting the upgrade process.

  • During the upgrade process, you alter the state of the Oracle ASM instances to an upgrade state. Because this upgrade state limits Oracle ASM operations, you should complete the upgrade process soon after you begin. The following operations are allowed when an Oracle ASM instance is in the upgrade state:

    • Diskgroup mounts and dismounts

    • Opening, closing, resizing, or deleting database files

    • Recovering instances

    • Queries of fixed views and packages: Users are allowed to query fixed views and run anonymous PL/SQL blocks using fixed packages, such as DBMS_DISKGROUP)

  • You do not need to shut down database clients unless they are on Oracle ACFS.

D.10.2 Upgrading Oracle ASM Separately from an Oracle Grid Infrastructure Upgrade

Complete the following tasks if you must upgrade from an Oracle ASM release where Oracle ASM was installed in a separate Oracle home, or if the Oracle ASM portion of Oracle Grid Infrastructure upgrade failed to complete:

  1. On the node you plan to start the upgrade, set the environment variable ASMCA_ROLLING_UPGRADE to true. For example:

    C:\> set ASMCA_ROLLING_UPGRADE=true
    
  2. From the Oracle Grid Infrastructure 12c Release 1 (12.1) home, start ASMCA. For example:

    C:\> cd app\12.1\grid\bin
    C:\..bin> asmca.bat
    
  3. Select Upgrade.

    Oracle ASM Configuration Assistant (ASMCA) upgrades Oracle ASM in succession for all nodes in the cluster.

  4. After you complete the upgrade, run the command to unset the ASMCA_ROLLING_UPGRADE environment variable.

    C:\> set ASMCA_ROLLING_UPGRADE=
    

See Also:

Oracle Database Upgrade Guide and Oracle Automatic Storage Management Administrator's Guide for more information about preparing an upgrade plan for Oracle ASM, and for starting, completing, and stopping Oracle ASM upgrades

D.11 Applying Patches to Oracle ASM

After you have upgraded Oracle ASM with Oracle Grid Infrastructure 12c Release 1, you can install individual patches for Oracle ASM by downloading them from My Oracle Support.

Starting with Oracle Grid Infrastructure 12c Release 1 (12.1), a new cluster state called "Rolling Patch" is available. This mode is similar to the existing "Rolling Upgrade" mode in terms of the Oracle ASM operations allowed in this quiesce state.

D.11.1 About Individual (One-Off) Oracle ASM Patches

Individual patches are called one-off patches. An Oracle ASM one-off patch is available for a specific release of Oracle ASM. If a patch you want is available, then you can download the patch and apply it to Oracle ASM using the OPatch Utility. The OPatch inventory keeps track of the patches you have installed for your release of Oracle ASM. If there is a conflict between the patches you have installed and patches you want to apply, then the OPatch Utility advises you of these conflicts. See Section D.11.3, "Patching Oracle ASM to a Software Patch Level" for information about applying patches to Oracle ASM using the OPatch Utility.

D.11.2 About Oracle Grid Infrastructure Software Patch Levels

The software patch level for Oracle Grid Infrastructure represents the set of all one-off patches applied to the Oracle Grid Infrastructure software release, including Oracle ASM. The release is the release number, in the format of major, minor, and patch set release number. For example, with the release number 12.1.0.1, the major release is 12, the minor release is 1, and 0.0 is the patch set number. With one-off patches, the major and minor release numbers remain the same, though the patch levels change each time you apply or roll back an interim patch.

As with standard upgrades to Oracle Grid Infrastructure, at any given point in time for normal operation of the cluster, all the nodes in the cluster must have the same software release and patch level. Because one-off patches can be applied as rolling upgrades, all possible patch levels on a particular software release are compatible with each other.

See Also:

D.11.3 Patching Oracle ASM to a Software Patch Level

  1. Download the patch you want to apply from My Oracle Support:

    https://support.oracle.com

    Select the Patches and Updates tab to locate the patch. To locate patch bundles, you can perform a Product or Family (Advanced) search for your platform and software release.

    Oracle recommends that you select Recommended Patch Advisor, and enter the product group, release, and platform for your software. My Oracle Support provides you with a list of the most recent patches and critical patch updates (CPUs).

    Place the patch in an accessible directory, such as C:\downloads.

  2. Change directory to the opatch directory in the Grid home. For example:

    C:\> cd app\12.1.0\grid\opatch
    
  3. Review the patch documentation for the patch you want to apply, and complete all required steps before starting the patch upgrade. Follow the instructions in the patch documentation to apply the patch.

D.12 Checking Cluster Health Monitor Repository Size After Upgrading

If you are upgrading from a prior release using IPD/OS to Oracle Grid Infrastructure 11g Release 2 (11.2.0.2 and later), then you should review the Cluster Health Monitor repository size (the CHM repository). Oracle recommends that you review your CHM repository needs, and enlarge the repository size to maintain a larger CHM repository.

Note:

Your previous IPD/OS repository is deleted when you install Oracle Grid Infrastructure.

By default, the CHM repository size is a minimum of either 1GB or 3600 seconds (1 hour), regardless of the size of the cluster.

To enlarge the CHM repository, use the following command syntax, where RETENTION_TIME is the size of CHM repository in number of seconds:

oclumon manage -repos changeretentiontime RETENTION_TIME

The value for RETENTION_TIME must be more than 3600 (one hour) and less than 259200 (three days). If you enlarge the CHM repository size, then you must ensure that there is local space available for the repository size you select on each node of the cluster. If there is not sufficient space available, then you can move the repository to shared storage.

For example, to set the repository size to four hours:

C:\> oclumon manage -repos changeretentiontime 14400

D.13 Downgrading Oracle Clusterware After an Upgrade

After a successful or a failed upgrade to Oracle Clusterware 12c Release 1 (12.1), you can restore Oracle Clusterware to the previous release. This section contains the following topics:

D.13.1 About Downgrading Oracle Clusterware After an Upgrade

Downgrading Oracle Clusterware restores the Oracle Clusterware configuration to the state it was in before the Oracle Clusterware 12c Release 1 (12.1) upgrade. Any configuration changes you performed during or after the Oracle Grid Infrastructure 12c Release 1 (12.1) upgrade are removed and cannot be recovered.

In the downgrade procedures, the following variables are used:

  • local node is the first node on which you started the upgrade process.

  • remote nodes are all other nodes where you started the upgrade process.

To restore Oracle Clusterware to the previous release, use the downgrade procedure for the release to which you want to downgrade.

D.13.2 Downgrading to Oracle Clusterware 11g Releases Prior to Release 11.2.0.1

To restore Oracle Clusterware to the previous release:

  1. On all remote nodes, as an Administrator user, use the command syntax Grid_home\crs\install\rootcrs.pl -downgrade [-force] to stop the Oracle Clusterware 12c Release 1 (12.1) resources, and shut down the Oracle Grid Infrastructure 12c Release 1 (12.1) stack.

  2. After the rootcrs.pl -downgrade script has completed on all remote nodes, on the local node use the following command syntax:

    Grid_home\crs\install\rootcrs.pl -downgrade -lastnode [-force]
    

    For example:

    C:\app\12.1.0\grid\crs\install> rootcrs.pl -downgrade -lastnode 
    

    Note:

    With Oracle Grid Infrastructure 12c, you no longer need to provide the location of the previous release Grid home or release number.

    This script downgrades the OCR. To stop a partial or failed Oracle Grid Infrastructure 12c Release 1 (12.1) installation and restore the previous release Oracle Clusterware, use the -force flag with this command.

  3. On each cluster member node where the upgrade completed successfully:

    1. Log in as the Oracle Grid Infrastructure installation owner.

    2. Use the following command to start the installer, where C:\app\12.1.0\grid represents the location of the new (upgraded) Grid home:

      setup.exe -updateNodeList -silent CRS=false ORACLE_HOME=C:\app\12.1.0\grid
      

      Add the flag -cfs if the Grid home is a shared home.

  4. On each cluster member node where the upgrade completed successfully:

    1. Log in as the Oracle Grid Infrastructure installation owner.

    2. Use the following command to start the installer, where the path you provide for the flag ORACLE_HOME is the location of the home directory from the earlier Oracle Clusterware installation.

      For example, if the location of the earlier Oracle Clusterware installation is C:\app\crs, the you would use a command similar to the following:

      C:\> cd C:\app\12.1.0\grid\oui\bin
      C:\..bin> setup.exe -updateNodeList -silent CRS=true ORACLE_HOME=C:\app\crs
      
    3. For downgrades to 11.1 and earlier releases

      If you are downgrading to Oracle Clusterware 11g Release 1 (11.1) or an earlier release, then you must run root.bat manually from the earlier release Oracle Clusterware home to complete the downgrade after you complete step b.

      OUI prompts you to run root.bat manually from the earlier release Oracle Clusterware installation home in sequence on each member node of the cluster to complete the downgrade. After you complete this task, downgrade is completed.

      Running root.bat from the earlier release Oracle Clusterware installation home restarts the Oracle Clusterware stack, starts all the resources previously registered with Oracle Clusterware in the older release, and configures the old initialization scripts to run the earlier release Oracle Clusterware stack.

  5. The installer stops the Oracle Grid Infrastructure 12c software stack. The Windows services used by Oracle Grid Infrastructure are recreated to refer to the Grid home for the older software release by one of the scripts during the downgrade process.

D.13.3 Downgrading to Oracle Clusterware 11g Release 2 (11.2.0.1) or Later Release

To restore Oracle Clusterware to the previous release:

  1. On all remote nodes, as an Administrator user, use the command syntax Grid_home\crs\install\rootcrs.pl -downgrade [-force] to stop the Oracle Clusterware 12c Release 1 (12.1) resources, and shut down the Oracle Grid Infrastructure 12c Release 1 (12.1) stack.

    For example:

    C:\app\12.1.0\grid\crs\install> rootcrs.pl -downgrade
    

    To stop a partial or failed Oracle Grid Infrastructure 12c Release 1 (12.1) installation and restore the previous release of Oracle Clusterware, use the -force flag with this command.

  2. After the rootcrs.pl -downgrade script has completed on all remote nodes, on the local node use the following command syntax:

    Grid_home\crs\install\rootcrs.pl -downgrade -lastnode [-force]
    

    For example:

    C:\app\12.1.0\grid\crs\install> rootcrs.pl -downgrade -lastnode 
    

    Note:

    With Oracle Grid Infrastructure 12c, you no longer need to provide the location of the previous release Grid home or release number.

    This script downgrades the OCR. To stop a partial or failed Oracle Grid Infrastructure 12c Release 1 (12.1) installation and restore the previous release Oracle Clusterware, use the -force flag with this command.

  3. On each cluster member node where the upgrade to Oracle Grid Iinfrastructure 12c has completed successfully, log in as an Administrator user, and use the following command to start the installer, where C:\app\12.1.0\grid is the location of the new (upgraded) Grid home (12.1):

    setup.exe -updateNodeList -silent CRS=false ORACLE_HOME=C:\app\12.1.0\grid
    

    Add the flag -cfs if the Grid home is a shared home.

  4. Run the following command, where C:\app\11.2.0.2\grid represents the home directory of the earlier Oracle Clusterware installation:

    setup.exe -updateNodeList -silent CRS=true ORACLE_HOME=C:\app\11.2.0.2\grid
    
  5. On each node, start Oracle Clusterware from the earlier release Oracle Clusterware home using the command crsctl start crs. For example, where the earlier release home is C:\app\11.2.0.2\grid, use the following command on each node:

    C:\app\11.2.0.2\grid\bin> crsctl start crs
    

D.14 Updating Oracle Enterprise Manager Cloud Control Target Parameters

Because the Oracle Clusterware upgrade is an out-of-place upgrade, the upgraded software has a new location for the Grid home. The path for the Oracle Clusterware home in some Oracle Enterprise Manager parameter files must be changed. If you do not change the CRS_HOME parameter, then you can encounter errors such as "cluster target broken" on Oracle Enterprise Manager Cloud Control.

To resolve the issue, upgrade the Enterprise Manager Cloud Control target, and then update the Enterprise Manager Agent Base Directory on each cluster member node running an agent, as described in the following sections:

D.14.1 Updating the Enterprise Manager Cloud Control Target After Upgrades

  1. Log in to Enterprise Manager Cloud Control

  2. Navigate to the Targets menu, and then to the Cluster page.

  3. Click a cluster target that was upgraded.

  4. Click Cluster, then Target Setup, and then Monitoring Configuration from the menu.

  5. Update the value for Oracle Home with the new Grid home path.

  6. Save the updates.

D.14.2 Updating the Enterprise Manager Agent Base Directory After Upgrades

  1. Navigate to the bin directory in the Management Agent home.

    The Agent Base Directory is a directory where the Management Agent home is created. The Management Agent home is in the path Agent_Base_directory\core\EMAgent_Version. For example, if the Agent Base Directory is C:\app\emagent, then Oracle creates the Management Agent home as C:\app\emagent\core\12.1.0.1.0.

  2. In the C:\app\emagent\core\12.1.0.1.0\bin directory, open the file emctl with a text editor.

  3. Locate the parameter CRS_HOME, and update the parameter to the new Grid home path.

  4. Repeat steps 1-3 on each node of the cluster with an Enterprise Manager agent.