, you cannot use rolling mode because updating the binaries on one node would immediately affect all other nodes, potentially crashing the active stack. Oracle Help Center Execution Guide for Non-Rolling Mode
Oracle strongly recommends performing database maintenance using a with an out‑of‑place patching strategy. This approach simplifies maintenance and avoids potential conflicts that arise from patching a live home. opatchauto72030 execute in nonrolling mode high quality
However, note: in public documentation. You may mean a specific interim patch number or have a typo. I'll provide the generic high-quality procedure for opatchauto in non-rolling mode for a RAC cluster or standalone. , you cannot use rolling mode because updating
In non-rolling operations, opatchauto must query and update the cluster state. If the GIMR or the Oracle Cluster Registry (OCR) contains stale configuration data from a previous failed patching attempt, or if the repository cannot be accessed in exclusive mode, the session throws Error 72030. 3. SSH Passwordless Connectivity Failures However, note: in public documentation
Incorrect Patch Path: Ensure you are pointing to the top-level directory of the unzipped patch, not a specific sub-patch folder.
Stale metadata from failed attempts can corrupt subsequent executions. Clear the central inventory locks and the opatchauto storage cache: