If you want, I can turn this into a runnable step-by-step runbook tailored to your Oracle version and environment (RAC vs single-instance).
However, if your Cluster Ready Services (CRS/Grid) home is built on a shared file system (such as ACFS, OCFS2, or a shared NFS/SAN appliance):
Before applying the patch binaries, cleanly shut down your database instances and the target Grid Infrastructure stack on all remote nodes. opatchauto72030 execute in nonrolling mode exclusive
A previous opatchauto session aborted unexpectedly (due to a timeout, manual cancellation, or a syntax error), leaving behind locking files in the GI_HOME or ORACLE_HOME .patch_storage directory.
The found inside your clsrscres.log or rootcrs log file. Share public link If you want, I can turn this into
Search for the specific command_id mentioned in the trace. Look for underlying javacore errors or "Permission denied" strings. 2. Verify Stack State
$GRID_HOME/crs/install/clsrsc.sh -postpatch -nonrolling -exclusive Use code with caution. The found inside your clsrscres
If the previous rolling attempt left a partial session, opatchauto might try to resume in rolling mode. You may need to update the session configuration file located in $GRID_HOME/OPatch/auto/dbsessioninfo/ . Open the JSON file for the failed session ID.
Explicitly stop the Grid Infrastructure stacks on all remote cluster nodes ( ) to satisfy non-rolling parameters: