Opatchauto72030 Execute In Nonrolling Mode High Quality Portable 【2025】

Overview

opatchauto72030 is an Oracle OPatch utility bundle used to apply OPatch patches and one-off fixes to Oracle Grid Infrastructure and database homes. Running opatchauto72030 in nonrolling mode with the HIGH quality level ensures coordinated downtime and a conservative, fully synchronized patch application across all nodes—minimizing risk and maximizing consistency for environments where rolling updates are not appropriate.

Anatomy of the Command

A typical execution command looks like:

opatchauto apply /path/to/patch/72030 -nonrolling

Or, if 72030 is an Oracle home label:

opatchauto apply /u01/app/oracle/product/19.0.0/dbhome_1 -nonrolling

Key parameters:

1. Prerequisites & Preparation

Before beginning, ensure all prerequisites are met to avoid a failed patching session. opatchauto72030 execute in nonrolling mode high quality

  1. Download Files:

    • Download p36182763_190000_Linux-x86-64.zip.
    • Download the latest OJVM patch (e.g., p36233258_190000_Linux-x86-64.zip) if required for database homes.
    • Download the latest OPatch version (Required: 12.2.0.1.43 or later).

  2. Validate OPatch Version: Replace the existing OPatch in both GI and DB homes.

    # Example for GI Home
unzip -o p6880880_190000_Linux-x86-64.zip -d /u01/app/19.0.0/grid/
chown -R grid:oinstall /u01/app/19.0.0/grid/OPatch
chmod -R 775 /u01/app/19.0.0/grid/OPatch

  3. Conflict Check: Unzip the patch and check for conflicts.

    # As grid user
$ORACLE_HOME/OPatch/opatch prereq CheckConflictAgainstOHWithDetail -phBaseDir ./36182763/36215643 -oh $ORACLE_HOME

  4. Root Script Automation (Optional but Recommended): Ensure the /etc/oraInst.loc file is correctly configured. Overview opatchauto72030 is an Oracle OPatch utility bundle

Run database health check

sqlplus / as sysdba <<EOF select patch_id, status from dba_registry_sqlpatch; EOF

Step 1: Stop All Clusterware Resources

In non‑rolling mode, you must shut down the entire cluster cleanly:

crsctl stop cluster -all

Wait for all nodes to show CRS is down via:

crsctl check crs

3. Command Syntax for Non-Rolling Mode

# For Oracle Grid Infrastructure home (RAC or standalone)
$ORACLE_HOME/OPatch/opatchauto apply <patch_location> -nonrolling

Frequently Asked Questions


Q1: Can I interrupt opatchauto in non‑rolling mode?

No. Interrupting can leave the cluster in a mixed‑state. Always let it complete or use opatchauto resume if supported. Or, if 72030 is an Oracle home label:


Q2: Does non‑rolling mode affect ASM disk groups?

Yes, ASM instances on all nodes are stopped and restarted together. Ensure no databases rely on ASM during the window.


Q3: How do I handle failures during execution?

Check the opatchauto log. Usually, you can fix the issue (e.g., free space, missing RPM) and re‑run the same command. opatchauto is idempotent.


Q4: Is there a way to simulate non‑rolling mode?

Yes, use ‑analyze flag:

opatchauto apply . -nonrolling -analyze


Validate database if applicable


sqlplus "/as sysdba" <<EOF
select PATCH_ID, STATUS from registry$sqlpatch;
EOF

Pages