typically patches the local node first, then requires you to run it on subsequent nodes (or it handles them if remote access is configured). Finalize with Datapatch
: If your GI home is on shared storage (e.g., ACFS or shared disks), rolling patching is not possible because updating the binaries on one node would affect the running processes on others. Non-Rollable Patches opatchauto72030 execute in nonrolling mode high quality
In a shared home environment, the software binaries are physically located on a shared disk rather than individual local disks for each node. Because patching these binaries affects all nodes simultaneously, a standard "rolling" update—where one node stays up while another is patched—is technically impossible. typically patches the local node first, then requires
To ensure high quality and minimize risks when executing opatchauto in non-rolling mode, follow these best practices: follow these best practices: