# As the root operating system user on Node 2 (and subsequent nodes) /u01/app/19.0.0/grid/bin/crsctl stop crs -f Use code with caution. Step 4: Run the Analyzer Validation Tool
In some scenarios, even if the storage layer is non-shared, opatchauto may throw an execution mode error due to a breakdown in automated inventory discovery. If node verification tools like cluvfy comp nodecon fail to query remote node topologies or if SSH connectivity details are broken (often linked to Oracle Bug 29529394 / INS-06005), the utility falls back to an "exclusive/non-rolling" assumption for safety. The Architecture of Non-Rolling Patching opatchauto72030 execute in nonrolling mode exclusive
However, if your Cluster Ready Services (CRS/Grid) home is built on a shared file system (such as ACFS, OCFS2, or a shared NFS/SAN appliance): # As the root operating system user on