The primary reason for this specific error code is a configuration. In a shared home, multiple nodes use the same physical installation binaries. Since a rolling patch updates binaries while they are still in use by other nodes, it would cause immediate system instability or failure. To protect the environment, opatchauto throws error 72030 to force a full maintenance window. Other triggers for non-rolling mode include:
Download the latest OPatch utility and your target patch from My Oracle Support . Back up your Oracle Homes before proceeding. opatchauto72030 execute in nonrolling mode
Once completed, use ./opatch lsinventory to confirm the patch is successfully applied across the homes. Key Differences: Rolling vs. Non-Rolling Non-Rolling upgrade in RAC using opatchauto - Oracle Forums The primary reason for this specific error code
The error message typically occurs during Oracle Grid Infrastructure (GI) or RAC database patching when the opatchauto utility detects an environment that does not support the default rolling mode. By default, opatchauto attempts to patch nodes sequentially (one at a time) to maintain high availability. However, certain configurations—most notably shared Oracle Homes —require a full cluster shutdown and a non-rolling execution. Why OPATCHAUTO-72030 Occurs To protect the environment, opatchauto throws error 72030
In a non-rolling session, all remote nodes must be shut down. Only the local node where you run the command should have the GI stack up.
Some patches contain metadata explicitly stating they cannot be applied in a rolling fashion due to significant binary or architectural changes.
If opatchauto detects that remote nodes are down or the cluster stack is inconsistent, it may require a non-rolling approach to resynchronize the nodes. How to Execute in Non-Rolling Mode