Oracle 19c End of Life: Support Ends 31 December 2029 (Extended to 2032)

Oracle Database 19c Premier Support ends on 31 December 2029 and paid Extended Support ends on 31 December 2032. After that only Sustaining Support remains, which brings no new security patches. Oracle moved these dates out in November 2024, so pages that still say April 2024 or April 2027 are quoting the old timeline.

One detail in Oracle's current policy matters for planning: from 1 May 2027 Oracle excludes Java 8-related third-party software from 19c support, mainly on the AIX, zLinux, HP-UX, Solaris and Windows ports, and 19c receives no Java updates after December 2030. The section on the Java 8 note below explains what that does and does not cover.

Checked against Oracle's Lifetime Support Policy: Oracle Technology Products (PDF, effective 2 October 2026) on 16 October 2026. Updated 16 October 2026.

Oracle Database 19c is the long-term release most Oracle estates run today, and its support dates have moved more than once. Six years 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, why the dates moved, what the Java 8 footnote means, the realistic upgrade paths, and how to plan the move.

19c (long-term release): generally available April 2019; Premier Support ends 31 December 2029; Extended Support ends 31 December 2032; then Sustaining Support, indefinitely, with no new fixes
21c (innovation release): generally available August 2021; Premier Support ends July 2027; Extended Support not offered; then Sustaining Support
26ai (long-term release, formerly 23ai): generally available October 2025; Premier Support ends December 2031; Extended Support date to be announced
18c: generally available July 2018; Premier Support ended June 2021; Extended Support not offered; Sustaining Support only

Oracle's public policy PDF gives months. The exact days, 31 December 2029 and 31 December 2032, come from My Oracle Support note 742060.1, Release Schedule of Current Database Releases (login required), and Oracle's Mike Dietrich confirmed them publicly on 20 November 2024. Oracle's own summary of the three support stages is on its Lifetime Support Policy page.

Nothing switches off. The database starts, queries run and backups complete. What changes is the supply of fixes and what it costs you. Until 31 December 2029 you are in Premier Support, which Oracle describes as maintenance and support for five years from general availability: updates, fixes, security alerts, critical patch updates and certification with most new third-party products, all within the standard support fee. From 1 January 2030 the same patch stream continues under Extended Support, which Oracle's policy says is provided 'for an additional fee' and may not include certification with some new third-party products; the budget conversation tends to arrive at the same time as the auditors' questions. From 1 January 2033 only Sustaining Support remains, which by Oracle's definition does not include new updates, fixes, security alerts, data fixes or critical patch updates. Any vulnerability found in 19c after that stays open, which auditors, insurers and payment-card assessors treat as a finding regardless of how well the rest of the stack is run.

Until November 2024 Oracle's published timeline for 19c ended Premier Support in April 2024 and Extended Support in April 2027. Many estates planned around those dates, and many of the pages that still rank for this question were written against them. On 19 November 2024 Oracle revised the schedule in My Oracle Support note 742060.1: Premier Support to 31 December 2029 and Extended Support to 31 December 2032. Oracle's Lifetime Support Policy document now carries the same dates.

What it means in practice: 19c is the release to stay on until your application vendors certify 26ai, the next long-term release, and there is no reason to rush an upgrade to meet a 2027 date that no longer exists. It does not mean the work has gone away. A production Oracle upgrade still takes a year of inventory, certification checks, rehearsal and a planned cutover, and Premier Support now ends in a little over three years.

Footnote 3 of Oracle's policy document reads, in part: for customers running Oracle Database 19c, during the Premier Support period of 1 May 2027 through 31 December 2029, and the Extended Support period from 1 January 2030 through 31 December 2032, 'support will be excluded for Java 8 related third-party software', which 'primarily impacts the Oracle Database 19c ports (i.e., on AIX, zLinux, HPUX, Solaris, Windows)'. It adds that 'Java 8 Extended support ends December 2030 and Oracle Database 19c will no longer receive updates for Java after that date', and points HP-UX customers to a separate support statement (Doc ID 3080621.1).

