to use non-rolling mode. Navigate to your patch directory and run the following as # Example syntax for 12c or 19c
If Node 1 fails mid-way through a non-rolling execution, do not restart the entire process from scratch.
Repeat this process sequentially for any subsequent nodes in the cluster topology. opatchauto72030 execute in nonrolling mode exclusive
Look for specific errors like CRS-1158: Clusterware cannot be started as exclusive or ACFS-9459: Failed to unload drivers .
Running a rolling patch on a shared home will cause sudden, uncoordinated binary corruption and node evictions across active cluster hosts. to use non-rolling mode
cat $GRID_HOME/cfgtoollogs/crsconfig/clsrscres.log cat $GRID_HOME/cfgtoollogs/crsconfig/rootcrs_ .log Use code with caution.
# Execute on the local node where you run OPatchAuto /u01/app/19.0.0/grid/bin/crsctl check crs Use code with caution. Step 3: Run the OPatchAuto Command with the Correct Flag Look for specific errors like CRS-1158: Clusterware cannot
Ensure that the Grid Infrastructure cluster stack is operational on the primary local deployment node (e.g., Node 1). For non-rolling patches, the local node infrastructure must remain active initially to let the installer query parameters from the local cluster registry. Step 3: Bring Down Remote Targets
While the primary keyword focuses on simply adding the -nonrolling flag, advanced users in a clustered environment may need to ensure execution. Exclusive execution refers to situations where you must patch the GI home separately from the Database home, or vice versa, without interference.