Oracle 19c End of Life: Premier, Extended and Sustaining Support Dates

The short answer

Oracle Database 19c Premier Support ends in December 2029, and Extended Support ends in December 2032. After that, 19c moves to Sustaining Support, which Oracle offers for as long as you license the product but which brings no new patches. 19c is a Long Term Support Release, generally available since April 2019, and these dates come from Oracle's Lifetime Support Policy for Technology Products, effective 2 October 2026.

Nothing switches off in 2026. The first change most 19c estates will feel is narrower: from 1 May 2027, Oracle excludes Java 8 related third-party software from 19c support. The real decision point is 2029, when staying on 19c starts to need Extended Support.

Oracle 19c support dates

Two footnotes in the policy matter for some estates. Premier Support for the AIX PPC32 client and the Linux x86-32 client ends in June 2027. And from 1 May 2027 through the end of Extended Support, Oracle excludes support for Java 8 related third-party software, which mainly affects the 19c ports on AIX, Linux on IBM Z, HP-UX, Solaris and Windows. Java 8 Extended support ends in December 2030, and 19c gets no Java updates after that.

What changes at each date

May 2027: the Java 8 exclusion

Database patches keep coming. What stops is support for issues in the Java 8 third-party components bundled with some 19c ports. If you run 19c on one of the platforms named above and use the embedded Java features, check how much depends on them before then.

December 2029: Premier Support ends

Oracle's Extended Support adds three more years for specific releases, and 19c is one of them. You keep updates, fixes, security alerts and Critical Patch Updates, but Oracle charges an additional fee for the stage, and certification covers existing third-party products and versions rather than new ones. A new operating system release in 2030 may not be certified for 19c.

December 2032: Sustaining Support only

Sustaining Support keeps the support line open and gives you the fixes, Critical Patch Updates and upgrade scripts created while 19c was in Premier and Extended Support. It does not include:

• New updates, fixes, security alerts, data fixes or Critical Patch Updates
• New tax, legal and regulatory updates
• New upgrade scripts
• Certification with new third-party or Oracle products
• The 24-hour response commitment for Severity 1 service requests

In practice, a vulnerability disclosed in 2033 stays open on 19c. Oracle's own term for this stage is Sustaining Support; it does not use "end of service", but this is the point where the release stops receiving new fixes.

Your options

1. Upgrade to Oracle AI Database 26ai

Oracle describes 26ai as the next long-term support release, superseding 19c, and it replaces 23ai. Oracle provides a direct upgrade path from 19c or 21c to 26ai. The policy lists 26ai Enterprise Edition with Premier Support to December 2031 and Extended Support still marked TBD. Oracle's FAQ says a long-term release gets five years of Premier and three of Extended, but the 26ai Extended Support date is not published yet.

Note the overlap: 26ai Premier Support ends in December 2031, two years after 19c Premier. Upgrading buys time on new features and certifications more than on the support calendar. Our post on Oracle 21c and 23ai support dates covers 26ai in more detail.

2. Stay on 19c and buy Extended Support

The right answer for applications certified only on Oracle, packaged software whose vendor supports 19c and nothing newer, or systems you plan to retire before 2032. Only Oracle produces Oracle Database patches.

3. Third-party support for Oracle Database

Several companies support Oracle Database releases without Oracle's patch stream. They can extend the life of 19c past 2032, but ask each how it handles a new CVE on your release. Our Oracle Database comparison sets out what each publishes about itself.

4. Move to PostgreSQL

For applications you control, the 19c deadline is a natural point to leave Oracle altogether. It is a programme measured in months: schema and PL/SQL conversion, data migration, a parallel run and cutover. The Oracle to PostgreSQL migration guide walks through it, and Oracle Database alternatives compares the other targets. If a licence audit is what brought the question forward, read your options after an Oracle licence audit first.

Where OSSeva fits

OSSeva does not support or patch Oracle Database. If you stay on Oracle, Oracle or a third-party Oracle support provider is the right partner. If you decide to leave, OSSeva's Oracle to PostgreSQL offer runs the assessment, ora2pg conversion, data migration, parallel run and cutover, then supports the PostgreSQL cluster from day one on your own servers, VMs, Kubernetes or cloud account. PostgreSQL then sits under one contract with MySQL, MariaDB, Redis, Valkey and Kafka, priced per cluster. The database support cost calculator works from your own numbers; book a discovery call for a quote.

Frequently asked questions

When is Oracle 19c end of life?

Oracle does not set an end-of-life date for 19c. Premier Support ends in December 2029 and Extended Support in December 2032, after which 19c receives Sustaining Support indefinitely, with no new patches.

What is the Oracle 19c end of support date?

December 2029 for Premier Support, and December 2032 for Extended Support. December 2032 is the last month in which Oracle ships new fixes for 19c.

Does Oracle 19c have Extended Support?

Yes. 19c is a Long Term Support Release, and Extended Support runs from January 2030 to December 2032, for an additional fee.

What is Oracle 19c end of service?

Oracle does not use the term. The closest equivalent is the end of Extended Support in December 2032. From then on, Sustaining Support provides technical help and existing fixes only.

Can I upgrade directly from 19c to 26ai?

Yes. Oracle supports upgrades to 26ai from 19c or 21c. Older releases have to reach one of those first.

Should we upgrade to 26ai or migrate to PostgreSQL?

Upgrade when your applications depend on Oracle features or certifications, or when the migration effort outweighs the benefit. Migrate when you control the application code, the Oracle footprint is a cost or audit concern, and you can give the project the months it needs. Many estates do both: upgrade the systems that must stay and move the rest.