Opatchauto72030 Execute In Nonrolling Mode Exclusive [hot] π₯ π
Show you the of your Grid Home before you begin.
This error indicates that opatchauto detected a , which makes traditional rolling patching impossible. This article explains the cause of the OPATCHAUTO-72030 error, why non-rolling mode is required, and provides a step-by-step guide to executing the patch in non-rolling mode, including the necessary exclusive actions. What Causes OPATCHAUTO-72030? Oracle RAC patching typically happens in one of two modes:
The flags passed to the command (like mixing rolling and non-rolling parameters) conflict with the patch metadata instructions.
After applying the fix, the command should complete without the OPATCHAUTO-72030 error, proceeding to apply the patch in non-rolling mode.
Stop the Oracle high-availability services on all nodes using the Oracle Cluster Control # Run on all nodes $GRID_HOME/bin/crsctl stop crs Use code with caution. Copied to clipboard Verify that no processes are holding the binaries. 2. Execute with the -nonrolling Flag The fix is to explicitly tell opatchauto opatchauto72030 execute in nonrolling mode exclusive
You should use this mode in the following scenarios:
To resolve this, you must explicitly use the -nonrolling option in your command. For non-rolling mode, before applying the patch. Correct Command Syntax:
# opatchauto apply -oh -nonrolling Use code with caution. Copied to clipboard Key Considerations for "Exclusive" Mode
While the primary keyword focuses on simply adding the -nonrolling flag, advanced users in a clustered environment may need to ensure execution. Exclusive execution refers to situations where you must patch the GI home separately from the Database home, or vice versa, without interference. Show you the of your Grid Home before you begin
Before executing the command, the following must be validated to prevent failure mid-outage:
The Grid Infrastructure management repository (GIMR) or cluster registry (OCR) being locked by another node or an orphaned process.
opatch lspatches | grep 72030
/u01/app/19.0.0/grid/OPatch/opatchauto apply /soft/<patch_location> -oh /u01/app/19.0.0/grid -nonrolling What Causes OPATCHAUTO-72030
Take a complete backup of your central inventory and the Grid Infrastructure home: tar -cvf gi_home_backup.tar $GRID_HOME Use code with caution. Step 2: Prepare the Cluster for Non-Rolling Operations
3 Concepts of Multi-Node Patch Orchestration Using OPatchAuto
If the 72030 error occurred mid-patch and left the cluster in a partially patched state, you must resume the session without the offending flag. Clean up any dead lock files if prompted by the utility. Resume the orchestration: $GRID_HOME/OPatch/opatchauto resume Use code with caution.
Step 4: Manual Exclusive Rollback/Roll-forward (The Fallback Method)