ORACLE DATABASE ADMINISTRATION

Patching Oracle Grid Infrastructure and Database to Release 23.26.3 with OPatchAuto

Munish Kumar Karna

Senior Database Solution Architect | Oracle Certified Professional | RAC · ASM · Data Guard · GoldenGate · OCI

Overview

This walkthrough documents an end-to-end Release Update of a 2-node Oracle RAC environment (Grid Infrastructure and Database homes) from 23.26.2 to 23.26.3, applied using OPatchAuto — Oracle's automated, orchestrated patching utility for Oracle Home environments. Alongside the patch apply itself, this write-up also covers three things that are often skipped in patching notes but matter in real operations: how OPatchAuto discovers which Oracle Homes exist on a node, how to run a non-invasive prerequisite check before committing to a patch window, and how Datapatch registers (and reverses) SQL-level changes in the database dictionary.

All command output and screenshots below are captured directly from the patching session (apply on both nodes, verification, and a rollback exercise for validation purposes), reformatted here for readability.

Environment Snapshot

• Cluster: 2-node Oracle RAC — racnode1 and racnode2

• Grid Infrastructure home: /u01/app/26.0.0/grid1

• Database home: /u01/app/oracle/product/26.0.0/dbhome_2

• Patch: 39568945 — Release Update 23.26.3.0.0 (from 23.26.2.0.0 Gold Image baseline)

• Tool: Oracle OPatchAuto, version 12.2.1.51.0

• Patching mode: in-place, rolling (node by node)

1. Command Reference — opatchauto apply -help

Before patching, it's worth revisiting what opatchauto apply actually exposes. The options below govern everything from home selection and logging to conflict handling, out-of-place cloning, and SQL-patch behavior — the switches that decide how controlled (or how aggressive) a patching run will be.

Option	What it does
-phBaseDir <patch.base.directory>	Location of the base patch directory.
-oh <home>	Location of the Oracle home to patch.
-log <log>	The log location.
-logLevel <log_priority>	Log level, defaults to INFO. Supported values: SEVERE, WARNING, INFO, CONFIG, FINE, FINER, FINEST, ALL, OFF.
-customLogDir <customLogDir>	Location for creating the log files.
-binary	Forces execution of “-phases offline:binary-patching”.
-analyze	Analyzes the environment for patch suitability on each home without changing it. The patch is not applied or rolled back, and targets are not shut down.
-invPtrLoc <inventory.pointer.location>	Central inventory pointer file location.
-host <host>	The remote host or host:port.
-wallet <wallet>	Location of the wallet file. Mandatory from DB 12.1 onwards when patching as a non-root user; the running user must be part of the wallet entry.
-force_conflict	Forces application of the patch when a conflict exists, removing all conflicting patches first.
-skip_conflict	Skips conflicting patches so the remaining patches can still be applied.
-no_relink	Skips the make/linking step so it runs only once across multiple patch applications; the final run should omit this option so compilation happens.
-deleteInactivePatches	Deletes inactive patches on the home before applying new ones. Required only for targets older than 23ai.
-skip_datapatch	Skips the sqlpatch (Datapatch) step; SQL changes are skipped on every database in the session.
-skip_twostage_enable	Skips enabling previously applied two-stage patches during apply.
-skip_rrpatch	Skips rrpatch-related actions during apply and rollback.
-post_twostage_enable	Enables incoming patches after applying them, towards the end of the session; effective on the last node patched.
-extreme_perf	Relinks the binary with the extremeperf make option to enable RAC in out-of-place patching.
-jre <jre>	Path to the JRE used for local patching (not used on remote nodes).
-drain_timeout <drain.timeout>	Maximum time a service waits before exiting or before SRVCTL proceeds to stop the database, once session draining is complete.
-remote-image-location <remote.image.location>	Remote image location path.
-port <port>	Port for connecting to the catalog database (default 1521).
-inplace	Patches the original Oracle home directly (default mode). Causes downtime and affects HA of services.
-sidb	Signifies patching of a standalone single-instance database (DB 12.2+).
-sdb	Signifies patching of a sharded database. Run 'opatchauto <apply\|rollback> -sdb -help' for details.
-outofplace	Performs out-of-place patching in a single session: clones the Oracle home and switches to the clone (DB 12.2+).
-rolling	Enables sharded-database rolling mode, patching each database one after another.
-database <database>	List of databases to patch. Not supported for out-of-place patching.
-silent <silent.key>	Properties file mapping original home paths to expected clone home paths for out-of-place patching.
-prepare-clone	Prepares the clone Oracle home for out-of-place patching (DB 12.2+).
-norestart	Skips restart during execution.
-switch-clone	Switches services from the original home to the clone home (or back, on rollback). DB 12.2+.
-nonrolling	Enables non-rolling mode; mandatory for in-place patching of shared homes.
-sid <sid>	Instance name (standalone SIDB) or catalog database name (shard patching). Defaults to $ORACLE_SID if not supplied.

