top of page
Search

April 2026 Oracle RU Patch Numbers Every DBA Must Know (19c / 21c / 23ai → 26ai)

Oracle's April 2026 Critical Patch Update is finally out — and after the well-documented delay around 19.31 and 23.26.2, it has become one of the most consequential RU cycles of the year. If you've been following our October 2025 RU patch guide or our deep dive on Oracle AI Database 26ai on-premises, this is the next mandatory checkpoint for every Oracle estate running 19c, 21c, 23ai, or 26ai.


Below are the exact patch IDs, verified across multiple sources (Oracle MOS, the Oracle CPU advisory, Mike Dietrich's upgrade blog, and DBsGuru), with field-tested guidance on what to apply, in which order, and what to watch out for.



Oracle April 2026 RU patch map showing patch numbers for 19c 19.31, 21c 21.22, 23ai 26ai 23.26.2 — DB RU, GI RU, OJVM, Exadata Full Stack
April 2026 RU patch map — verified DB / GI / OJVM / Exadata IDs across 19c, 21c, and 23ai → 26ai.


Section 1: Oracle Patch Checklist — April 2026 RUs (Exact Patch IDs)



Oracle Database 19c — RU 19.31.0.0.260412


  • Database RU (UNIX): Patch 39034528

  • Grid Infrastructure RU (UNIX): Patch 39036936

  • Combo OJVM + DB RU: Patch 39062931 — for Java-in-DB workloads (EBS, Forms, SOA, custom JVM PL/SQL)

  • Combo OJVM + GI RU: Patch 39062956 — single-pass RAC + OJVM apply

  • OJVM standalone (all platforms): Patch 38906621

  • Exadata Q-Full-Stack: Patch 39063037

  • MS Windows BP (32 + 64-bit): Patch 38818049



Oracle Database 21c — RU 21.22.0.0.260421

  • Database RU (UNIX): Patch 39073698

  • Grid Infrastructure RU (UNIX): Patch 39073631

  • Exadata Q-Full-Stack: Patch 39063054

  • MS Windows BP: Patch 38955012

  • Note: 21c has no separate OJVM patch — OJVM fixes are inside the DB RU and GI RU.



Oracle AI Database 23ai → 26ai — RU 23.26.2.0.0

  • Database RU (UNIX): Patch 39093711

  • Grid Infrastructure RU (UNIX): Patch 39088031

  • Grid GoldImage: Patch 39099896 — fresh install + patch in one step

  • Database GoldImage: Patch 39099680

  • Client GoldImage: Patch 39099870

  • Exadata Q-Full-Stack: Patch 39063134


Important context: Oracle delayed both 19.31 and 23.26.2 from the original 28 April 2026 ETA, briefly placed 19.31 on hold on 13 May, and re-released DB RU + GI RU for Linux on 15 May. Non-Linux platforms have rolled out through late May and into June. Always check the Oracle Critical Patch Update advisory for April 2026 before downloading — IDs above are correct, but availability dates vary per platform.



Section 2: Why These Patches Matter — DBA View


1️⃣ Oracle 19c — RU 19.31


19c remains the long-term workhorse running ~70% of enterprise OLTP. 19.31 ships fixes that touch the production-critical surface:

  • Optimizer: further fixes for cardinality misestimates introduced by adaptive plans in JSON + relational hybrid queries.

  • RAC: GC current/CR block-shuffle improvements under heavy DML on interconnect-bound clusters.

  • Active Data Guard: MRP apply lag and resync edge cases on PDB-level redo when concurrent block-change tracking is enabled.

  • Security: multiple CVE fixes — see the CPU advisory for the full list.

  • AutoUpgrade: tighter pre-checks for 19c → 26ai jumps (the upgrade most enterprises are planning now).


Verdict: If you run EBS, BFSI core banking, telecom CDR, or any high-throughput OLTP — apply 19.31 in your next maintenance window.



2️⃣ Oracle 21c — RU 21.22


21c continues to be the innovation release for JSON, blockchain tables, AutoML, and in-database automation. 21.22 hardens:

  • JSON indexes — concurrent DML with autogather stats stability fixes (an issue some teams hit on JSON-heavy microservices).

  • In-DB AutoML — SQL-based training pipeline reliability under partition-pruned input.

  • Blockchain tables — temporal consistency under high-write workloads.

  • OCI ATP/ADW parity — alignment fixes between on-prem 21c and Autonomous behavior.



3️⃣ Oracle AI Database (23ai → 26ai) — RU 23.26.2


This is the second RU in the 26ai-branded train. It builds on 23.26.1 (which we covered in our Oracle 26ai on-premises release guide) and adds:

  • AI Vector Search: HNSW index rebuild reliability + approximate-search recall improvements on >1B-row vector tables.

  • SQL Firewall: lower-overhead allow-list capture, especially for OLTP workloads running thousands of distinct SQL_IDs/hour.

  • True Cache: Active Data Guard re-sync fixes after primary RAC node eviction.

  • Memory Guard: smarter PGA throttling on AI/embedding-heavy sessions touching >70% PGA.

  • Multitenant: In-Memory columnstore tuning for GenAI retrieval functions running across multiple PDBs.


Verdict: Non-negotiable for anyone running AI Vector Search, RAG, or 26ai in production. The vector index fixes alone justify the apply.


Section 3: Recommended Patching Strategy (Field-Tested)


Apply order: GI first, then DB, then OJVM

For RAC and Exadata, the only safe sequence:

  • Step 1: GI RU (rolling)

  • Step 2: DB RU (rolling)

  • Step 3: OJVM (if applicable — Combo patch lets you do steps 1+3 or 2+3 in one apply)


Use opatchauto for RAC + Combo patches

# Baseline before patching
$ORACLE_HOME/OPatch/opatch lsinventory > /tmp/lsinv_before_$(date +%F).txt

# Apply GI RU (rolling) on each node, then DB RU
$GRID_HOME/OPatch/opatchauto apply /stage/39036936
$ORACLE_HOME/OPatch/opatchauto apply /stage/39034528

# Or Combo OJVM+DB in one go
$ORACLE_HOME/OPatch/opatchauto apply /stage/39062931

# Run datapatch after every DB RU
$ORACLE_HOME/OPatch/datapatch -verbose

# Verify
$ORACLE_HOME/OPatch/opatch lsinventory > /tmp/lsinv_after_$(date +%F).txt
diff /tmp/lsinv_before_*.txt /tmp/lsinv_after_*.txt

Three non-negotiables

  • Never skip more than two RUs on 19c — optimizer regressions stack up otherwise.

  • Always lsinventory before AND after. Capture both for audit trails and to debug failed restarts.

  • Run datapatch -verbose after every DB RU. The number of teams that forget this and then chase phantom plan changes is staggering.


Watch the apply walkthrough


Step-by-step opatchauto + datapatch walkthroughs (RAC + standalone) are on the Oracle DBA Online Training YouTube channel → — 200+ free Oracle DBA tutorials covering Architecture, Installation, RAC, Data Guard, RMAN, GoldenGate, OEM, and Performance Tuning.


Section 4: Quick Takeaways


  • April 2026 CPU closes high-impact issues across optimizer, RAC, ADG, vector search, and SQL Firewall layers — and the delayed rollout means many shops are patching in May–June 2026.

  • 19c → priority for most enterprises — 19.31 includes OLTP and ADG reliability fixes that should land in your next maintenance window.

  • 21.22 stabilizes JSON, blockchain, and AutoML edge cases.

  • 23ai → 26ai (RU 23.26.2) is non-negotiable for vector and GenAI retrieval workloads.

  • Exadata + RAC teams should patch early — cluster-wide stability fixes are worth the window.

Need a complete RAC + Data Guard switchover-based rolling patching plan for 19.31 or 23.26.2? DBNexus Training & Consulting (formerly Oracle DBA Online Training) runs live, hands-on patching labs as part of every Oracle DBA cohort — you patch real RAC clusters under instructor supervision before going to production. Also you can learn how to apply the April 2026 Oracle RU Patch.



FAQ


What's the exact 19.31 DB RU patch number for April 2026?

Patch 39034528 (19.31.0.0.260412) for UNIX/Linux. GI RU is 39036936. OJVM standalone is 38906621.


What is the 23.26.2 / 26ai RU patch for April 2026?

DB RU is 39093711 and GI RU is 39088031 (RU 23.26.2.0.0).


Why was 19.31 delayed in 2026?

Oracle initially targeted 28 April 2026, then delayed the rollout and briefly placed 19.31 on hold. DB RU and GI RU for Linux were re-released on 15 May 2026; non-Linux platforms followed through late May / early June.


Do I need to apply OJVM separately on 21c?

No. 21c rolls OJVM fixes into the DB RU and GI RU. There is no separate OJVM patch for 21c.


In what order do I apply GI, DB, and OJVM on RAC?

Always: GI RU → DB RU → OJVM, rolling node-by-node. Or use the Combo patches (39062931 for OJVM+DB, 39062956 for OJVM+GI on 19c) to do two in one apply.



Ready to apply the April 2026 Oracle RU patch with confidence? Train with DBNexus.


DBNexus Training & Consulting (formerly Oracle DBA Online Training) runs live, instructor-led Oracle DBA programs covering everything in this article — 19c, 21c, 23ai, 26ai, AutoUpgrade, opatchauto, RAC rolling patching, Data Guard switchover-based patching, Exadata Q-FS, OJVM Combo apply, and the monthly CSPU cadence. Real lab environments. Real production scenarios. Recorded sessions. Lifetime access.

  • Hands-on patching labs on real RAC clusters and Data Guard standbys — not slides.

  • Production-style scenarios: rolling RU apply, datapatch verification, rollback drills, opatchauto failure recovery, Exadata QFS handling.

  • 10,000+ DBAs trained globally across India, US, UK, Singapore, and the Middle East.

  • Interview prep + CV review included.

  • Subscribe to the YouTube channel Oracle DBA Online Training for 200+ free Oracle DBA video tutorials.

📞 CALL NOW: +91 8169158909 — talk to the DBNexus team directly about the next Oracle DBA + Patching batch, fees, and demo class. (India, IST 9 AM–10 PM.)


Early-bird seat for the next batch? Mention this post when you call — we will block a free demo session for you on the RAC rolling RU patching lab.

Comments

bottom of page