Opatchauto72030 Execute In Nonrolling Mode -

To execute OPatchAuto (patch 72030) in non-rolling mode, you must use the -nonrolling flag. This mode applies the patch to all nodes in the cluster simultaneously, which requires downtime as all services must be stopped across the cluster. Prerequisites

Verification Failed: If the command fails, check the logs located in /cfgtoollogs/opatchauto/. opatchauto72030 execute in nonrolling mode

Error 3: “Cannot apply in non‑rolling mode because database instances are running”

Cause: opatchauto detected live instances it cannot shut down.
Solution: Manually stop all DB instances using srvctl stop instance and retry. To execute OPatchAuto (patch 72030) in non-rolling mode

Key capabilities:

/OPatch/opatch lsinventory /OPatch/opatch lsinventory Use code with caution. Copied to clipboard Why use Non-Rolling Mode? Schedule a maintenance window – Communicate full outage

  1. Schedule a maintenance window – Communicate full outage clearly.
  2. Test in a staging cluster – Clone production if possible.
  3. Take a full Grid home backup – Tar the GI_HOME directory.
  4. Backup OCR & voting disks – ocrconfig -manualbackup, crsctl query css votedisk.
  5. Run opatchauto analyze first – It detects issues before action.
  6. Disable any external monitoring – Nagios, OEM, etc., to avoid false alerts.
  7. Increase _CRS_STACK_TIMEOUT – Prevents premature node fencing during patching.
  8. Log everything – opatchauto apply ... -logDir /tmp/patch72030_logs
  9. Have a rollback plan – Keep the old home mounted and ready.
  10. After success, run cluvfy – cluvfy comp software to validate cluster health.

Replace <patch_directory> with the path where you extracted the patch.

Step 3: Execute the Patch in Non-Rolling Mode As the root user, run the apply command. The critical switch here is -nonrolling.