Downgrading Oracle Grid Infrastructure Using Online Abort Upgrade

If upgrade of Oracle Grid Infrastructure fails before setting the active version of Oracle Clusterware, then follow these steps to downgrade Oracle Grid Infrastructure to the earlier release.

Run this procedure to downgrade Oracle Clusterware only when the upgrade fails before root script runs the crsctl set crs activeversion command on the last node. Use this procedure for downgrading Oracle Grid Infrastructure if there is a need to avoid downtime of the whole cluster. This procedure downgrades the cluster to the previous release. Because Oracle ASM and database operations are limited in this state, it is recommended to move the cluster from this state as soon as possible. Complete the downgrade of Oracle Grid Infrastructure as per the procedure documented in Downgrading Oracle Grid Infrastructure after Upgrade Fails.

1. Shut down the Oracle Grid Infrastructure stack on the first node:

   crsctl stop crs

2. From any node where the Grid Infrastructure stack from the earlier release is running, unset the Oracle ASM rolling migration mode as follows:
   1. As the grid user, and run the following command as SYSASM user on the Oracle ASM instance:

      SQL> ALTER SYSTEM STOP ROLLING MIGRATION;

3. On any node running Oracle Grid Infrastructure other than the first node, from the Grid home of the earlier release, run the command:

   $ clscfg -nodedowngrade -h hostname

   hostname is the host name of the first node.

4. From the later release Grid home, run the command to downgrade Oracle Clusterware:

   $ rootcrs.sh -downgrade -online

   If rootcrs.sh is not present, then use rootcrs.pl.

5. Start Oracle Grid Infrastructure stack on the first node from the earlier release Grid home:

   $ crsctl start crs

Note:

You can downgrade the cluster nodes in any sequence.