This dry-run reports any conflicts or issues.
OPATCHAUTO-72030: Execution mode invalid. Cannot execute in rolling mode... Execute in non-rolling mode. Why Non-Rolling Mode is Required
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.
The "exclusive" nature of this error meant there was no middle ground. To move forward, the cluster's heartbeat had to stop entirely.
External processes (like monitoring agents or backup software) locking files in the Oracle Home. Step-by-Step Troubleshooting 1. Check the Log Files opatchauto72030 execute in nonrolling mode exclusive
For an analysis-only run to verify applicability, add the -analyze flag:
The utility will handle stopping the local stack, applying the binary patch to the shared home, and restarting the services.
Before executing any exclusive patching operations, verify your current OPatch and OPatchAuto versions. Outdated patching utilities frequently misinterpret patch metadata. Log in as the grid user and check the OPatch version: $ORACLE_HOME/OPatch/opatch version Use code with caution.
Non-rolling patches require downtime. Schedule this during a maintenance window to avoid business disruption. This dry-run reports any conflicts or issues
Monitor the apply:
# As root /u01/app/19.0.0/grid/OPatch/opatchauto apply /path/to/patch/35319490 -nonrolling Use code with caution.
Once Node 1 returns a successful execution message, log in to as root . Execute the identical command:
Review the generated log file to confirm that all system space requirements and OS privileges pass verification. Step 3: Execute OPatchAuto with the -nonrolling Flag Execute in non-rolling mode
Non-rolling mode is typically used when a patch affects the Oracle Clusterware itself, when patching a shared CRS home, or when the patch metadata mandates it. In a non-rolling patching session, all nodes (both local and remote) must be down or stopped before patching begins. The process involves patching the first node, then nodes 2 through n-1, and finally the last node. This mode results in full cluster downtime during the patching window.
Before executing the command, the following must be validated to prevent failure mid-outage:
It runs post-patching configuration tools ( rootcrs.sh or rootcrs.pl ). It restarts the local Oracle Clusterware stack. Step 4: Serial Processing of Remaining Nodes