If it’s stuck, you may need to check the input.json or state files in the OPatch/auto/core directory (though modifying these is for advanced users only). 3. Validate OPatch and OPatchAuto Versions
: All remote nodes must be shut down before starting a non-rolling session. opatchauto72030 execute in nonrolling mode
: Run the command to apply the patch in non-rolling mode. If it’s stuck, you may need to check the input
: If a failure occurs mid-way, you can often resume using: opatchauto resume : Run the command to apply the patch in non-rolling mode
To execute in non-rolling mode (specifically for patch ID 72030 or similar GI/Database RU updates), you are essentially instructing the utility to shut down all services across all nodes simultaneously, apply the patch, and then bring them back up.
: If opatchauto struggles to stop services, manually stop the stack using crsctl stop crs -f on all nodes before running the command with the -norestart flag (if you prefer manual control).
with the explicit non-rolling flag: