Opatchauto72030 Execute In Nonrolling Mode Exclusive Best
Oracle Grid Infrastructure and Database patching can be a complex task, even for experienced Database Administrators (DBAs). One of the most common and disruptive errors encountered during a non-rolling patch application is
Typically, the error manifests in the OPatchAuto log files with a signature resembling this:
When faced with the OPATCHAUTO-72030 error, the resolution is straightforward: rerun the command with the -nonrolling flag. The general syntax for applying a patch in non-rolling mode is as follows: opatchauto72030 execute in nonrolling mode exclusive
All nodes are shut down, and the patch is applied to the shared grid home simultaneously.
What are you currently patching (e.g., 19c, 21c)? Oracle Grid Infrastructure and Database patching can be
# /OPatch/opatchauto apply -nonrolling Use code with caution. Copied to clipboard (Reference:) Preparation:
Stop all databases running out of the Oracle Homes across all nodes: srvctl stop database -d Use code with caution. What are you currently patching (e
OPatchAuto can be executed either as the root user or as the Oracle home owner. When executed as a non-root user, it requires a wallet containing the necessary credentials to switch to root during critical patching phases. As a rule, Oracle strongly recommends running OPatchAuto from the product home as the root user to ensure all operations complete without permission-related interruptions.
# /GRID_HOME/rdbms/install/rootadd_patch.sh Use code with caution. Start the stack back up: # crsctl start crs Use code with caution. Best Practices to Avoid Future Failures
The reason for the 72030 error is now clear: for a shared CRS home, Oracle cannot safely perform rolling patching because a shared home is simultaneously accessed by multiple nodes. Any rolling operation would cause version mismatches and potential cluster corruption. Therefore, OPatchAuto enforces a non-rolling session, resulting in an exclusive lock on the home. This "exclusive" access during the non-rolling mode ensures that no other node interferes with the patching process, guaranteeing data integrity and a successful patch application.
