The error code is a specific warning and pre-check constraint triggered by Oracle's automated patching orchestrator ( opatchauto ). It occurs during the application of complex patches—such as Grid Infrastructure (GI) Release Updates (RU) or Patch Set Updates (PSU)—in a multi-node Real Application Clusters (RAC) environment.
To help provide more specific guidance,g., 19.18, 19.21, 21c).
# Check patch inventory for Grid and Database homes $GRID_HOME/OPatch/opatch lsinventory $ORACLE_HOME/OPatch/opatch lsinventory # Check clusterware functionality status $GRID_HOME/bin/crsctl check crs $GRID_HOME/bin/crsctl stat res -t Use code with caution. Best Practices to Avoid OPatchAuto Failures opatchauto72030 execute in nonrolling mode exclusive
Mastering OPatchAuto Error 72030: How to Execute in Non-Rolling Mode
This article is your definitive guide to the OPATCHAUTO-72030 error. We will explore its precise meaning, the differences between rolling and non-rolling patching modes, why a shared CRS home forces non-rolling mode, and provide a step-by-step guide to executing OPatchAuto in non-rolling mode. We'll also cover best practices and how to handle the "exclusive" nature of this operation. The error code is a specific warning and
Typically, the error manifests in the OPatchAuto log files with a signature resembling this:
opatchauto apply /path/to/patch/ -nonrolling -local Use code with caution. Scenario B: Active Session Invalidation Error # Check patch inventory for Grid and Database
Once the first node is finished, you must still run the command on the remaining nodes to update the local configuration and inventory, though the actual binary patching of the shared home is already done.
In non-rolling mode, the cluster is down by design. However, if your patch includes a reboot script, nodes may not rejoin correctly.
: If your /u01/app/19.0.0/grid (or similar) is on a shared file system, you must use the -nonrolling flag.