Never cancel an opatchauto session mid-execution using Ctrl+C or kill -9 unless absolutely necessary. If a freeze occurs, allow the built-in timeouts to trigger so the utility can run its cleanup routines.
The "nonrolling mode exclusive" execution is the standard requirement for these environments to ensure the shared binaries are modified while the entire stack is down.
The opatchauto utility is the next-generation patching tool for Oracle Grid Infrastructure and RAC databases. Unlike the legacy opatch (which patches a single Oracle home), opatchauto understands cluster topologies. It can patch both the Grid home (CRS/ASM) and all database homes across all nodes in a cluster. opatchauto72030 execute in nonrolling mode exclusive
When a patch requires "exclusive" non-rolling execution, opatchauto must be the sole automation process managing the lifecycle of the stack. If it detects left-over metadata from a previous failed patch, or if it finds GI active on a peer node where it expects it to be down, it triggers the 72030 roadblock to prevent binary corruption or cluster split-brain scenarios. Common Root Causes
If processes refuse to die, gracefully terminate them using kill -9 for processes like ohasd.bin , ocssd.bin , or crsd.bin . Step 2: Unlock the Grid Home (If Required) The opatchauto utility is the next-generation patching tool
Underlying OS architecture libraries missing during the standard make phase of execution. Why "Non-Rolling Mode Exclusive"?
The error typically occurs during Oracle Grid Infrastructure (GI) patching when the system is unable to proceed in "rolling" mode (where nodes are patched one by one without total cluster downtime). This message indicates that a non-rolling mode execution is required, often due to a shared home configuration or specific patch requirements. Understanding Error OPATCHAUTO-72030 or crsd.bin .
# As grid user on Node 1 cluvfy comp software -n all -verbose