Oracle Database 19c end of life support dates and upgrade options

Architecture

Oracle 19c End of Life: Support Dates and Your Options

Oracle Database 19c Premier Support runs to 31 December 2029 and paid Extended Support to 31 December 2032. What each date changes, the upgrade paths that work for production, and how to plan the move without a rushed cutover.

By RadixTrie1 October 20262 min read

Oracle Database 19c is the long-term release most Oracle estates run today, and its support dates have moved more than once. As things stand, Premier Support for Oracle 19c ends on 31 December 2029 and paid Extended Support ends on 31 December 2032. That sounds like a long runway. For a production database with certified applications, a change freeze calendar and an upgrade that needs rehearsing, it is about the right amount of time to do the job properly, as long as the planning starts now. This article sets out what each date actually changes, the realistic upgrade paths, and how to plan the move.

Oracle 19c end of life dates

Premier Support: until 31 December 2029. New patches, security fixes, Release Updates and full technical support, included in your standard annual support fee.
Extended Support: until 31 December 2032. Patches and security fixes continue, but for an additional fee on top of standard support. This is the date most people mean by Oracle 19c end of life.
Sustaining Support: after that, indefinitely. You can still log a support request and use existing patches, but no new fixes or security updates are produced for 19c.
Older releases such as 12c and 18c are already outside Premier Support. If you are still on one of them, 19c or the next long-term release is the first stop, not the last.

What changes on each date

Nothing switches off. The database starts, queries run and backups complete. What changes is the supply of fixes and what it costs you. Until the end of 2029 you are on the standard support fee with a full patch stream. From 2030 the same patch stream costs more, and the budget conversation tends to arrive at the same time as the auditors' questions. From 2033 any newly found vulnerability in 19c stays open, which auditors, insurers and payment-card assessors treat as a finding regardless of how well the rest of the stack is run.

Your options, ranked

Upgrade to the next long-term release before Premier Support ends. Oracle's next long-term release after 19c is 23ai, which Oracle now brands as Oracle AI Database 26ai. Moving during 2027 to 2029 keeps you on the standard support fee the whole way and gives you the longest runway afterwards.
Stay on 19c and budget for Extended Support. Reasonable when a key application is not yet certified on the newer release. It buys up to three years at a higher cost; it is a bridge, not a destination.
Move the workload to PostgreSQL. For some systems, an end-of-life date is the moment to stop paying for Oracle licences altogether. It is a bigger project than an upgrade, and it suits applications you control rather than packaged software certified only on Oracle. Our <a href="/blog/oracle-to-postgresql-migration">Oracle to PostgreSQL migration guide</a> covers how it is done.
Move to a managed cloud database. Oracle's own cloud services and other managed offerings take version management off your hands, at the price of a new cost model and new network and latency planning.
Accept the risk on a system being retired. For a database that is genuinely being switched off soon, isolation, hardened access and a written risk acceptance can be reasonable. It is the worst option for anything that is staying.

Whichever route you take, the first step is the same: an inventory of every 19c database with its edition, size, options in use, the applications that connect to it, and whether each application vendor certifies the target release.

Upgrade paths that work for production

AutoUpgrade. Oracle's recommended upgrade tool runs the pre-checks, fixups, upgrade and post-upgrade steps, and can be rehearsed in analyse mode first. It is the default choice for an in-place or side-by-side upgrade.
Data Pump or transportable tablespaces. Useful when the upgrade is combined with a platform or storage move, or when you want a clean new database rather than an upgraded one.
Data Guard rolling upgrade or GoldenGate. For systems that cannot take a long outage, replication to a standby on the new release followed by a switchover cuts downtime to minutes.
Plan for multitenant. From 21c onwards Oracle no longer supports the non-CDB architecture, so a 19c database that is still non-CDB has to become a pluggable database as part of the move. Build that into the plan rather than discovering it in the test run.

A plan that fits a production estate

Start with the inventory and the application certifications, because they decide the target release and the timeline. Then build a test environment on the target version with production-like data, run the application and its heaviest reports against it, and compare execution plans, because optimiser changes between releases are where most post-upgrade performance surprises come from. Rehearse the cutover, time it, and keep the old database intact as the rollback until the new one has run a full business cycle. Done this way, an Oracle upgrade is a planned weekend rather than an incident.

This is ordinary work for a senior Oracle DBA and a distraction for everyone else. Our Oracle DBA services cover exactly this: assessment, upgrade planning, rehearsal and cutover, with senior engineers who stay on afterwards under a fixed monthly retainer if you want them to. In South Africa, see our Oracle database support page. If the estate also runs SQL Server, our article on SQL Server 2017 and 2019 end of life covers the Microsoft side.

Running Oracle 19c? Let's map your upgrade before the deadlines do it for you.

TAGSOracleOracle 19cUpgradeEnd of Life