Typical Invocations

• Patch the GI home and all RAC homes: <GI_HOME>/OPatch/opatchauto apply <Patch_Location>

• Patch multiple homes explicitly: <GI_HOME>/OPatch/opatchauto apply <Patch_Location> -oh <GI_HOME>,<RAC_HOME1>,<RAC_HOME2>

• Patch specific databases on RAC homes only: <RAC_HOME>/OPatch/opatchauto apply <Patch_Location> -database db1,db2...dbn

• Patch a software-only install: <RAC_HOME>/OPatch/opatchauto apply <Patch_Location> -oh <RAC_HOME>

2. How OPatchAuto Discovers Oracle Homes

OPatchAuto doesn't guess which homes to patch — it reads the central inventory, inventory.xml, under the oraInventory/ContentsXML directory. Each <HOME> entry records the home's name, its filesystem location, and (for the Grid home) the CRS flag that marks it as the cluster's Grid Infrastructure home. This is exactly why a home must be properly registered before it can be targeted by an automated patching run.

RACNODE1 — CENTRAL INVENTORY BEFORE THE DB HOME WAS DE-REGISTERED

[root@racnode1 ContentsXML]# ls

comps.xml inventory.xml libs.xml

[root@racnode1 ContentsXML]# cat inventory.xml

<?xml version="1.0" standalone="yes" ?>

<VERSION_INFO>

<SAVED_WITH>12.2.0.9.0</SAVED_WITH>

<MINIMUM_VER>2.1.0.6.0</MINIMUM_VER>

</VERSION_INFO>

<HOME_LIST>

</HOME_LIST>

<COMPOSITEHOME_LIST>

</COMPOSITEHOME_LIST>

</INVENTORY>

[root@racnode1 ContentsXML]# pwd

/u01/app/oraInventory/ContentsXML

[root@racnode1 ContentsXML]#

Four homes are registered at this point: two Grid Infrastructure homes and two Database homes.

RACNODE2 — INVENTORY.XML AFTER A DATABASE HOME WAS REMOVED

[root@racnode2 ContentsXML]# cat inventory.xml

<?xml version="1.0" standalone="yes" ?>

<VERSION_INFO>

<SAVED_WITH>12.2.0.9.0</SAVED_WITH>

<MINIMUM_VER>2.1.0.6.0</MINIMUM_VER>

</VERSION_INFO>

<HOME_LIST>

</HOME_LIST>

<COMPOSITEHOME_LIST>

</COMPOSITEHOME_LIST>

</INVENTORY>

Figure 1 — inventory.xml content, viewed directly on the host.

Once a home is removed from this list, OPatchAuto simply stops seeing it — it will neither analyze it nor patch it. This is a useful first check whenever a patching run reports fewer homes than expected.

3. Prerequisite Check (‑analyze)

The -analyze flag runs every prerequisite and validation check OPatchAuto would normally run before an apply — patch applicability, conflict detection, and SQL-patch applicability — without touching the home or shutting anything down. It's the safest way to confirm a patch window will go cleanly before committing to any downtime.

PREREQUISITE CHECK KICKS OFF ON THE GRID HOME

[root@racnode1 grid1]# /u01/app/26.0.0/grid1/OPatch/opatchauto apply /u01/PatchOracleGI23.26.3/39568945 -analyze

OPatchauto session is initiated at Mon Sep 14 21:00:22 2026

System initialization log file is /u01/app/26.0.0/grid1/cfgtoollogs/opatchautodb/systemconfig2026-09-14_09-00-54PM.log.

