Opatchauto72030 Execute In Nonrolling Mode __full__ May 2026
OPatchAuto72030 typically occurs when you attempt to execute a patch in non-rolling
mode, but the environment or the specific patch metadata requires rolling execution (or vice versa).
This report outlines the cause, impact, and resolution for this issue. Executive Summary During the application of a patch using opatchauto , the utility failed with error
. This indicates a conflict between the execution mode specified in the command line and the patch's internal orchestration requirements. Problem Description Error Code: OPatchAuto72030
"The patch(es) do not support the specified execution mode." This usually happens when using the -nonrolling
flag on a patch designed only for rolling updates, or when the Grid Infrastructure (GI) stack state prevents non-rolling execution. Analysis of Causes Patch Metadata Constraints
: Some Bundle Patches (BP) or Release Updates (RU) have internal flags that mandate a rolling fashion to maintain high availability. Stack State
: If the Oracle Clusterware is partially active or in a state that opatchauto deems incompatible with a "stop-all" non-rolling approach. Command Syntax : Incorrect use of -nonrolling
on patches that contain components (like JVM updates) which require specific sequences. Resolution Steps 1. Verify Patch Documentation file for the specific Patch ID.
Confirm if "Non-Rolling" is a supported install method for that version. opatchauto72030 execute in nonrolling mode
Note if specific prerequisite steps (like stopping certain services manually) are required. 2. Execute in Rolling Mode (Recommended)
Unless there is a specific architectural reason to down the entire cluster, use the default rolling mode: # Run without the -nonrolling flag ./opatchauto apply
If you must apply it non-rolling (e.g., during a complete blackout window), ensure all services are stopped and use the override if available, though this is generally discouraged for RU patches. 4. Update OPatch and OPatchAuto
Ensure you are using the latest version of the OPatch utility. Download the latest OPatch from My Oracle Support (MOS).
Incompatibility often arises from outdated patching tools trying to read new patch metadata. Conclusion
is a safety mechanism to prevent inconsistent patch states. To proceed, align the command-line arguments with the instructions found in the patch's README or default to a rolling application to ensure cluster integrity. Next Steps: Check your current OPatch version opatch version Review the patch README for the "Installation Method" section. Provide the if you need specific command syntax for that update.
Troubleshooting Oracle Error: OPatchAuto-72030 Execute in Non-Rolling Mode
When patching a multi-node Oracle Grid Infrastructure or RAC environment, the automation provided by opatchauto is usually a lifesaver. However, encountering OPatchAuto-72030 can bring your maintenance window to a grinding halt.
This error typically indicates a validation failure where the tool detects a conflict between the requested patching mode (Non-Rolling) and the current state or configuration of the cluster. Understanding the Error OPatchAuto72030 typically occurs when you attempt to execute
The full error message usually looks like this:OPatchAuto-72030: Execute in non-rolling mode failed.
In a Non-Rolling upgrade or patch application, all nodes in the cluster are expected to be shut down or updated simultaneously. This is the opposite of Rolling mode, where nodes are patched one by one to maintain high availability. Common Causes
Node Status Inconsistency: One or more nodes are still active or have services running that prevent a global "Non-Rolling" lock.
Incorrect Flag Usage: Using the -nonrolling flag on an environment that was initially patched (or partially patched) in rolling mode.
Inventory Issues: The Central Inventory or the local oraInventory on one of the nodes is out of sync.
Resource Busy: Internal Oracle Clusterware resources are holding locks that prevent the non-rolling transition. How to Resolve OPatchAuto-72030 1. Verify the Cluster State
Before running opatchauto in non-rolling mode, ensure that the stack is prepared. While opatchauto attempts to manage the stack for you, manual interference often causes this error. Check the status: crsctl check cluster -all
If you are performing a manual non-rolling patch, ensure the stack is down on all nodes if required by the specific patch readme. 2. Check for "Half-Finished" Sessions
If a previous patching attempt failed, opatchauto might have left a session state behind. Look for VERIFICATION PASSED or VALIDATION SUCCEEDED
Clear the session: Try running opatchauto resume to see if it can complete the previous action.
If it’s stuck, you may need to check the input.json or state files in the OPatch/auto/core directory (though modifying these is for advanced users only). 3. Validate OPatch and OPatchAuto Versions
Outdated patching tools are a leading cause of 70000-series errors.
Ensure OPatch is at the latest version recommended by My Oracle Support (MOS) for your specific Release Update (RU).
Update OPatch on all nodes in the cluster, not just the local node. 4. Use the Log Files
The console output for OPatchAuto-72030 is often vague. To find the "smoking gun," navigate to:$ORACLE_HOME/cfgtoollogs/opatchauto/
Look for the specific execution ID folder. Inside, check the opatchauto_. Search for the "FAILED" keyword just above the 72030 error code; it will usually point to a specific node or a specific system command that failed. 5. Manual Fallback
If opatchauto continues to fail in non-rolling mode, you can fall back to the manual opatch method: Stop the stack on the node.
Run opatch apply (following the patch readme instructions for manual steps). Run the necessary post-install scripts.
The OPatchAuto-72030 error is essentially a "safety catch." It triggers when the tool isn't 100% sure it can safely take down the entire cluster or apply the patch globally without risking corruption. By updating your OPatch utility and ensuring a clean cluster state, you can usually bypass this hurdle.
3.2. Validate Patch Applicability
cd /u01/app/stage/34774103 # patch directory
opatchauto apply -analyze
- Look for
VERIFICATION PASSEDorVALIDATION SUCCEEDED.
5.1 Extended Downtime
- Rolling mode: Application outage is seconds to minutes per node (failover).
- Non-rolling mode: Entire cluster is down for 15–60 minutes (or longer, depending on patch size).
Error 4: "Patch 72030 conflicts with patch 68300"
Cause: Another interim patch is already installed.
Fix: Roll back conflicting patch first or merge patches using opatch napply.