No. If Oracle marks a patch as “non-rolling,” the binary change is incompatible with a rolling strategy. Ignoring this leads to cluster crashes.
The patch README for bug 72030 may state: "This patch is not rolling installable. Use -nonrolling flag."
This distinction is the heart of our keyword. opatchauto72030 execute in nonrolling mode
| 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 |
The command opatchauto72030 execute in nonrolling mode explicitly forces a non-rolling strategy for patch 72030. | Step | Command | |-------|----------| | Verify
| Step | Command |
|-------|----------|
| Verify cluster resources | crsctl stat res -t -init |
| Check database registry | sqlplus / as sysdba → select version, status from dba_registry; |
| Run datapatch (if DB home patched) | cd $ORACLE_HOME/OPatch; ./datapatch -verbose |
| Relink applications (optional) | $ORACLE_HOME/bin/relink all |
To minimize risk when using opatchauto -nonrolling: Not all patches can be applied in rolling mode
Not all patches can be applied in rolling mode. Here are legitimate reasons why patch 72030 would require -nonrolling: