Opatchauto72030 Execute In Nonrolling Mode | Exclusive
Driver modules (like ACFS, AFD, or OHASD) failing to unload or load cleanly.
By default, opatchauto tries to orchestrate patches using a topology. In a rolling strategy, Node 1 is shut down and patched, while Node 2 continues serving production traffic. Once Node 1 is online, the process moves to Node 2.
Modifying the binaries on Node 1 instantaneously modifies the active binaries underlying the active stack on Node 2.
Note: The -nonrolling parameter tells opatchauto to manage the exclusive locking required for the shared file system. 4. Monitor the Patch Session
The most detailed data lives in the Grid Infrastructure alert and trace directories. Check the automated script log: