Upgrading Oracle Grid Infrastructure Using Command-Line Interface

Complete this procedure to upgrade Oracle Grid Infrastructure (Oracle Clusterware and Oracle Automatic Storage Management) from an earlier release using the command-line interface.

Note:

You must migrate from Oracle ASMFD to Oracle ASMLib before starting the upgrade.
You must remove Grid Infrastructure Management Repository (GIMR) before starting the upgrade.

You should have your network information, storage information, and operating system users and groups available to you before you start upgrade, and you should be prepared to run root scripts.

As the grid user, download the Oracle Grid Infrastructure image files and extract the files to the Grid home.
For example:
```
mkdir -p /u01/app/23.0.0/grid
chown grid:oinstall /u01/app/23.0.0/grid
cd /u01/app/23.0.0/grid
unzip -q download_location/grid_home.zip
```
download_location/grid_home.zip is the path of the downloaded Oracle Grid Infrastructure image file.
Note:
- You must extract the image software into the directory where you want your Grid home to be located.
- Download and copy the Oracle Grid Infrastructure image files to the local node only. During upgrade, the software is copied and installed on all other nodes in the cluster.
If Oracle ASMFD was configured in the earlier release, then migrate from Oracle ASMFD to Oracle ASMLib.
Confirm if Grid Infrastructure Management Repository (GIMR) was configured in the earlier release.
```
srvctl config mgmtdb
```
Confirm if Oracle Fleet Patching and Provisioning (Oracle FPP) was configured in central server mode in the earlier release.
```
srvctl config rhpserver
```
Note:
- If Oracle FPP is configured on your cluster, then you are recommended to use the Oracle FPP Self-Upgrade feature for smooth migration of the metadata from GIMR to the new metadata repository. Refer to Oracle Fleet Patching and Provisioning Self Upgrade for more information about how to use the Oracle FPP Self-Upgrade feature.
- If you upgrade Oracle Grid Infrastructure using this procedure, then you must re-configure Oracle FPP metadata repository to use the Oracle FPP Server. Refer to Migrating Metadata from GIMR to Oracle FPP Metadata Repository for steps to re-configure Oracle FPP metadata repository.
If the GIMR was configured in the earlier release and Oracle FPP was configured in central mode, then export the Oracle FPP Metadata to re-configure Oracle FPP after the upgrade and remove GIMR from the existing Oracle Grid Infrastructure installation.
```
Grid_home/crs/install/reposScript.sh -export_dir=dir_to_export_CHA_model_and_Oracle_FPP_metadata
```
Note:
- Exporting CHA models is optional. If the export fails, then you can continue removing the GIMR.
- You can remove GIMR even if you do not upgrade to Oracle Grid Infrastructure 23ai. However, it is mandatory to remove GIMR before the upgrade.

Start the Oracle Grid Infrastructure installation by running the following command.

cd /u01/app/23.0.0/grid
./gridSetup.sh -upgrade -ORACLE_BASE /u01/app/grid [-ignoreDownNodes] -executeConfigTools -executeRootScript -configMethod ROOT

Provide the root user password when prompted.
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, libraries, or other files that reside in the Oracle Clusterware and Oracle ASM homes.
Update the Oracle Enterprise Manager target parameters as described in the topic Updating Oracle Enterprise Manager Cloud Control Target Parameters.

Note:

After upgrading to Oracle Grid Infrastructure 23ai, remove the ADR_BASE=/u01/app/grid entry from $ORACLE_HOME/network/admin/sqlnet.ora file, if you use Oracle ASM for database storage.
At the end of 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 new Oracle Grid Infrastructure home (Grid home). If you did not set the OCR backup location manually, then the backup location is changed for you during the upgrade.
Because upgrades of Oracle Clusterware are out-of-place upgrades, the previous release Oracle Clusterware home cannot be the location of the current release OCR backups. Backups in the old Oracle Clusterware home can be deleted.
If the cluster being upgraded has a single disk group that stores the OCR, OCR backup, Oracle ASM password, and the Oracle ASM password file backup, then Oracle recommends that you create a separate disk group or use another existing disk group and store the OCR backup and Oracle ASM password file backup in that disk group.