Oracle Database Upgrade Matrix (Enterprise / LTS Focus)
1️⃣ Direct Upgrade Support Matrix
Legend
✅ Supported & recommended
⚠️ Supported but not recommended
❌ Not supported
| Source → Target | 19c | 21c | 23ai | 26ai |
|---|---|---|---|---|
| 11.2.0.4 | ✅ | ❌ | ❌ | ❌ |
| 12.1.0.2 | ✅ | ❌ | ❌ | ❌ |
| 12.2.0.1 | ✅ | ❌ | ❌ | ❌ |
| 18c | ✅ | ❌ | ❌ | ❌ |
| 19c | — | ⚠️ | ✅ | ❌ |
| 21c | ⚠️ | — | ✅ | ❌ |
| 23ai | ❌ | ❌ | — | ✅* |
* 23ai → 26ai is not a classic upgrade
It is a Release Update (RU) transition, same code line.
2️⃣ Recommended Enterprise Upgrade Paths (What Actually Works)
✅ Best‑Practice Path (Most Enterprises)
11g / 12c / 18c
↓
19c ← Stability Anchor (LTS)
↓
23ai ← AI Foundation (LTS)
↓
26ai ← AI‑Native Platform
✅ If Already on 19c
19c → 23ai → (RU) → 26ai
🚫 Not Recommended (Even If “Technically Possible”)
| Path | Reason |
|---|---|
| 19c → 26ai | Skips AI foundation |
| 12c → 23ai | Too many dictionary jumps |
| 19c → 21c → 23ai | 21c is innovation‑only |
| 11g → 23ai | Unsupported |
3️⃣ AutoUpgrade Support Matrix (Execution‑Level)
| Source | Target | AutoUpgrade | Notes |
|---|---|---|---|
| 11.2.0.4 | 19c | ✅ | Most common path |
| 12.1 | 19c | ✅ | Direct supported |
| 18c | 19c | ✅ | Minor effort |
| 19c | 23ai | ✅ | Preferred method |
| 23ai | 26ai | ❌ | RU, not AutoUpgrade |
✅ AutoUpgrade is mandatory for serious environments
(DBUA only for small/non‑critical DBs)
4️⃣ CDB / PDB Compatibility Matrix
| Version | Non‑CDB | CDB |
|---|---|---|
| 11g | ✅ | ❌ |
| 12.1 | ✅ | ❌ |
| 12.2 / 18c | ⚠️ | ✅ |
| 19c | ⚠️ (deprecated) | ✅ |
| 23ai | ❌ | ✅ |
| 26ai | ❌ | ✅ |
👉 23ai and above = CDB‑only architecture
5️⃣ RAC & Data Guard Upgrade Compatibility
| Path | RAC | Data Guard |
|---|---|---|
| 18c → 19c | ✅ | ✅ |
| 19c → 23ai | ✅ | ✅ |
| 23ai → 26ai | ✅ | ✅ |
| 19c → 26ai | ❌ | ❌ |
✅ Standby must be upgraded in lockstep
6️⃣ Zero‑Downtime Upgrade Matrix (GoldenGate)
| Scenario | Recommended Approach |
|---|---|
| 19c → 23ai | GoldenGate logical replication |
| 23ai → 26ai | Not required (RU change) |
| Platform change | GoldenGate |
| DB size > 10 TB | GoldenGate |
Typical flow:
19c (Prod)
↓ GG Replication
23ai (Target)
↓ Cutover
7️⃣ AI Feature Availability Matrix
| Capability | 19c | 23ai | 26ai |
|---|---|---|---|
| VECTOR data type | ❌ | ✅ | ✅ |
| AI Vector Search | ❌ | ✅ | ✅ |
| JSON Relational Duality | ❌ | ✅ | ✅ |
| Select AI (NL → SQL) | ❌ | ✅ | ✅ |
| AI Agents | ❌ | ❌ | ✅ |
| Built‑in RAG | ❌ | ⚠️ | ✅ |
✅ AI features are optional, not mandatory
8️⃣ Executive One‑Slide Summary (Paste Directly)
Upgrade Rule of Thumb:
• 19c = Last Classic LTS
• 23ai = Mandatory AI Foundation
• 26ai = AI‑Native Platform
Never jump 19c → 26ai directly.
Always stabilize on 23ai first.
9️⃣ Interview / Architecture Review Ready Answer
Q: Why can’t we upgrade 19c directly to 26ai?
✅ Correct Answer:
Oracle 26ai is a continuation of the 23ai code line delivered via release update. Enterprises must first upgrade to 23ai to establish SQL, optimizer, and AI foundations, then transition safely to 26ai.
No comments:
Post a Comment