In plain language: the database itself stays supported to the dates above. What falls out of support from 1 May 2027 is third-party software in the 19c stack that depends on Java 8, and the platforms most exposed are the non-Linux ports. Oracle's Mike Dietrich has said publicly that the embedded Oracle JVM is not affected and that the note concerns external Java-related libraries, but the policy text is what Oracle Support will apply, so confirm it for your platform. The questions to ask now: which platform each 19c database runs on, which third-party components in the stack depend on Java 8, and whether the application vendor has a plan for them before May 2027. On Linux x86-64 the exposure is usually small; on AIX, Solaris, HP-UX and Windows it needs an answer.

1. Upgrade to the next long-term release before Premier Support ends. Oracle's next long-term release after 19c is 26ai, formerly branded 23ai, with Premier Support to December 2031. Moving during 2027 to 2029, once your application vendors certify it, keeps you on the standard support fee the whole way and gives you the longest runway afterwards.

2. 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 an additional fee; it is a bridge, not a destination.

3. 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 Oracle to PostgreSQL migration guide covers how it is done.

4. 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.

5. 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.

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 supports only the multitenant 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.

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.

Two dates. Premier Support ends on 31 December 2029 and paid Extended Support on 31 December 2032, per Oracle's Lifetime Support Policy for Oracle Technology Products. When people say Oracle 19c end of life they usually mean the second date, after which only Sustaining Support remains and no new security patches are produced.

Yes, fully. Oracle 19c is in Premier Support until 31 December 2029 at the standard support fee, with Release Updates, security patches and full technical support. Nothing about the 2026 position requires an urgent move; what it requires is a dated plan, because the next long-term release needs vendor certification before you can move to it.

Oracle's policy defines three stages. Premier Support is five years from general availability with updates, fixes, security alerts and critical patch updates, plus certification with most new third-party products. Extended Support adds up to three years for specific releases for an additional fee, with the same patch stream but possibly without certification for some new third-party products. Sustaining Support runs for as long as you license the product, with technical support and the patches already released, but no new fixes, security alerts or critical patch updates.

Yes. Oracle's policy states that Extended Support is provided 'for an additional fee' on top of the standard support fee; the amount is set out in Oracle's Technical Support Policies and your contract, so ask your Oracle account team for the figure that applies to you. For 19c the Extended Support period runs from 1 January 2030 to 31 December 2032.

26ai. Oracle 21c is an innovation release whose Premier Support ends in July 2027 with no Extended Support offered, so it would be out of support about two and a half years before 19c is. Oracle 26ai, the long-term release formerly branded 23ai, has Premier Support to December 2031. Move when your application vendors certify 26ai, and not before.

Because that was the published date until November 2024. Oracle's earlier timeline had Premier Support ending in April 2024 and Extended Support in April 2027. On 19 November 2024 Oracle moved them to 31 December 2029 and 31 December 2032, and its current policy document (effective 2 October 2026) carries the new dates. Pages, forum threads and vendor roadmaps written before then are out of date.

If your 19c databases run on Linux x86-64, probably little. If they run on AIX, zLinux, HP-UX, Solaris or Windows, from 1 May 2027 Oracle excludes Java 8-related third-party software from support, and after December 2030 19c receives no Java updates at all. Identify the Java 8-dependent components in the stack, ask the application vendor for its plan, and treat it as one more reason to have the 26ai certification conversation early.

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, delivered through our remote DBA services wherever the estate runs. In South Africa, see our Oracle database support page. A database health check is the usual first step. If the estate also runs SQL Server, our articles on SQL Server 2019 end of life (8 January 2030) and SQL Server 2017 end of life (12 October 2027) cover the Microsoft side. Every one of our database services is delivered by the engineer who does the work.

Related reading: Oracle to PostgreSQL Migration: What Actually Takes the Time · Oracle Database Support in South Africa: Keeping Licensed Estates Healthy and Compliant · SQL Server 2019 End of Life (8 January 2030): Dates, Risks and Your Options · The Database Health Check: What a Good One Covers and What It Finds