cd /tmp
$GRID_HOME/OPatch/opatch lsinventory
/u01/app/19.0.0/grid/OPatch/opatchauto apply /images/patches/36123456 -nonrolling -local Use code with caution. Step 4: Verify the Patch Application opatchauto72030 execute in nonrolling mode high quality
To resolve this and ensure a high-quality patch application, you must switch to , which requires specific procedural steps to maintain environment stability. 1. Root Causes of OPATCHAUTO-72030 cd /tmp $GRID_HOME/OPatch/opatch lsinventory /u01/app/19
Beginning with Oracle 12c, non-rolling patching requires the GI stack to be up on the local node when the command is invoked. However, the patching process itself involves shutting down all Oracle services as it progresses through each node. Some documentation states "all nodes (including the local node) must be stopped" because the automated process will handle the shutdown as part of its orchestration. Root Causes of OPATCHAUTO-72030 Beginning with Oracle 12c,
Once the cluster is stable, start your databases if they are not configured to auto-start: # As oracle user srvctl start database -d ORCL Use code with caution. Troubleshooting Ongoing Non-Rolling Failures
Shared CRS home configurations, patches that are not rollable, environments where scheduled downtime is acceptable, GI home patching.