Home / Oracle DBA / Database upgrades
Oracle database upgrades
Oracle 19c upgrade services, and the path to 26ai
For IT teams still running Oracle 11.2.0.4, 12.1, 12.2, 18c or 21c. We take each database to Oracle 19c or Oracle AI Database 26ai: AutoUpgrade analysis, choice of method (AutoUpgrade, Data Pump, transportable tablespaces, Data Guard or GoldenGate), a test upgrade with plan comparison, a timed rehearsal, cutover with a guaranteed restore point, and post-upgrade tuning. Work is led by a senior Oracle DBA with 20+ years' experience, with India-based DBAs overlapping 09:00–13:30 US Eastern.
Quick answer
What do Oracle 19c upgrade services include?
Oracle 19c upgrade services cover assessment, method selection, testing, cutover and fallback. Direct upgrade to 19c is supported from 11.2.0.4, 12.1.0.2, 12.2.0.1 and 18c. AutoUpgrade is Oracle's recommended tool. A sound project runs AutoUpgrade in analyze mode, tests SQL performance on a copy, rehearses the runbook, and keeps a guaranteed restore point until the upgrade is accepted.
Deadlines
Oracle Database support dates
Per Oracle's Lifetime Support Policy (effective October 2, 2026): 19c Premier Support ends December 2029 and paid Extended Support December 2032; 21c, an Innovation Release, has Premier Support to July 2027 with no Extended Support; 26ai Premier Support ends December 2031, Extended Support to be announced. Releases 11.2 and 12.1 are past Extended Support and in Sustaining Support. Oracle updates this policy, so check the current Oracle Lifetime Support Policy for your release and platform before planning.
Oracle 19c
Upgrading to Oracle 19c: supported paths
| Current release | Direct to 19c? | Route |
|---|---|---|
| 18c (all releases) | Yes | AutoUpgrade direct |
| 12.2.0.1 | Yes | AutoUpgrade direct |
| 12.1.0.2 | Yes | AutoUpgrade direct |
| 11.2.0.4 | Yes | AutoUpgrade direct |
| 12.1.0.1, 11.2.0.3 or earlier | No | Upgrade to a release that supports direct upgrade first, or move the data with Data Pump or transportable tablespaces |
Source: Oracle Database 19c Upgrade Guide, "Oracle Database Releases That Support Direct Upgrade".
19c details that catch teams out
- Start on the latest 19c Release Update, not the base 19.3 image
- Leave
COMPATIBLEat the old value until the fallback window closes; raising it rules out flashback to the restore point - Upgrade the time zone file (DST) as part of the project, not later
- Check deprecated and desupported parameters in the AutoUpgrade report
- On AIX, Linux on IBM Z, Solaris, HP-UX and Windows ports, note Oracle's Java 8 support caveat for 19c in the Lifetime Support Policy
Why 19c is still the common target
19c is the long-term support release with the widest packaged-application certification today and Extended Support to December 2032 per Oracle's policy. Most ERP and vendor applications certify on 19c first. If a vendor has certified 26ai and you can convert to multitenant now, going straight to 26ai saves a second project later.
Oracle AI Database 26ai
Upgrading to 26ai
Oracle's 26ai Upgrade Guide lists direct upgrade only from 19c and 21c. Anything older goes to 19c first, then to 26ai. If you already run 23ai, check Oracle's 26ai documentation for the supported update path.
The larger change is architecture. Oracle desupports upgrading a non-CDB to a non-CDB, so every 26ai database runs as a pluggable database (PDB) inside a container database (CDB). You can convert during the upgrade with AutoUpgrade, convert on 19c first, or migrate into a PDB with Data Pump or transportable tablespaces.
Each PDB conversion touches backup scripts, RMAN catalogs, monitoring, service names and connection strings. We plan those changes as part of the project, not as clean-up afterwards.
| Oracle 19c | Oracle 26ai | |
|---|---|---|
| Premier Support to | Dec 2029 | Dec 2031 |
| Extended Support | To Dec 2032 (paid) | To be announced |
| Direct upgrade from | 11.2.0.4, 12.1.0.2, 12.2.0.1, 18c | 19c, 21c |
| Non-CDB allowed | Yes (deprecated) | No; PDB required |
| Application certification | Widest today | Check with each vendor |
| Good fit | Packaged apps, lowest risk | Longest runway, new features |
Methods
Oracle upgrade methods compared
| Method | Typical downtime | Use when | Notes |
|---|---|---|---|
| AutoUpgrade (in place or to a new server) | Hours | Standard path; most upgrades | Oracle's recommended tool; analyze, fixups and deploy modes; restore point and checkpoints; can convert non-CDB to PDB |
| DBUA | Hours | Single database, GUI preferred | Older interactive tool; AutoUpgrade is preferred for repeatable runs |
| Data Pump export and import | Longer; grows with data size | Very old releases, platform or character set change, cleanup on the way | Simple and flexible; slow for large databases |
| Transportable tablespaces / full transportable export | Shorter than Data Pump for large data | Large databases, new hardware, cross-platform moves | Datafiles move, metadata via Data Pump; incremental backups can shorten the final step |
| Data Guard rolling upgrade (transient logical standby, DBMS_ROLLING) | Minutes | Data Guard in place and downtime is costly | DBMS_ROLLING requires Active Data Guard licensing; check data type support for logical standby |
| GoldenGate replication | Near zero | Systems that cannot stop; cross-platform or cross-version moves | Separately licensed; more setup; allows a reverse feed for fallback |
Moving to the cloud at the same time? See Oracle cloud migration.
Choosing
How to choose the method
- Allowed downtime is a few hours: AutoUpgrade, in place or to a new server.
- Allowed downtime is minutes and Data Guard exists: a rolling upgrade with a transient logical standby.
- Downtime must be near zero, or you need a live way back: GoldenGate.
- Source is older than 11.2.0.4, or the platform changes: Data Pump for small databases, transportable tablespaces for large ones.
- Many databases: AutoUpgrade with one config file per wave, so each run is repeatable.
Considering third-party support instead of upgrading? Read our comparison guide. When moving off Oracle beats upgrading, see Oracle to PostgreSQL.
Upgrade checklist
- Application vendor certification for the target release
- AutoUpgrade analyze report reviewed and fixed
- Full RMAN backup and a guaranteed restore point
- Fresh dictionary and optimizer statistics
- SQL plan baselines captured for critical queries
- Time zone file and character set checked
- Rehearsal timed on a production-size copy
- Rollback steps written and tested
Approach
How we run an Oracle 19c or 26ai upgrade
Assess
Inventory versions, editions, options, character sets, invalid objects and application certifications. Run AutoUpgrade in analyze mode (and
preupgrade.jarwhere a 19c target still calls for it) to list blockers without changing anything.Choose the method
Pick from the table above based on downtime, size, platform and licensing. Decide whether to convert to a PDB now or later.
Fix and prepare
Apply AutoUpgrade fixups, gather dictionary statistics, capture SQL Tuning Sets and plan baselines for critical SQL, and take a full RMAN backup.
Test
Upgrade a copy and run application tests. Compare execution plans before and after with SQL Performance Analyzer where licensed, or with captured SQL Tuning Sets and AWR reports.
Rehearse
A timed dress rehearsal of the production runbook on a production-size copy, including the restore to the starting point.
Cut over with a way back
AutoUpgrade deploy with a guaranteed restore point, or a standby or GoldenGate reverse feed kept ready, so the upgrade can be reversed if checks fail.
Stabilize
Watch performance for the first weeks, fix plan changes as they appear, then drop the restore point and raise
COMPATIBLEonce the business signs off.
Testing and fallback
Performance testing and a tested way back
SQL Performance Analyzer (SPA) runs a captured SQL workload on the old and new release and reports which statements got slower. Database Replay replays real production load against the upgraded copy. Both belong to Real Application Testing, which on-premises Enterprise Edition licenses separately, and AWR reports need the Diagnostics Pack. Confirm what you are licensed for before we use them; without them we compare plans from captured SQL Tuning Sets and application test runs.
Guaranteed restore point. Before the upgrade we create a guaranteed restore point. If post-upgrade checks fail, Flashback Database returns the database to its pre-upgrade state in minutes rather than hours of restore. This works only while COMPATIBLE stays at the old value, which is why we raise it last.
What you get
- Inventory and AutoUpgrade analyze report for every database
- Upgrade path and method decision for each, with downtime estimate
- AutoUpgrade config files and a written runbook
- Test upgrade with before-and-after SQL performance comparison
- Timed rehearsal results, including the restore
- Cutover run, with rollback criteria agreed in advance
- Post-upgrade tuning and handover notes
Who does the work
Senior Oracle DBAs, US-hours overlap
Upgrades are led by a senior Oracle DBA with 20+ years' experience. Our India-based DBAs work a US-aligned shift (14:00–23:00 IST, overlapping 09:00–13:30 US Eastern), with a daily standup in the overlap and a written end-of-day handoff. Cutovers are planned around your maintenance window. After go-live, remote Oracle DBA services can cover monitoring, patching, RMAN backups and performance tuning.
Case study: phased migration with parallel run
Financial services · client name withheld
- Mainframe core banking to cloud-native
- 18 months, 12 senior engineers
- Phased migration with parallel run
- Zero-downtime cutover
- Regulatory audit with no findings
The same discipline applies to an Oracle upgrade: rehearse, run in parallel where possible, and cut over only with a proven way back. See case studies.
Contact us
Plan your Oracle upgrade
Tell us your current versions and deadline. A senior Oracle DBA will reply with the upgrade path and next steps.
- A senior engineer reads every message
- Reply within one business day
- No obligation, and your details are used only to reply
Prefer the full form? Go to the contact page.
FAQ
Questions buyers ask us
Can we upgrade directly from 11g to 19c?
Yes, from 11.2.0.4. Oracle's 19c Upgrade Guide lists direct upgrade from 11.2.0.4, 12.1.0.2, 12.2.0.1 and 18c. Older releases, such as 11.2.0.3 or 12.1.0.1, need an intermediate upgrade first or a move with Data Pump or transportable tablespaces.
Can we upgrade directly from 12c or 19c to 26ai?
Only from 19c or 21c. Oracle's 26ai Upgrade Guide lists those two as the releases that support direct upgrade. Databases on 12c or 18c go to 19c first, then to 26ai, and must become pluggable databases along the way.
When does Oracle 19c support end?
Per Oracle's Lifetime Support Policy effective October 2, 2026, 19c Premier Support runs to December 2029 and paid Extended Support to December 2032. Oracle updates the policy, so check the current version for your platform.
What is Oracle AutoUpgrade?
AutoUpgrade is Oracle's recommended upgrade tool. Analyze mode reports problems without changing anything, fixups mode applies the safe pre-upgrade fixes, and deploy mode runs the upgrade with checkpoints and a guaranteed restore point. It can also convert a non-CDB into a pluggable database and upgrade many databases from one config file.
How much downtime does an Oracle 19c upgrade need?
An AutoUpgrade run usually needs a few hours, depending on database size, components and the number of invalid objects. A Data Guard rolling upgrade can cut downtime to minutes, and GoldenGate replication to near zero, at more setup and licensing cost.
Do we have to move to multitenant to upgrade past 19c?
Yes. Oracle desupports upgrading a non-CDB to a non-CDB, so a 26ai database runs as a pluggable database inside a container database. AutoUpgrade can convert during the upgrade, or you can convert on 19c first.
Do we need Real Application Testing to upgrade?
No, but it helps. SQL Performance Analyzer and Database Replay are part of Real Application Testing, a separately licensed option for on-premises Enterprise Edition. Without it, we compare execution plans from captured SQL Tuning Sets and application test runs.
How do we roll back a failed Oracle upgrade?
We create a guaranteed restore point before the upgrade and leave the COMPATIBLE parameter at the old value until the business signs off. If checks fail, Flashback Database returns the database to its pre-upgrade state. Data Guard and GoldenGate methods keep the old database available as a second way back.
Should we upgrade to 19c or 26ai?
19c is the lower-risk choice for packaged applications because certification is widest. 26ai has the longer Premier Support runway, to December 2031 per Oracle's policy. Check each application vendor's certification and your readiness for multitenant before choosing.
Next step
Tell us what you need to build or who you need to hire.
A 30-minute call with a senior architect. You leave with a scoped plan or a role profile, whether or not you work with us.