The patch README for bug 72030 may state: "This patch is not rolling installable. Use -nonrolling flag."
To execute successfully in this mode, specific node availability conditions must be met: opatchauto72030 execute in nonrolling mode
When this error occurs, opatchauto explicitly requires the -nonrolling flag to proceed. Non-rolling mode means that the entire stack (GI and Database) will be offline simultaneously across the cluster, rather than being patched one node at a time. Key Requirements for Non-Rolling Mode The patch README for bug 72030 may state:
# opatchauto apply -oh -nonrolling Use code with caution. Copied to clipboard Analyze Mode (Dry Run): Key Requirements for Non-Rolling Mode # opatchauto apply
| Step | Command | |-------|----------| | Verify cluster resources | crsctl stat res -t -init | | Check database registry | sqlplus / as sysdba → select version, status from dba_registry; | | Run datapatch (if DB home patched) | cd $ORACLE_HOME/OPatch; ./datapatch -verbose | | Relink applications (optional) | $ORACLE_HOME/bin/relink all |