Oracle 19c end of life date: what Oracle's policy says, and what ends first

Oracle 19c end of life date, release by release

Oracle's Lifetime Support Policy for Oracle Technology Products, effective 2 October 2026, lists these database dates.

Oracle lists Sustaining Support as indefinite for every release. Checked 27 October 2026 against Oracle's Lifetime Support Policy for Oracle Technology Products. Oracle revises this document, so check any 19c date in a planning deck against the current edition.

Oracle 19c end of life extended support: what each level means

Oracle's Software Technical Support Policies, effective 9 October 2026, define the levels.

• Premier Support is the standard level. For 19c it runs to December 2029.
• Extended Support, when offered, "is generally available for three years following the expiration of Premier Support and only for the terminal patchset release of a program." To get it, "you must continue to pay the technical support fee for SULS/Premier Support and purchase Extended Support." Oracle's footnote puts the 19c Extended Support period at 1 January 2030 to 31 December 2032.
• Sustaining Support lasts as long as you pay, but it "does not include" new program updates, fixes, security alerts or critical patch updates.

So the date that matters for patching is December 2029 if you don't buy Extended Support, and December 2032 if you do. Oracle's policy document mentions no Extended Support fee waiver for 19c. Amazon's RDS page does say "fees waived for Extended Support" beside its 19c Premier date, so if a waiver matters to your budget, get Oracle's terms for your contract in writing.

What ends before 19c does?

Most of the near-term risk in a 19c estate isn't 19c.

21c. Oracle Database 21c is an Innovation Release. Premier Support ends in July 2027, and Oracle offers no Extended Support. A 21c database is on a shorter clock than the 19c ones beside it.

Older releases. 18c and 12.2.0.1 never had Extended Support, 12.1 Enterprise Edition's ended in July 2022, and 11.2's in December 2020. Any of these still running gets no new fixes or security patches.

Java 8 on some platforms. Oracle's footnote says that from 1 May 2027, 19c support "will be excluded for Java 8 related third-party software", mainly affecting the 19c ports on AIX, zLinux, HP-UX, Solaris and Windows. Java 8 Extended Support ends in December 2030, after which 19c gets no Java updates.

HP-UX. Oracle points 19c customers on HP-UX to a separate support statement (Doc ID 3080621.1) for their end dates. On HP-UX, don't assume the table above applies.

Unsupported releases like these turn up on almost any list of legacy system examples. What running them means for audit and security is in the risks of running end-of-life software.

What replaces 19c? Oracle AI Database 26ai

The next long-term release is Oracle AI Database 26ai. Oracle's database FAQ says 26ai "is a long-term support release that replaces Oracle Database 23ai", reached from 23ai by applying the October 2025 release update. It calls 26ai "the next long-term support release of Oracle Database, superseding 19c", with direct upgrade paths from 19c and 21c.

The upgrade has rules worth knowing early. Oracle's 26ai upgrade guide says "AutoUpgrade and Replay Upgrade are the only supported method for upgrading to Oracle AI Database 26ai," with DBUA desupported. Releases after 19c "only use the multitenant architecture", so a 19c database that isn't yet a container database moves to multitenant as part of the upgrade. Traditional auditing is desupported in 26ai in favor of unified auditing, and so are Database Extensions for .NET.

Check your edition. Oracle's policy row covers 26ai Enterprise Edition, and Amazon's RDS documentation says Oracle released 26ai for Linux x86-64 as Enterprise Edition only, without Standard Edition 2.

RDS Oracle 19c end of life: what AWS says

Amazon's RDS for Oracle upgrade overview says major versions "remain available at least until the end of support date for the corresponding Oracle Database release version," and gives these dates for when an upgrade might be required.

Note the License Included row: on RDS, it has the 2029 date, not 2032. AWS says it gives at least 12 months' notice of a required major upgrade, and may then upgrade remaining instances during maintenance windows. Separately, AWS will end support for Amazon RDS Custom for Oracle, a different service, on 31 March 2027. That's a service retirement, not a 19c date.

The real exposure: the PL/SQL and what depends on it

Version dates are the easy part to plan. The harder part is what the database does. In most 19c estates the business logic isn't only in the applications. It sits in PL/SQL packages, triggers and scheduler jobs, and other systems depend on it through database links, views and direct table access. That's what a 26ai upgrade has to carry across, and what any move off Oracle would have to rewrite. Before choosing a date, list:

• the PL/SQL packages, triggers and jobs, and which applications call them;
• database links in and out, and what each one is for;
• applications built on the database, from Oracle Forms and APEX to code in other languages;
• anything using features that change in 26ai, such as traditional auditing;
• which databases are on 19c, and which older releases still run beside them.

Oracle Forms is the common case. Standalone Forms 12c leaves Premier Support in December 2026, years before 19c, as we explain in Oracle Forms end of support. If APEX is on your shortlist, our guide to Oracle Forms to APEX migration covers what moves and what gets rebuilt. And if one DBA holds most of what's known about the packages, capture that knowledge now.

Where the 30-day assessment fits in a 19c estate

Before anyone sets an upgrade date, know what the databases hold. The 30-day assessment is fixed in scope, at a price agreed before we start. Over 30 days we read the PL/SQL packages, triggers, jobs and database links, establish which databases are on 19c and which older releases run beside them, and map what depends on each, from Forms and APEX applications to integrations. We find the hidden architectural debt, such as business rules copied between packages, and flag the security and compliance gaps, starting with anything on an unsupported release.

The report says in plain language what is broken and what it would take to fix it, including what a move to 26ai would touch. Your own team can act on it, or we can do the upgrade as a separate project with its own scope and price. Either way, the report stands on its own. If a version inventory would answer your question, we'll tell you that.

Pick a time to talk about your Oracle estate.