Check the opatchauto log. Usually, you can fix the issue (e.g., free space, missing RPM) and re‑run the same command. opatchauto is idempotent.
crsctl start cluster -all Then verify resource status: opatchauto72030 execute in nonrolling mode high quality
OPatchAuto session completed successfully. Patch applied in non‑rolling mode. Logs are written to: $ORACLE_HOME/cfgtoollogs/opatchauto/opatchauto_<timestamp>.log Check the opatchauto log
crsctl stop cluster -all Wait for all nodes to show CRS is down via: crsctl start cluster -all Then verify resource status:
Always remember: Embrace its structure, respect its downtime, and execute with precision. For further reading, consult Oracle Support Document 244241.1 (Opatchauto FAQ) and the specific README for your patch ID.
Your command will be:
Yes, use ‑analyze flag: opatchauto apply . -nonrolling -analyze Conclusion The command opatchauto72030 execute in nonrolling mode is more than a routine maintenance task—it is a surgical operation on Oracle Grid Infrastructure. By understanding when and why to use non‑rolling mode, and adhering to high‑quality best practices (validation, backup, monitoring, and post‑validation), you transform a risky patching window into a predictable, successful maintenance event.