Skip To Main Content

Breadcrumb

Sticky Header Banner

This is the command that triggers the outage and patching.

# As root user
/opatchauto apply /path/to/72030 -nonrolling -oh /u01/app/grid_home

(Note: If -oh is omitted, opatchauto attempts to patch all detected homes. Specifying -nonrolling is the critical flag here.)

This is the specific Oracle patch number. In this case, Oracle Patch 72030 is a hypothetical placeholder (though actual patches follow this numeric format). In real-world scenarios, this would be a known Release Update (e.g., RU 19.20.0.0.0) or a One-off patch addressing a specific bug. The number informs opatchauto which set of instructions (*.xml metadata) to follow.

opatchauto apply /patch/72030 -analyze

This dry-run reports any conflicts or issues.

Before you run opatchauto72030 execute in nonrolling mode exclusive, your checklist must be exhaustive.

  • Verify the patch README: Some patches force non‑rolling exclusive because of underlying binary or schema changes.
  • This flag modifies the behavior of the patching session. When you use exclusive in conjunction with opatchauto execute:

    opatchauto is an intelligent wrapper around OPatch that automates patching for Oracle homes. It determines the current cluster state, stops/restarts services as needed, and applies patches consistently across nodes.