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
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
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 If opatchauto detects that remote nodes are down
Run the opatchauto apply command with the -nonrolling flag. The error message typically occurs during Oracle Grid
