opatchauto apply /u01/app/stage/34774103 -nonrolling
This distinction is the heart of our keyword.
| Feature | Rolling Mode (Default) | Non-Rolling Mode |
|---------|------------------------|------------------|
| Downtime | Near-zero (services fail over) | Full cluster downtime required |
| Process | Patches nodes one at a time | Patches all nodes simultaneously |
| Application continuity | Preserved for running sessions (with drain timeout) | All sessions are terminated |
| When to use | Most routine patches | Patches that modify ASM instances, OCR, or voting disks; rolling-incompatible patches |
| Command flag | No flag (or -rolling) | -nonrolling | opatchauto72030 execute in nonrolling mode
The command opatchauto72030 execute in nonrolling mode explicitly forces a non-rolling strategy for patch 72030. opatchauto apply /u01/app/stage/34774103 -nonrolling
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. This distinction is the heart of our keyword
In non‑rolling mode, the utility will stop the entire stack, but you can also pre‑stop:
# As grid user, on each node
crsctl stop cluster -all
Wait for crsctl status resource -t to show nothing running.
Even with a perfect plan, issues arise. Here are errors tied to non‑rolling mode with opatchauto:
Agree