Once the cluster is stable, start your databases if they are not configured to auto-start: # As oracle user srvctl start database -d ORCL Use code with caution. Troubleshooting Ongoing Non-Rolling Failures
Locked Files: Sometimes a lingering process holds a file in the GI_HOME. Use 'fuser' or 'lsof' to identify and kill these processes.
sqlplus / as sysdba <<EOF select patch_id, status from dba_registry_sqlpatch; EOF
Patching is a critical maintenance task. By adhering to these best practices, you ensure high quality, minimal risk, and a smooth operation for your Oracle RAC environment.
Stale metadata from failed attempts can corrupt subsequent executions. Clear the central inventory locks and the opatchauto storage cache: opatchauto72030 execute in nonrolling mode high quality
Mastering OPatchAuto Error 72030: How to Execute Patching in Non-Rolling Mode
srvctl config database -d <db_name> srvctl modify database -d <db_name> -o <new_ORACLE_HOME>
# As oracle user: Stop databases srvctl stop database -d # As root user: Stop Grid Infrastructure /bin/crsctl stop crs -f Use code with caution. 2. Execute OPatchAuto with the Non-Rolling Flag
If the patch involves conflict resolution—where patch 72030 must merge with or replace existing patches—the administrator must ensure that the calculated sub-patch list is correct. In non-rolling mode, there is no "partial success" state where some nodes are patched and others are not; the operation must succeed universally. Therefore, high-quality execution involves anticipating prompts, ensuring appropriate user privileges (typically root), and managing the storage repositories effectively to prevent time-outs during the copy phase. Once the cluster is stable, start your databases
For environments where high availability is a strict requirement (e.g., development, test, or single-instance production), executing opatchauto in non-rolling mode with the specific qualifier 72030 (often referencing a patch ID or a specific bundle scenario) offers distinct advantages in speed and simplicity.
# As oracle / grid user srvctl stop database -d ORCL # As root user /u01/app/19.0.0/grid/bin/crsctl stop crs Use code with caution.
Resolving OPATCHAUTO-72030: Executing opatchauto in Non-Rolling Mode
# 1. Set environment variables export PATH=$PATH:<GI_HOME>/OPatch export ORACLE_HOME=<GI_HOME> sqlplus / as sysdba <<EOF select patch_id, status
$GI_HOME/OPatch/opatchauto apply /path/to/unzipped/patch \ -oh /u01/app/19.0.0/grid \ -nonrolling \ -ocmrf /tmp/ocm.rsp \ -logLevel CONFIG \ -log /custom/log/path/opatchauto.log
For high-quality patch execution, Oracle administrators should:
October 2024 Audience: Oracle Database Administrators, System Architects, Middleware Specialists