Session log file is /u01/app/26.0.0/grid1/cfgtoollogs/opatchauto/opatchauto2026-09-14_09-03-00PM.log

The id for this session is FUYP

Executing OPatch prereq operations to verify patch applicability on home /u01/app/26.0.0/grid1

Figure 2 — opatchauto apply -analyze initiating the prerequisite session.

FULL ANALYZE RUN — GRID HOME AND DATABASE HOME, RACNODE1

[root@racnode1 grid1]# /u01/app/26.0.0/grid1/OPatch/opatchauto apply /u01/PatchOracleGI23.26.3/39568945 -analyze

OPatchauto session is initiated at Mon Sep 14 21:00:22 2026

System initialization log file is /u01/app/26.0.0/grid1/cfgtoollogs/opatchautodb/systemconfig2026-09-14_09-00-54PM.log.

Session log file is /u01/app/26.0.0/grid1/cfgtoollogs/opatchauto/opatchauto2026-09-14_09-03-00PM.log

The id for this session is FUYP

Executing OPatch prereq operations to verify patch applicability on home /u01/app/26.0.0/grid1

Patch applicability verified successfully on home /u01/app/26.0.0/grid1

Executing OPatch prereq operations to verify patch applicability on home /u01/app/oracle/product/26.0.0/dbhome_2

Patch applicability verified successfully on home /u01/app/oracle/product/26.0.0/dbhome_2

Executing patch validation checks on home /u01/app/26.0.0/grid1

Patch validation checks successfully completed on home /u01/app/26.0.0/grid1

Executing patch validation checks on home /u01/app/oracle/product/26.0.0/dbhome_2

Patch validation checks successfully completed on home /u01/app/oracle/product/26.0.0/dbhome_2

Verifying SQL patch applicability on home /u01/app/oracle/product/26.0.0/dbhome_2

SQL patch applicability verified successfully on home /u01/app/oracle/product/26.0.0/dbhome_2

OPatchAuto successful.

--------------------------------Summary--------------------------------

Analysis for applying patches has completed successfully:

Host:racnode1

CRS Home:/u01/app/26.0.0/grid1

Version:23.0.0.0.0

==Following patches were SUCCESSFULLY analyzed to be applied:

Patch: /u01/PatchOracleGI23.26.3/39568945/39578859

Log: /u01/app/26.0.0/grid1/cfgtoollogs/opatchauto/core/opatch/opatch2026-09-14_21-05-15PM_1.log

Patch: /u01/PatchOracleGI23.26.3/39568945/39578865

Log: /u01/app/26.0.0/grid1/cfgtoollogs/opatchauto/core/opatch/opatch2026-09-14_21-05-15PM_1.log

Patch: /u01/PatchOracleGI23.26.3/39568945/39578862

Log: /u01/app/26.0.0/grid1/cfgtoollogs/opatchauto/core/opatch/opatch2026-09-14_21-05-15PM_1.log

Patch: /u01/PatchOracleGI23.26.3/39568945/39578856

Log: /u01/app/26.0.0/grid1/cfgtoollogs/opatchauto/core/opatch/opatch2026-09-14_21-05-15PM_1.log

Patch: /u01/PatchOracleGI23.26.3/39568945/39578879

Log: /u01/app/26.0.0/grid1/cfgtoollogs/opatchauto/core/opatch/opatch2026-09-14_21-05-15PM_1.log

Host:racnode1

RAC Home:/u01/app/oracle/product/26.0.0/dbhome_2

Version:23.0.0.0.0

==Following patches were SKIPPED:

Patch: /u01/PatchOracleGI23.26.3/39568945/39578865

Reason: This patch is not applicable to this specified target type - "rac_database"

Patch: /u01/PatchOracleGI23.26.3/39568945/39578862

Reason: This patch is not applicable to this specified target type - "rac_database"

Patch: /u01/PatchOracleGI23.26.3/39568945/39578856

Reason: This patch is not applicable to this specified target type - "rac_database"

==Following patches were SUCCESSFULLY analyzed to be applied:

Patch: /u01/PatchOracleGI23.26.3/39568945/39578859

