If you are certain the environment is correct, the most common fix is to on all nodes first, then run opatchauto using the -binary flag. This bypasses the orchestration of the stack and focuses solely on the software bits:
– For RAC or Oracle Clusterware, "nonrolling mode" means all nodes will be patched at the same time (cluster downtime required), as opposed to "rolling mode" (one node at a time with cluster still available).
The resulting output will look like this:
A: Yes, more so than rolling mode. While rolling mode aims for zero downtime, non-rolling mode requires remote nodes to be down, which will result in downtime for the applications accessing those nodes. opatchauto72030 execute in nonrolling mode exclusive
"We’re going dark," Alex announced to the monitoring team. Following the standard protocol , Alex began the transition to non-rolling mode The Shutdown
Patch the first node while the Grid Infrastructure (GI) stack is up. Phase 2 (Remote Nodes 2 to n-1): Patch these nodes in parallel. Phase 3 (Final Node): Complete the session on the last node. Oracle Help Center Best Practices for Error 72030 Verify Cluster State:
Before running the command, you must stop the Oracle Clusterware (CRS) on all nodes to prepare for the non-rolling (exclusive) application. As root : # /bin/crsctl stop crs -all Use code with caution. Step 2: Apply the Patch with -nonrolling If you are certain the environment is correct,
This is the command that triggers the outage and patching.
Ensure that no orphaned Oracle processes are lingering on the problematic node. Run these commands as the root user:
Explicitly stop the Grid Infrastructure stacks on all remote cluster nodes ( ) to satisfy non-rolling parameters: While rolling mode aims for zero downtime, non-rolling
This specific error typically occurs when the orchestration engine fails to validate the environment or execute the required shutdown/startup sequences necessary for a non-rolling patch application. What is Non-Rolling Mode?
If your configuration uses a shared storage location (e.g., NFS, ACFS) for the Grid Infrastructure home ( $GRID_HOME ) across multiple nodes, opatchauto will identify this shared state and throw the OPATCHAUTO-72030 error. It forces you to use the -nonrolling flag because patching a shared home while a node is running will cause corruption. Steps to Execute in Non-Rolling Mode (Exclusive)
Search for any residual lock files or active session tracking folders (e.g., *.lock or session IDs).
Troubleshooting Common Edge Cases During Non-Rolling Patching