Troubleshooting Common Edge Cases During Non-Rolling Patching
If an Oracle home component or background process (like an orphaned tfactl or management agent process) keeps a file handle open, OPatchAuto will fail to overwrite binaries.
This article explains what "execute in nonrolling mode exclusive" means, why OPatchAUTO72030 appears, implications for availability, prerequisites, step-by-step handling, troubleshooting, and best practices.
Run opatchauto apply -analyze prior to execution. This validates whether the environment can support the requested orchestration mode (rolling vs. non-rolling) without modifying system binaries. opatchauto72030 execute in nonrolling mode exclusive
Instead of restarting the entire patching session from scratch, you can instruct OPatchAuto to resume from where it failed, using explicit flags to force non-rolling behavior. Execute the following command as root : $ORACLE_HOME/OPatch/opatchauto resume -nonrolling Use code with caution.
/u01/app/grid/OPatch/opatchauto apply /u01/app/patches/72030 -nonrolling -exclusive Use code with caution. Copied to clipboard ⚠️ Critical Notes
– Likely refers to -exclusive flag or a mode where no other patching or configuration changes can occur simultaneously; often used for certain GI patches or when applying patches that affect clusterware binaries in a non‑rolling fashion. This validates whether the environment can support the
A: Strictly speaking, -nonrolling is the flag to enable non-rolling mode. The term "exclusive" in the context of opatchauto72030 often refers to the necessity of using this flag to exclusively patch a shared CRS home, a process that cannot be shared with rolling activity.
If opatchauto continues to fail with the 72030 orchestration error, you can fall back to using standard opatch manually on each home. This bypasses the automation layer orchestration entirely but requires manual stack management: # crsctl stop crs -f Use code with caution.
Understanding why this error occurs, how opatchauto manages orchestration modes, and how to safely resolve the conflict is essential for maintaining database uptime and patch integrity. Understanding the Error: OPatchAuto 72030 OPATCHAUTO-72030: Cannot execute in rolling mode
Note: Ensure your OPatch version matches or exceeds the minimum version specified in the Patch README.
Stop all databases running out of the Oracle Homes across all nodes: srvctl stop database -d Use code with caution.
Once the first node is finished, you must still run the command on the remaining nodes to update the local configuration and inventory, though the actual binary patching of the shared home is already done.
To ensure a smooth operation, the following steps represent a best-practice workflow:
OPATCHAUTO-72030: Execution mode invalid. OPATCHAUTO-72030: Cannot execute in rolling mode, as CRS home is shared. OPATCHAUTO-72030: Execute in non-rolling mode. OPatchAuto failed with error code 42. Use code with caution. Core Technical Concepts