Execute In Non-rolling Mode - Opatchauto-72030

But the cluster was live. Four thousand active sessions. Three replicas of the order-processing database. If he ran the patch in , nodes would update one by one—seamless, safe, standard.

He pulled up the change request dashboard. His eyes skimmed over the numbers: active transactions, replication lag, customer SLAs. If he did this now, the order system would vanish for at least forty-five minutes. The on-call manager would scream. The VP of Engineering would ask why he hadn’t scheduled a maintenance window.

Log Entry: opatchauto-72030 execute in non-rolling mode Time: 02:13:47 UTC Host: dg-cr1-node0 User: oracle opatchauto-72030 execute in non-rolling mode

opatchauto apply /u01/storage/patch_4100 -nonrolling

OPatchAuto succeeded in non-rolling mode. But the cluster was live

The first node went dark. Then the second. Then the third.

Stopping CRS on node0... Stopping CRS on node1... Stopping CRS on node2... Applying patch to Oracle home... Patch 34567890 applied to node0 (1 of 3) Starting CRS on node0... If he ran the patch in , nodes

Here’s a short technical-fictional story based on that log line. The Non-Rolling Mode

“Non-rolling means—”

This operation will patch all nodes in non-rolling mode. Database services on all instances will be interrupted until patching completes on all nodes. Proceed? [y/n]