: In a non-rolling session, OPatchAuto typically follows three phases: Phase 1 : Patch the local node (Node 1). Phase 2 : Patch remote nodes (Nodes 2 through ) in parallel. Phase 3 : Patch the final node ( ) to complete the session. Key Takeaways
Alex knew the drill. Usually, patching was a "rolling" affair—a graceful relay race where one node in the cluster goes down for maintenance while the others carry the workload. But this patch was different. It touched the very heart of the shared Grid Infrastructure (GI) Home opatchauto72030 execute in nonrolling mode exclusive
/u01/app/grid/OPatch/opatchauto apply /path/to/patch -oh /u01/app/grid -nonrolling Use code with caution. Copied to clipboard Always ensure you are using the latest OPatch utility (Patch 6880880) before starting. 3. Common Troubleshooting Tweaks : In a non-rolling session, OPatchAuto typically follows
# As grid user on Node 1 cluvfy comp software -n all -verbose Key Takeaways Alex knew the drill
The failure message indicates that the orchestration engine cannot proceed in the default "rolling" mode (patching one node at a time while others stay up).
If your Grid Infrastructure home is shared across nodes, binaries cannot be updated on one node while the other is still running from the same disk.