Opatchauto72030 Execute In Nonrolling Mode Exclusive |top| Jun 2026

Shared home /u01/app/19.0.0/grid can only be patched in nonrolling mode. 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.

What is the you entered right before the error appeared?

This is the command that triggers the outage and patching.

Because the automated tracking mechanism behaves differently during non-rolling shared home updates, verify that database-level data dictionary updates are properly applied. Once the binary phase concludes and the cluster stacks are successfully restarted across all nodes, run the datapatch tool to sync the SQL modifications: Doc ID 2957442.1 OPATCHAUTO-72030 During Opatchauto

srvctl stop database -d yourdb srvctl stop listener opatchauto72030 execute in nonrolling mode exclusive

| Feature | Rolling Mode | Non-Rolling Exclusive | |---------|--------------|------------------------| | Downtime | Minimal (per node) | Full cluster downtime | | Risk | Lower | Higher | | Speed | Slower (sequential) | Faster (parallel) | | Exclusive lock | No | Yes | | Use case | Production with HA | Maintenance window |

Always remember: The -exclusive flag locks others out. The -nonrolling flag locks your database out. Plan accordingly, test rigorously, and keep your crsctl commands ready.

The failure message indicates that the orchestration engine cannot proceed in the default "rolling" mode (patching one node at a time while others stay up).

Never cancel an opatchauto session mid-execution using Ctrl+C or kill -9 unless absolutely necessary. If a freeze occurs, allow the built-in timeouts to trigger so the utility can run its cleanup routines. Shared home /u01/app/19

This flag modifies the behavior of the patching session. When you use exclusive in conjunction with opatchauto execute :

# As root user: opatchauto apply /path/to/patch/number -nonrolling Use code with caution. Copied to clipboard 🔍 Why This Happens

A single master copy of the Grid Infrastructure binaries resides on a clustered filesystem shared by all nodes. Because the underlying executable disk footprint is singular, any binary change affects every node simultaneously, making non-rolling execution mandatory. Step-by-Step Resolution Guide

# /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 OPATCHAUTO-72030: Execute in non-rolling mode

$GRID_HOME/bin/crsctl check crs $GRID_HOME/bin/crsctl stat res -t Use code with caution.

Ensure you have the latest OPatch utility installed in both GI and Database homes. Backup: Always back up your Oracle Home before proceeding.

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

By default, opatchauto applies patches in , which allows nodes to be patched one by one without total cluster downtime. However, certain patches or configurations (such as shared CRS homes ) are not "rollable". When opatchauto detects this, it throws the following message: