Opatchauto72030 Execute In Nonrolling Mode (2024)

The patch does not require non‑rolling mode. Solution: Remove -nonrolling and let opatchauto decide, or force rolling with -rolling (not recommended against patch instructions).

To resolve this, you must explicitly use the flag. Benefits of Non-rolling Mode

Not all patches can be applied in rolling mode. Here are legitimate reasons why patch 72030 would require -nonrolling :

Non-rolling mode requires flawless, passwordless SSH connectivity for the root user across all cluster nodes. If SSH prompts for a password, opatchauto will fail immediately. opatchauto72030 execute in nonrolling mode

Depending on how far the previous session progressed, you can attempt to resume the failed session using the session ID found in your logs:

: Even in non-rolling mode, opatchauto automates the complex sequence of stopping services, applying binary patches, and restarting the stack across the cluster. Execution Requirements When running in non-rolling mode:

Unzip the new OPatch utility directly into both $GRID_HOME and $ORACLE_HOME . Verify the version as the software owner: $GRID_HOME/OPatch/opatch version Use code with caution. The patch does not require non‑rolling mode

fuser -v $GRID_HOME/bin/oracle fuser -v $ORACLE_HOME/bin/oracle Use code with caution. Step 4: Validate Inventory and SSH Equivalence

Search for the string 72030 or FATAL to identify the underlying command that failed (e.g., an internal ssh call or an opatch inventory check). Step 2: Update OPatch and OPatchAuto

Another context where this error can appear is in an Oracle Flex Cluster configuration. If your GI cluster is a flex setup, Oracle documentation specifies that the first and last node where opatchauto is executed must be Hub nodes and not Leaf nodes. If you are patching a Leaf node, you might encounter a similar error. Ensure you are running the patching session from an appropriate Hub node. Benefits of Non-rolling Mode Not all patches can

Once the patching is complete, start the cluster back up on all nodes: $GRID_HOME/bin/crsctl start crs Use code with caution. Step 5: Verify Patch Application Check that the patches have been applied correctly: $GRID_HOME/OPatch/opatch lsinventory Use code with caution. 4. Key Differences: Rolling vs. Non-Rolling Rolling Mode ( opatchauto ) Non-Rolling Mode ( -nonrolling ) Minimal (Zero) Significant (Full Cluster) Cluster Status Active (mixed version) Applicability General PSUs/RUs Specific patches/interims Default No (requires -nonrolling flag) 5. Troubleshooting Common Issues

While the exact command may vary by Oracle version, a realistic execution would look like this:

Once completed, use ./opatch lsinventory to confirm the patch is successfully applied across the homes. Key Differences: Rolling vs. Non-Rolling Non-Rolling upgrade in RAC using opatchauto - Oracle Forums

command in each Oracle Home to confirm the patch ID is successfully applied. Oracle Help Center a patch in non-rolling mode instead? 10 Troubleshooting OPatchAuto - Oracle Help Center

# As the root user from the GI_HOME/OPatch directory: ./opatchauto apply -nonrolling Use code with caution. Steps for Non-Rolling Patching: