If the CRS (Cluster Ready Services) home is shared across multiple nodes, it cannot be patched while other nodes are still using it.

Understanding OPATCHAUTO-72030: Mastering Non-Rolling Mode Patching

In some software versions (e.g., 12.2.0.1.10), a bug or specific validation might force the use of the -nonrolling flag even on single-node setups. How to Execute Patching in Non-Rolling Mode

Some specific patches contain changes that do not support different versions running simultaneously across the cluster.

The error typically occurs during Oracle Grid Infrastructure (GI) patching when the utility detects a configuration—such as a shared CRS home —that is incompatible with standard rolling mode. This error is a safeguard, informing the user that the patching session cannot proceed unless it is explicitly executed in non-rolling mode . Why Does OPATCHAUTO-72030 Occur?

Oracle's opatchauto utility defaults to , which patches one node at a time while keeping the cluster operational. However, certain environments require a full cluster shutdown:

To resolve error 72030 and successfully apply your patch, you must use the -nonrolling parameter. 1. Prepare the Environment Rocky Linux release 8.8 19c rac ru安装 - 墨天轮