Opatchauto-72030 Execute In Non-rolling Mode Apr 2026

He pressed y .

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.

“Yeah,” Leo said. “72030.”

Leo leaned back. The chair squeaked. He didn't need the docs to know what came next. opatchauto-72030 execute in non-rolling mode

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...

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

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 pressed y

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.

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]

Leo typed:

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

Twenty-two minutes later, node0 was back. Then node1. Then node2. Services re-registered. Connections trickled back.

OPatchAuto succeeded in non-rolling mode. No intrusion, but the signature matched CVE-2026-4100

Leo exhaled. Maya pinged: “All green?”

But opatchauto had just vetoed that.