Opatchauto72030 | Execute In Nonrolling Mode

# /OPatch/opatchauto apply -oh -nonrolling Common Causes for OPATCHAUTO-72030 Shared CRS Home

To bypass OPATCHAUTO-72030, you must explicitly instruct the opatchauto utility to run in a non-rolling fashion. Follow this strict operational workflow to execute the patch successfully. Step 1: Perform Vital Prerequisites

Unzip the patch files into a local directory on each node (e.g., /tmp/patch/ ) rather than using a shared ACFS or NFS mount, which can introduce locking latencies during non-rolling shutdowns. opatchauto72030 execute in nonrolling mode

Go to $GRID_HOME/OPatch/auto/dbsessioninfo/ .

The tool will:

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

Run the analyze command to ensure the patch is applicable without making changes: # /OPatch/opatchauto apply -oh -nonrolling Common Causes for

# Run on ALL nodes as root # crsctl stop crs -f

To bypass this guardian, the DBA must switch tactics from "rolling" (no downtime) to "non-rolling" (system-wide maintenance window). Stop the World Go to $GRID_HOME/OPatch/auto/dbsessioninfo/

Locate the folder corresponding to your patch ID or execution date. Open the main text log and the opatchauto_storage.log file.

: If the execution fails, check the logs located at: $GI_HOME/cfgtoollogs/opatchauto/