Change "key" : "nonrolling", "value" : "false" to "key" : "nonrolling", "value" : "true" . Run: opatchauto resume -session . 4. Best Practices for Non-Rolling Patches
To fix this, you must explicitly instruct the patch utility to run in combined with an exclusive cluster state.
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)
Start by patching a single node, then patch the remaining nodes in parallel, and finish with the final node to complete the session.
Run OPatchAUTO in nonrolling mode:
Disables the node-by-node automated sequencing. It treats the target operations as an isolated, standalone event on that specific host.
The resulting output will look like this:
Some patches contain changes that are incompatible with running mixed versions across a cluster simultaneously. Execution Workflow (Non-Rolling Mode)
The error is a sign that the automated "Exclusive" lock required for a non-rolling patch cannot be safely established. By checking the deep logs and verifying that the GI stack can be stopped manually, you can usually bypass the automation hurdle and successfully update your environment. opatchauto72030 execute in nonrolling mode exclusive
Error 72030 indicates a . It specifically means:
If a session is active, you may need to use the -resume or -rollback command to clear the state before trying the non-rolling execution again. Verify Clusterware State
: If your patch bundle permits, decouple the Grid Infrastructure patching from the Database patching to isolate infrastructure issues from database workloads.
Understanding the OPatchAuto-72030 Error in Exclusive Non-Rolling Mode Change "key" : "nonrolling", "value" : "false" to
This article explains what "execute in nonrolling mode exclusive" means, why OPatchAUTO72030 appears, implications for availability, prerequisites, step-by-step handling, troubleshooting, and best practices.
Running in non-rolling mode is an efficient and reliable way to handle complex Oracle Grid Infrastructure (GI) or RAC environments, especially when dealing with shared homes or non-rollable patches. This mode ensures full consistency across the stack by updating multiple components in parallel while they are offline, which significantly reduces the total maintenance window compared to sequential rolling updates.
Note that the -nonrolling option is generally not supported for "out-of-place" patching (using -outofplace ), where a new home is cloned.
If your diagnostic logs indicate that the binary patching phase succeeded but the cluster configuration failed to restart or finish its post-patch tasks, follow this sequence to recover. Step 1: Clean Up Failed Cluster States Best Practices for Non-Rolling Patches To fix this,
The term "exclusive" in this context usually refers to an or state required for patching shared binaries. Rocky Linux release 8.8 19c rac ru安装 - 墨天轮
A: As shown in the logs, when opatchauto fails (e.g., with the 72030 error), it often returns with error code 42 .