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.
Cause: You applied to the wrong Oracle home (e.g., DB home instead of GI home).
Solution: Check ORACLE_HOME before running. Use absolute path to the correct home’s opatchauto.
Although opatchauto can attempt to shutdown databases automatically in non‑rolling mode, it is safer to do it manually: opatchauto72030 execute in nonrolling mode
# As oracle user on each node
srvctl stop database -d <db_unique_name>
srvctl status database -d <db_unique_name> # Verify all instances are down
Assuming you have met all prerequisites, here is the exact procedure to apply patch 72030 across a 2‑node or multi‑node cluster in non‑rolling mode.
<path_to_opatchauto> apply /stage/patches/72030 -analyze -nonrolling Oracle’s opatchauto utility is the standard tool for
Note: Fix any reported issues (like locked processes or insufficient space) before proceeding.
Step 2: Stop the Stack (Optional but Recommended for Non-Rolling)
While opatchauto handles the shutdown, in Non-Rolling mode, it is often safer and cleaner to manually stop the CRS stack on all nodes before invoking the patch to ensure a clean slate. Cause: You applied to the wrong Oracle home (e
# Run on ALL nodes as root
# crsctl stop crs -f
Step 3: Execute the Patch in Non-Rolling Mode
As the root user, run the apply command. The critical switch here is -nonrolling.
# Syntax:
# /opatchauto apply -nonrolling -silent
When executing opatchauto72030 execute in nonrolling mode, you may encounter: