1. Grid Infrastructure Installation and Upgrade Guide
  2. Upgrading Oracle Grid Infrastructure
  3. Preparing to Upgrade an Existing Oracle Clusterware Installation
  4. Upgrade Checklist for Oracle Grid Infrastructure

Upgrade Checklist for Oracle Grid Infrastructure

Review this checklist before upgrading an existing Oracle Grid Infrastructure. A cluster is being upgraded until all cluster member nodes are running the new installations, and the new clusterware becomes the active version.

Table 11-1 Upgrade Checklist for Oracle Grid Infrastructure Installation

Check Task
Review Upgrade Guide for deprecation and desupport information that may affect upgrade planning.

Oracle Database Upgrade Guide
Patch set (recommended) Install the latest patch set release for your existing installation. Review My Oracle Support note 2180188.1 for the list of latest patches before upgrading Oracle Grid Infrastructure.
Install user account Confirm that the installation owner you plan to use is the same as the installation owner that owns the installation you want to upgrade.
Create a Grid home Create a new Oracle Grid Infrastructure Oracle home (Grid home) where you can extract the image files. All Oracle Grid Infrastructure upgrades (upgrades of existing Oracle Clusterware and Oracle ASM installations) are out-of-place upgrades.
Instance names for Oracle ASM

Oracle Automatic Storage Management (Oracle ASM) instances must use standard Oracle ASM instance names.

The default ASM SID for a single-instance database is +ASM.

Cluster names and Site names Cluster names must have the following characteristics:

  • At least one character but no more than 15 characters in length.

  • Hyphens (-), and single-byte alphanumeric characters (a to z, A to Z, and 0 to 9).

  • It cannot begin with a numeric character.

  • It cannot begin or end with the hyphen (-) character.
Operating System Confirm that you are using a supported operating system, kernel release, and all required operating system packages for the new Oracle Grid Infrastructure installation.
Network addresses for standard Oracle Grid Infrastructure

For standard Oracle Grid Infrastructure installations, confirm the following network configuration:

  • The private and public IP addresses are in unrelated, separate subnets. The private subnet should be in a dedicated private subnet.

  • The public and virtual IP addresses, including the SCAN addresses, are in the same subnet (the range of addresses permitted by the subnet mask for the subnet network).

  • Neither private nor public IP addresses use a link local subnet (169.254.*.*).
OCR on raw or block devices Migrate OCR files from RAW or Block devices to Oracle ASM or a supported file system. Direct use of RAW and Block devices is not supported.

Run the ocrcheck command to confirm Oracle Cluster Registry (OCR) file integrity. If this check fails, then repair the OCR before proceeding.

Check space for GIMR

When upgrading to Oracle Grid Infrastructure 19c or a later release, a new GIMR is created only if the source Grid home has a GIMR configured. Allocate additional storage space as described in Oracle Clusterware Storage Space Requirements.

When upgrading from Oracle Grid Infrastructure 12c Release 2 (12.2), the GIMR is preserved with its contents.
Oracle ASM password file

When upgrading from Oracle Grid Infrastructure 12c Release 2 (12.2), Oracle Grid Infrastructure 18c, or Oracle Grid Infrastructure 19c to Oracle Grid Infrastructure 21c, move the Oracle ASM password file from file system to Oracle ASM, before proceeding with the upgrade using the following ASMCMD command:

ASMCMD [+] > pwcopy --asm current_location_of_ASM_password_file_in_OS_directory +target_disk_group_name/orapwASM

Note:

Set compatible.asm to at least 12.2.0.1, before moving the password file.
CVU Upgrade Validation Use Cluster Verification Utility (CVU) to assist you with system checks in preparation for starting an upgrade.
Shut Down Single-instance Database If you have a single-instance database on a cluster that uses Oracle ASM, then you must shut down the single-instance database before upgrading.
Unset Environment variables

As the user performing the upgrade, unset the environment variables $ORACLE_HOME and $ORACLE_SID.

Check that the $ORA_CRS_HOME environment variable is not set. Do not use $ORA_CRS_HOME as an environment variable, except under explicit direction from Oracle Support.

Refer to the Checks to Complete Before Upgrading Oracle Grid Infrastructure for a complete list of environment variables to unset.

Check system upgrade readiness with dry-run upgrade Run Oracle Grid Infrastructure installation wizard, gridSetup.sh, in dry-run upgrade mode to perform system readiness checks for Oracle Grid Infrastructure upgrades.
Oracle ORAchk Upgrade Readiness Assessment Download and run the Oracle ORAchk Upgrade Readiness Assessment to obtain automated upgrade-specific health check for upgrades to Oracle Grid Infrastructure. See My Oracle Support note 1457357.1, which is available at the following URL:

https://support.oracle.com/rs?type=doc&id=1457357.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.
HugePages memory allocation Allocate memory to HugePages large enough for the System Global Areas (SGA) of all databases planned to run on the cluster, and to accommodate the System Global Area for the Grid Infrastructure Management Repository.

Related Topics

Parent topic: Preparing to Upgrade an Existing Oracle Clusterware Installation