When applying a patch using the -nonrolling flag, the orchestration flow changes completely. Prior to Oracle 12c, a non-rolling patch required every single piece of infrastructure to be completely dark before modifying binaries. Modern iterations of opatchauto (12c through 19c and up to Oracle 26) use a structured, multi-phase method to maintain local tracking: Sequence Phase Target Scope Active Status Requirement Local Node (where command is typed)
Note: If targeting specific homes across complex environments, append the explicit target directory using the -oh argument to establish rigid deployment bounds. Important Operational Rules Doc ID 2957442.1 OPATCHAUTO-72030 During Opatchauto opatchauto72030 execute in nonrolling mode exclusive
OPATCHAUTO-72030: Execution mode invalid. OPATCHAUTO-72030: Cannot execute in rolling mode, as CRS home is shared. OPATCHAUTO-72030: Execute in non-rolling mode. OPatchAuto failed. Root Cause of the Error When applying a patch using the -nonrolling flag,
Step 4: Manual Exclusive Rollback/Roll-forward (The Fallback Method) Important Operational Rules Doc ID 2957442
# Execute on the local node where you run OPatchAuto /u01/app/19.0.0/grid/bin/crsctl check crs Use code with caution. Step 3: Run the OPatchAuto Command with the Correct Flag
This error occurs when OPatchAuto is invoked in its default mode but detects that it cannot be used. The key phrase is "CRS home is shared." But what does that mean?