Log: /u01/app/oracle/product/26.0.0/dbhome_2/cfgtoollogs/opatchauto/core/opatch/opatch2026-09-14_21-13-31PM_1.log

Patch: /u01/PatchOracleGI23.26.3/39568945/39578879

Log: /u01/app/oracle/product/26.0.0/dbhome_2/cfgtoollogs/opatchauto/core/opatch/opatch2026-09-14_21-13-31PM_1.log

OPatchauto session completed at Mon Sep 14 21:22:47 2026

Time taken to complete the session 21 minutes, 56 seconds

[root@racnode1 grid1]#

A second -analyze pass below shows OPatchAuto correctly recognizing that a database running from a home on a different host is out of scope for the current session — it flags this rather than failing silently.

ANALYZE RUN — DATABASE HOME SKIPPED BECAUSE IT RUNS ON ANOTHER HOST

[root@racnode1 grid1]# /u01/app/26.0.0/grid1/OPatch/opatchauto apply /u01/PatchOracleGI23.26.3/39568945 -analyze

OPatchauto session is initiated at Mon Sep 14 21:54:41 2026

System initialization log file is /u01/app/26.0.0/grid1/cfgtoollogs/opatchautodb/systemconfig2026-09-14_09-55-10PM.log.

Following home(s) will not be included as part of current opatchauto session as they do not run from the current host.

Database Name: orcldb

Oracle Home: /u01/app/oracle/product/26.0.0/dbhome_2

Host:

racnode1

racnode2

To complete the patching process for the above databases, execute it on host where the databases are running.

Session log file is /u01/app/26.0.0/grid1/cfgtoollogs/opatchauto/opatchauto2026-09-14_09-56-07PM.log

The id for this session is 9PC9

Executing OPatch prereq operations to verify patch applicability on home /u01/app/26.0.0/grid1

Patch applicability verified successfully on home /u01/app/26.0.0/grid1

Executing patch validation checks on home /u01/app/26.0.0/grid1

Patch validation checks successfully completed on home /u01/app/26.0.0/grid1

OPatchAuto successful.

--------------------------------Summary--------------------------------

Analysis for applying patches has completed successfully:

Host:racnode1

CRS Home:/u01/app/26.0.0/grid1

Version:23.0.0.0.0

==Following patches were SUCCESSFULLY analyzed to be applied:

Patch: /u01/PatchOracleGI23.26.3/39568945/39578859

Log: /u01/app/26.0.0/grid1/cfgtoollogs/opatchauto/core/opatch/opatch2026-09-14_21-58-03PM_1.log

Patch: /u01/PatchOracleGI23.26.3/39568945/39578865

Log: /u01/app/26.0.0/grid1/cfgtoollogs/opatchauto/core/opatch/opatch2026-09-14_21-58-03PM_1.log

Patch: /u01/PatchOracleGI23.26.3/39568945/39578862

Log: /u01/app/26.0.0/grid1/cfgtoollogs/opatchauto/core/opatch/opatch2026-09-14_21-58-03PM_1.log

Patch: /u01/PatchOracleGI23.26.3/39568945/39578856

Log: /u01/app/26.0.0/grid1/cfgtoollogs/opatchauto/core/opatch/opatch2026-09-14_21-58-03PM_1.log

Patch: /u01/PatchOracleGI23.26.3/39568945/39578879

Log: /u01/app/26.0.0/grid1/cfgtoollogs/opatchauto/core/opatch/opatch2026-09-14_21-58-03PM_1.log

OPatchauto session completed at Mon Sep 14 22:06:42 2026

Time taken to complete the session 11 minutes, 35 seconds

ANALYZE RUN — BOTH GRID AND DATABASE HOMES VALIDATED TOGETHER ON RACNODE1

[root@racnode1 grid1]# /u01/app/26.0.0/grid1/OPatch/opatchauto apply /u01/PatchOracleGI23.26.3/39568945 -analyze

OPatchauto session is initiated at Mon Sep 14 22:23:30 2026

System initialization log file is /u01/app/26.0.0/grid1/cfgtoollogs/opatchautodb/systemconfig2026-09-14_10-23-54PM.log.

Session log file is /u01/app/26.0.0/grid1/cfgtoollogs/opatchauto/opatchauto2026-09-14_10-25-59PM.log

The id for this session is 5VTM