Opatchauto72030 Execute In Nonrolling Mode Exclusive =link= Now

When applying Oracle Grid Infrastructure or RAC patches, encountering typically indicates a conflict between the requested patching mode and the target environment's configuration. This error occurs when OPatchAuto attempts to default to rolling mode but determines that a non-rolling execution is required. Understanding the Error: OPATCHAUTO-72030

When patching Oracle Real Application Clusters (RAC) or Grid Infrastructure (GI), administrators frequently use the opatchauto utility to automate the process. However, during patching, you may encounter the following error:

When executing OPatch in non-rolling mode, there are two sub-modes: shared and exclusive. In shared mode, multiple OPatch sessions can run concurrently, allowing multiple patches to be applied simultaneously. However, this can lead to conflicts and errors if multiple patches are applied to the same database object. Exclusive mode, on the other hand, ensures that only one OPatch session can run at a time, providing a higher level of control and minimizing the risk of conflicts.

opatchauto execute /path/to/72030 -nonrolling exclusive opatchauto72030 execute in nonrolling mode exclusive

cd $ORACLE_HOME (Grid home) $ORACLE_HOME/OPatch/opatchauto apply /stage/72030 -nonrolling -exclusive

Proceed with this method only if the business allows a downtime window of at least 1-2 hours (depending on node count) and if a verified fallback strategy (restoring homes from backup) is in place. If high availability is paramount, switch to Rolling Mode .

OPatchAuto tracks progress in the storage management and inventory. If a previous run crashed, it might still think it is in the middle of a "rolling" window. Check the inventory status using: opatch lsinventory. When applying Oracle Grid Infrastructure or RAC patches,

If no other DBA is actively running a patch, manually remove or back up these lock files to clear the exclusive block. 2. Validate the Cluster State

Manually appending the -nonrolling parameter to opatchauto apply or opatchauto resume commands on a bundle patch that contains exclusive sub-patches.

opatchauto detected that another patching process is running, or a previous failed session did not clean up its lock files. However, during patching, you may encounter the following

Run OPatchAUTO in nonrolling mode:

: Use the resume parameter to pick up exactly where the automation stopped: opatchauto resume Use code with caution. Best Practices for Enterprise Patching Workflows

"For this patch, you must run opatchauto in non-rolling and exclusive mode."

It runs post-patching configuration tools ( rootcrs.sh or rootcrs.pl ). It restarts the local Oracle Clusterware stack. Step 4: Serial Processing of Remaining Nodes

To run OPatchAuto in non-rolling mode, you must explicitly specify the -nonrolling option.