Opatchauto72030 Execute In Nonrolling Mode High Quality Guide

A typical execution command looks like:

opatchauto apply /path/to/patch/72030 -nonrolling

Or, if 72030 is an Oracle home label:

opatchauto apply /u01/app/oracle/product/19.0.0/dbhome_1 -nonrolling

Key parameters:

Imagine you are patching a 2‑node RAC with patch 72030 (a hypothetical October 2025 RU). The README states: “This patch updates the Clusterware binary and affects voting file locations. Non‑rolling mode is mandatory.”

Your command will be:

/opt/app/19c/grid/OPatch/opatchauto apply /staging/72030 -nonrolling

During execution, opatchauto will:

Expected total downtime: 45 minutes (20 minutes patching + 25 minutes restart and validation). opatchauto72030 execute in nonrolling mode high quality

| Pitfall | Solution | |--------|----------| | Running as wrong OS user | Always run opatchauto as the Grid home owner (grid), not oracle. | | Missing shared storage access | Ensure all nodes can access the same staged patch directory (e.g., NFS, ACFS). | | Rolling mode forced by default | Explicitly use -nonrolling; otherwise, opatchauto may default to rolling for RAC. | | Interrupted execution | Do not Ctrl+C. Use opatchauto resume if supported; otherwise, roll back using -rollback. | | SQL patch failures | Run datapatch -verbose manually after successful binary patching. |


If the patch causes critical failures, rollback in non-rolling mode. A typical execution command looks like: opatchauto apply

# As root
opatchauto rollback -patchid 36182763 -oh /u01/app/19.0.0/grid -nonrolling

| Error Message | Likely Cause | Resolution | |---------------|--------------|------------| | AC-00015: Cannot proceed - rolling mode required | Patch mandates rolling mode | Switch to -rolling or contact Oracle support | | AC-00030: opatchauto failed due to inventory lock | Another opatch process running | Kill other processes or reboot node | | PRCD-1120: Failed to stop resource | CRS resources not offline | Force stop: crsctl stop res -all -force | | OPATCHAUTO-72030: Incompatible home | Wrong home path specified | Verify home with opatch lsinventory -home |

  • Archive run artifacts to central location.
  • Remove staged patch files from local hosts (optionally keep for audit).
  • Document rollback and run root-cause analysis.