Opatchauto-72030 Execute In Non-rolling Mode Apr 2026

Leo typed:

He closed the terminal, finished his cold coffee, and wrote the post-mortem email subject line before sleep took him:

“All green.”

“Why we ran opatchauto-72030 in non-rolling mode—and why I’d do it again.” opatchauto-72030 execute in non-rolling mode

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]

But opatchauto had just vetoed that.

But the exploit was already being scanned for in the wild. Twelve hours ago, a probe hit their edge firewall. No intrusion, but the signature matched CVE-2026-4100. Someone was looking for an open door. Leo typed: He closed the terminal, finished his

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

“I know what it means.”

“You seeing this?” Maya’s voice crackled over the headset. [y/n] But opatchauto had just vetoed that

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.

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

The tool paused for three seconds—long enough for him to second-guess everything—then spat back: