Next platform deadline: Amazon EKS Nov 26, 2026  

All 14 deadlines

Oracle & Middleware

The Oracle upgrade checklist for 2026–2027: 12 checks before you start

Support dates, JDK 17/21, AutoUpgrade, multitenant, testing and rollback: twelve checks that keep an upgrade on schedule.

By the SRASH team · · 7 min read

Key facts

  • Fusion Middleware 12c: Premier Support ends Dec 2026, Extended Dec 2027.
  • RDS Custom for Oracle: retires Mar 31, 2027.
  • Oracle Database 21c: Premier Support ends Jul 2027, no Extended Support.
  • Oracle Database 19c: Premier Dec 2029, Extended Dec 2032. 26ai: Premier to Dec 2031.

Scope and dates

1. Build one inventory

List every database, middleware domain and application tier with its version, patch level, edition, platform and owner. Upgrades slip most often because of a system nobody listed.

2. Put the support dates next to each line

ProductDateWhat happens
Fusion Middleware 12c (12.2.1.4 / 12.2.1.19)Dec 2026Premier Support ends
Amazon RDS Custom for OracleMar 31, 2027Service retires; console and resources inaccessible
Oracle Database 21cJul 2027Premier Support ends; no Extended Support
Fusion Middleware 12cDec 2027Extended Support ends
Oracle Database 19cDec 2029Premier Support ends; Extended to Dec 2032
Oracle AI Database 26aiDec 2031Premier Support ends; Extended to be determined

3. Work backwards from the date

Count the environments you must upgrade, add a rehearsal for each, and add change freezes. If the result starts before today, the project is already late.

Middleware

4. Confirm the path to 14.1.2

Oracle documents the upgrade to 14.1.2 from 12.2.1.4. Older releases need a staged path or a clean build with WebLogic Deploy Tooling.

5. Test on JDK 17 or 21 first

WebLogic 14.1.2 is certified on JDK 17 and 21. Run your applications on the new JDK in a test domain before anything else; it is where most surprises come from.

6. Plan for the Remote Console

The classic Administration Console was removed in 14.1.2. Update runbooks, training and any scripts that relied on it.

Database

7. Use AutoUpgrade

For 26ai, Oracle states AutoUpgrade and Replay Upgrade are the only supported upgrade methods; DBUA and the manual Parallel Upgrade Utility are desupported. Run AutoUpgrade in analyze mode early to see the fix-up list.

8. Plan the multitenant conversion

Releases after 19c are multitenant only, so a non-CDB is converted to a pluggable database. Once the conversion completes, the AutoUpgrade restore point can no longer take you back, so take and test a backup first.

9. Check the direct path

Oracle supports direct upgrades to 26ai from 19c and 21c. Anything older goes through an intermediate release.

Cloud

10. Decide RDS Custom targets per database

For RDS Custom for Oracle, compare Oracle on EC2 (the path AWS documents), Amazon RDS for Oracle and Oracle Database@AWS, and choose RMAN active duplication or Data Guard per database.

Proof

11. Baseline performance before you change anything

Capture AWR reports and key timings before the upgrade, so you can prove afterwards that nothing got slower, or find out quickly if something did.

12. Write the rollback plan and rehearse it

Every cut-over needs a timed rehearsal and a tested way back. Keep the old system available until the new one has run through a full business cycle.

Start with a free 30-minute review.

Databases, cloud or AI: talk to a senior engineer about what you run and what is coming. We reply within one business day and sign your NDA on request.