Opatchauto-72030 Execute In Non-rolling Mode -

Logs scrolled:

Twenty-two minutes later, node0 was back. Then node1. Then node2. Services re-registered. Connections trickled back. opatchauto-72030 execute in non-rolling mode

The entire cluster would go down. All nodes. At once. Patch applied to the Oracle home while the databases were offline. Then a full restart. It was the nuclear option—sledgehammer surgery. Logs scrolled: Twenty-two minutes later, node0 was back

“Why we ran opatchauto-72030 in non-rolling mode—and why I’d do it again.” Logs scrolled: Twenty-two minutes later

The patch was critical. CVE-2026-4100. A buffer overflow in the interconnect fabric that allowed a compromised container to read host memory. The security team had stamped it in red ink that bled through three pages of compliance forms.

“Non-rolling means—”

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