Oracle Grid Infrastructure 23ai powers mission-critical RAC, ASM, and Clusterware environments, making regular Release Updates essential for enterprise stability, security, and operational efficiency. In this guide, we’ll walk through the complete process of patching Oracle Grid Infrastructure to Release Update 23.26.2.0.0 using Patch 39088031, including OPatch troubleshooting, prerequisite checks, and successful OPatchAuto deployment in a RAC production environment.
Why Upgrade Oracle Grid Infrastructure to 23.26.2?
Oracle GI RU 39088031 provides:
- Security vulnerability remediation
- RAC and Clusterware bug fixes
- ASM stability improvements
- Enhanced Oracle Restart and CRS reliability
- Better alignment with Oracle Database 23ai RU 23.26.2
- Updated Gold Image consistency across cluster nodes
For Oracle RAC administrators, keeping Grid Infrastructure aligned with database patch levels is critical for maintaining supportability and minimizing operational risk.
Existing Environment Validation
Before patching, verify current patch levels.
Database Home:
$ opatch lspatches
38743669;Database Release Update : 23.26.1.0.0Grid Home:
$ opatch lspatches
38743688;OCW RELEASE UPDATE 23.26.1.0.0
38743706;ACFS RELEASE UPDATE 23.26.1.0.0This confirms both homes are running 23.26.1 Gold Image prior to patching.
Step 1: Upgrade OPatch Utility
The initial Grid Home OPatch version:How To Download And Install The Latest OPatch
OPatch Version: 12.2.0.1.48Oracle recommends OPatch 12.2.0.1.49 or later.
Resolution:
- Download latest p6880880
- Replace existing OPatch
- Correct ownership:
chown -R grid:oinstall OPatchStep 2: Run Comprehensive Prerequisite Checks
Each sub-patch within GI RU 39088031 should be validated individually:
Included patches:
- 39093711
- 39093738
- 39099110
- 39099119
- 39099244
Example:
opatch prereq CheckConflictAgainstOHWithDetailResults:
All conflict checks passed successfully after OPatch upgrade.
Step 3: Apply GI RU Using OPatchAuto
Oracle RAC environments should use:
/u01/app/23.26.0.0/grid/OPatch/opatchauto apply /u01/patch/39088031 -oh /u01/app/23.26.0.0/grid -logLevel FINESTOPatchauto session is initiated at Mon May 4 14:38:16 2026
System initialization log file is /u01/app/23.26.0.0/grid/cfgtoollogs/opatchautodb/systemconfig2026-05-04_02-38-27PM.log.
Session log file is /u01/app/23.26.0.0/grid/cfgtoollogs/opatchauto/opatchauto2026-05-04_02-38-45PM.log
The id for this session is G3VH
Executing OPatch prereq operations to verify patch applicability on home /u01/app/23.26.0.0/grid
Patch applicability verified successfully on home /u01/app/23.26.0.0/grid
Executing patch validation checks on home /u01/app/23.26.0.0/grid
Patch validation checks successfully completed on home /u01/app/23.26.0.0/grid
Performing prepatch operations on CRS - bringing down CRS service on home /u01/app/23.26.0.0/grid
Prepatch operation log file location: /u01/app/grid/crsdata/rac-node1/crsconfig/crs_prepatch_apply_inplace_rac-node1_2026-05-04_02-40-48PM.log
CRS service brought down successfully on home /u01/app/23.26.0.0/grid
Start applying binary patch on home /u01/app/23.26.0.0/grid
Binary patch applied successfully on home /u01/app/23.26.0.0/grid
Running rootadd_rdbms.sh on home /u01/app/23.26.0.0/grid
Successfully executed rootadd_rdbms.sh on home /u01/app/23.26.0.0/grid
Performing postpatch operations on CRS - starting CRS service on home /u01/app/23.26.0.0/grid
Postpatch operation log file location: /u01/app/grid/crsdata/rac-node1/crsconfig/crs_postpatch_apply_inplace_rac-node1_2026-05-04_02-54-32PM.log
CRS service started successfully on home /u01/app/23.26.0.0/grid
OPatchAuto successful.
--------------------------------Summary--------------------------------
Patching is completed successfully. Please find the summary as follows:
Host:rac-node1
CRS Home:/u01/app/23.26.0.0/grid
Version:23.0.0.0.0
Summary:
==Following patches were SUCCESSFULLY applied:
Patch: /u01/patch/39088031/39093711
Log: /u01/app/23.26.0.0/grid/cfgtoollogs/opatchauto/core/opatch/opatch2026-05-04_14-45-20PM_1.log
Patch: /u01/patch/39088031/39093738
Log: /u01/app/23.26.0.0/grid/cfgtoollogs/opatchauto/core/opatch/opatch2026-05-04_14-45-20PM_1.log
Patch: /u01/patch/39088031/39099110
Log: /u01/app/23.26.0.0/grid/cfgtoollogs/opatchauto/core/opatch/opatch2026-05-04_14-45-20PM_1.log
Patch: /u01/patch/39088031/39099119
Log: /u01/app/23.26.0.0/grid/cfgtoollogs/opatchauto/core/opatch/opatch2026-05-04_14-45-20PM_1.log
Patch: /u01/patch/39088031/39099244
Log: /u01/app/23.26.0.0/grid/cfgtoollogs/opatchauto/core/opatch/opatch2026-05-04_14-45-20PM_1.log
OPatchauto session completed at Mon May 4 15:05:28 2026
Time taken to complete the session 27 minutes, 2 secondsStep 4: Successful Patch Completion
Output:
OPatchAuto successful.$ ./opatch lspatches
39099244;RHP RELEASE UPDATE 23.26.2.0.0 (39099244)
39099119;MICRONAUT RELEASE UPDATE 23.26.2.0.0 (39099119)
39099110;ACFS RELEASE UPDATE 23.26.2.0.0 (39099110)
39093738;OCW RELEASE UPDATE 23.26.2.0.0 (39093738)
39093711;Database Release Update : 23.26.2.0.0 (39093711)
OPatch succeeded.
Successfully applied:
- Patch 39093711
- Patch 39093738
- Patch 39099110
- Patch 39099119
- Patch 39099244
Total patch duration:
Approximately 27 minutes.
Post-Patching Benefits
After GI RU 23.26.2 deployment:
Infrastructure gains:
- Updated RAC stack
- Enhanced CRS performance
- ASM security improvements
- ACFS bug fixes
- Better node synchronization
- Improved Gold Image compliance
DBA Best Practices for Oracle GI 23ai
Recommended patching checklist:
- Upgrade OPatch first
- Validate all patch bundles
- Run minimum version checks
- Check conflicts individually
- Ensure correct file ownership
- Use OPatchAuto for RAC
- Monitor CRS logs carefully
- Validate cluster services post-patch
Common Oracle GI Patch Risks
Watch for:
- OPatch incompatibility
- Unzip failures
- CRS shutdown issues
- Ownership problems
- Patch supersets
- RAC communication issues
Thorough preparation significantly reduces deployment failures.
Final Thoughts
Oracle Grid Infrastructure 23ai Patch 39088031 is a critical Release Update for maintaining RAC platform security, stability, and compatibility with Oracle AI Database environments.
This production-tested deployment demonstrates that successful GI patching requires:
- Updated OPatch tooling
- Proper prerequisite validation
- Correct patch bundle preparation
- Automated OPatchAuto deployment
- Careful CRS lifecycle management
For enterprise DBAs, Oracle GI patching remains one of the most important operational disciplines for protecting mission-critical infrastructure.
Oracle Grid patching is not just maintenance—it’s enterprise continuity engineering.
Comments 1