The process will output logs to: $ORACLE_HOME/cfgtoollogs/opatchauto/core/opatch/opatch<timestamp>.log
What is your current (e.g., 19c, 21c)?
$GI_HOME/OPatch/opatchauto apply <PATCH_LOCATION> -analyze -nonrolling opatchauto72030 execute in nonrolling mode high quality
: Some patches contain metadata explicitly stating they cannot be applied while other nodes are active.
When OPatchAuto runs in rolling mode, it patches nodes one at a time while other nodes continue serving requests: If you see this in your logs: If
: Alex re-ran the command, but this time added the critical flag: # opatchauto apply /u01/app/oracle/patches/35319490 -nonrolling Success and Verification
: These errors occur when the cluster cannot be set to rolling patch mode. If you see this in your logs: Oracle strongly recommends backing up all Oracle homes
If opatchauto encounters an issue, it will point to a specific log file path within /cfgtoollogs/opatchauto/ . Keep a terminal window open to monitor progress:
The analyze option simulates a full patch application session by running all prerequisite checks without making any changes to the system—neither binaries nor configurations.
Use the explicit non-rolling syntax to bypass the automated rolling orchestration logic that might be failing.
Oracle strongly recommends backing up all Oracle homes before any patch operation. Use your organization's preferred backup method for Oracle home directories.