Navigate to your global OPatch storage directory to view the high-level orchestration log: cd $ORACLE_HOME/cfgtoollogs/opatchauto/ ls -lrt Use code with caution.
: On all nodes, stop the Oracle Clusterware stack as the root user: # /bin/crsctl stop crs Use code with caution. Copied to clipboard Run OPatchAuto in Non-Rolling Mode : Execute the apply command with the -nonrolling flag from the local node:
Always download the latest OPatch utility from My Oracle Support (MOS) and replace the existing OPatch directory in both the Grid Infrastructure Home and Database Home before retrying.
The most frequent reasons for encountering this specific execution error include: opatchauto72030 execute in nonrolling mode exclusive
When this error triggers, it effectively acts as a safety mechanism to prevent system corruption that would occur if you tried to patch a shared home while other nodes were still using it. Detection Accuracy:
Run the command from the first node. The -exclusive flag ensures the GI stack is managed correctly during the downtime.
The "exclusive" option in non-rolling mode ensures that the patch is applied exclusively to the specified instance, without affecting other instances in a multi-instance environment. This option is particularly useful in RAC (Real Application Clusters) environments where multiple instances of the database are running. Navigate to your global OPatch storage directory to
Ensure you have the latest OPatch utility installed in both GI and Database homes. Backup: Always back up your Oracle Home before proceeding.
Start by patching a single node, then patch the remaining nodes in parallel, and finish with the final node to complete the session.
When you start a non-rolling mode session, (the local node must be up). OPatchAuto then patches nodes, typically in a sequence: The most frequent reasons for encountering this specific
# Execute the live update using elevated root permissions /u01/app/19.0.0/grid/OPatch/opatchauto apply /soft/35319490 -nonrolling Use code with caution.
Use opatch lspatches to confirm that the patch was applied correctly after the restart.
The central inventory ( oraInventory ) across cluster nodes is out of sync, causing opatchauto to misidentify which nodes are currently running the software versions being updated. Step-by-Step Troubleshooting and Resolution