[grid@racnode1 ~]$ opatchauto apply /soft/72030 -nonrolling OPatchauto session initiated at Wed Apr 13 09:00:00 2026System configuration: RAC with 2 nodes Mode: Non-rolling (cluster-wide downtime)
Validating patch 72030... Conflict check passed. Shutting down cluster services on all nodes... OK
Applying patch to nodes: racnode1, racnode2 racnode1: Patch applied successfully. racnode2: Patch applied successfully. opatchauto72030 execute in nonrolling mode
Running root scripts... racnode1: rootupgrade.sh completed. racnode2: rootupgrade.sh completed.
OPatchauto completed successfully at Wed Apr 13 09:45:00 2026When applying patches, opatchauto can operate in two
When applying patches, opatchauto can operate in two main modes: Cause: Another interim patch is already installed
# As grid user on each node
$ORACLE_HOME/OPatch/opatch lspatches
Cause: Another interim patch is already installed.
Fix: Roll back conflicting patch first or merge patches using opatch napply.
| Issue | Action |
|--------|--------|
| PRIF-10XX (OCR errors) | Run ocrcheck, ensure voting disks online |
| opatchauto apply -nonrolling fails mid‑way | Use opatchauto resume after fixing cause |
| Inconsistent patch state across nodes | Run opatchauto rollback /patch/path -nonrolling |
Oracle’s opatchauto utility is the standard tool for applying interim patches, bundle patches, and Patch Set Updates (PSU) to Oracle Grid Infrastructure (GI) and Oracle RAC environments. Patch 72030 (used here as a representative patch ID) may require specific application strategies. This paper details the execution of opatchauto for patch 72030 using non-rolling mode — where all cluster nodes are patched simultaneously with downtime. We compare it to rolling mode, provide exact command syntax, pre-requisites, and a step-by-step execution guide.