| Feature | Rolling Mode (Default) | Non‑Rolling Mode | |---------|------------------------|------------------| | | One node at a time. | All nodes simultaneously. | | Cluster availability | Cluster remains available (though services move). | Cluster is fully down during patching. | | Downtime required | Minimal per node; overall longer patching time. | Single, longer downtime window. | | Failure risk | Lower; if one node fails, others still run. | Higher; any failure affects whole cluster. | | Use case | Most RAC patches, online patching. | Non‑RAC (standalone), or when rolling mode is not allowed by patch notes. |
: Ensure the Oracle Inventory is consistent across all nodes. opatchauto72030 execute in nonrolling mode
If you are running this (e.g., ACFS or NFS), ensure the patch location is accessible on all nodes, or copy the patch directory to each node and run opatchauto locally with the -local flag in addition to -nonrolling . | Feature | Rolling Mode (Default) | Non‑Rolling
Ensure you are using the latest version of the OPatch utility. Download the latest OPatch from My Oracle Support (MOS). | Cluster is fully down during patching
: Ensure the clusterware and database stacks are stopped on all nodes except the one where you are running opatchauto Run Command : Execute the utility as the user using the following syntax:
The keyword opatchauto72030 execute in nonrolling mode implies that patch 72030 a full cluster outage.