Oracle's Lifetime Support Policy defines three distinct tiers — Premier Support, Extended Support, and Sustaining Support — each with materially different patch entitlements, bug-fix commitments, and certification guarantees. Most enterprises don't understand the difference until a product moves from Premier to Extended and the patches they expected stop arriving. Understanding where your Oracle products sit in the Lifetime Support timeline, what Oracle will and won't fix at each tier, and what the cost implications are is foundational to any Oracle support strategy.
Oracle's Lifetime Support Policy is the framework Oracle uses to define the support lifecycle for each of its products — from the point of general availability through eventual end of all support activity. The policy applies to Oracle Database, Oracle Fusion Middleware (including WebLogic, SOA Suite, Oracle Forms, and related products), Oracle E-Business Suite, Oracle PeopleSoft, Oracle JD Edwards EnterpriseOne, Oracle Siebel CRM, Oracle Java SE, and Oracle's cloud infrastructure and application products.
The policy divides a product's supported life into three sequential phases: Premier Support, Extended Support, and Sustaining Support. Each phase is time-bounded and product-specific — the dates are published by Oracle on the Oracle Lifetime Support Policy page and the Oracle Software Technical Support Policies document, and they vary significantly between products and release versions. What matters for enterprise planning is not just knowing the dates, but understanding exactly what Oracle commits to providing (and what it explicitly withdraws) at each tier boundary.
The Lifetime Support framework was designed by Oracle to create commercial leverage. Products approaching the end of Premier Support are migration targets — Oracle uses Lifetime Support timelines to drive upgrade discussions, new license sales, and cloud migration conversations. Understanding Oracle's incentive structure is as important as understanding the technical definitions of each tier.
Independence statement: Oracle Licensing Experts is not affiliated with Oracle Corporation. The analysis below is based on our team's direct experience advising enterprise buyers through support transitions. We have no commercial interest in which support option you choose.
Premier Support is Oracle's primary, full-service support tier. For Oracle Database, the current version typically receives five years of Premier Support from the date of General Availability. For Oracle Fusion Middleware products and Oracle Applications (EBS, PeopleSoft, JD Edwards), Premier Support periods vary — EBS has historically received extended Premier Support relative to database versions, reflecting Oracle's interest in keeping application customers paying Oracle support while maintaining upgrade pressure.
During Premier Support, Oracle commits to delivering: error corrections (patches for documented software bugs), security patches and Critical Patch Updates (CPUs) published quarterly, certification with new operating systems, hardware platforms, third-party software, and Oracle's own products, access to the My Oracle Support knowledge base and community resources, and Oracle's standard incident management and technical support. This is the tier that most enterprises expect when they sign an Oracle support contract and pay 22% of net license value annually.
The distinction within Premier Support that matters most is the difference between error corrections (bug fixes) and product enhancements. Oracle does not commit to adding new features during Premier Support — the obligation is to fix documented bugs and maintain operational stability. Oracle does release new features during Premier Support, but these are delivered through new versions and patch sets, not as entitlements of the support contract. Enterprises running on Premier Support receive the quarterly CPU security patches, the PSU (Patch Set Update) or RU (Release Update) bundle patches, and individual fixes through the My Oracle Support SR (Service Request) process.
For Oracle Database, the Premier Support path has become increasingly structured around Release Updates (RUs) — quarterly patch bundles that combine critical bug fixes and security patches. Individual one-off patches are still available during Premier Support but increasingly Oracle steers customers toward the RU bundle approach. This is relevant for enterprises using Oracle compliance review and patch management processes, as the Oracle USMM and LMS scripts will detect version and patch level during any audit.
Extended Support is the first paid extension beyond Premier Support. Oracle offers Extended Support for a defined period — typically three years — after Premier Support ends for a specific product release. For Oracle Database 19c, Premier Support ran through April 2024, with Extended Support available through April 2027. For Oracle Database 12.2, Premier Support ended in March 2022 with Extended Support through March 2025. These dates are version-specific and non-negotiable once Premier Support ends.
Extended Support has a cost premium. Oracle's published list price for Extended Support is an additional fee — typically 10% of net license value per year on top of the base 22% annual support fee, bringing the total to approximately 32% during the Extended Support period. In practice, Oracle frequently waives or reduces this Extended Support surcharge for large accounts as a commercial concession during Oracle agreement or renewal negotiations. Enterprises entering Extended Support negotiations should treat this surcharge as negotiable, not fixed.
This is where the Lifetime Support Policy becomes adversarial toward the buyer. During Extended Support, Oracle explicitly reduces its support obligations in ways that are not always communicated clearly. Oracle restricts new platform certifications during Extended Support — Oracle will not certify a product on Extended Support with new operating system versions, new hardware platforms, or new third-party software versions released after the Extended Support period began. This creates a progressive technology lock-in: as new Linux distributions, new server hardware, and new VMware or hypervisor versions are released, they will not be certified for products on Extended Support.
Oracle also narrows its bug-fix commitment during Extended Support. Oracle will provide fixes for severity 1 issues (system down or data loss) but becomes increasingly selective about severity 2 and 3 bugs — deferring fixes to future versions rather than backporting them to the Extended Support version. This means the volume of available fixes declines over the Extended Support period, and the practical support quality degrades compared to Premier Support, even though the cost increases.
Our support cost reduction service includes an independent assessment of whether Extended Support surcharges are justified — and whether third-party support or migration offers a better outcome. Enterprises routinely discover they are paying Extended Support premiums for coverage that doesn't match their actual risk profile.
Sustaining Support is Oracle's minimum-service tier — the final phase before a product version is unsupported entirely. Sustaining Support has no defined end date; it continues indefinitely, which Oracle markets as an advantage. The reality is more complex: Sustaining Support represents a significant withdrawal of Oracle's active support commitment.
Under Sustaining Support, Oracle commits to: access to existing My Oracle Support patches and fixes already published during Premier and Extended Support; access to the knowledge base and existing documentation; and technical support through the SR (Service Request) process. What Oracle explicitly does not commit to: new error corrections or bug fixes for Sustaining Support releases; new security patches or CPUs (existing CPUs remain accessible but new ones will not be backported); new platform certifications; and fixes for newly discovered issues.
The most significant issue with Sustaining Support for enterprise security teams is the absence of new security patches. Oracle's quarterly Critical Patch Updates (CPUs) are not backported to products in Sustaining Support. If a new security vulnerability is discovered — including a critical CVE — Oracle will not release a patch for the Sustaining Support release. This creates a genuine security compliance exposure that many enterprises underestimate when they allow products to drift into Sustaining Support without a clear remediation plan.
For enterprises subject to regulatory requirements — PCI DSS, HIPAA, SOX, GDPR — operating Oracle products in Sustaining Support without compensating controls creates a potential compliance gap that auditors will flag. The Oracle audit defense implications extend beyond licensing: if an enterprise is operating unpatched software due to Sustaining Support limitations, this becomes a legal and regulatory exposure, not just a technical one.
| Support Entitlement | Premier Support | Extended Support | Sustaining Support |
|---|---|---|---|
| Error corrections / bug fixes | Yes — full backport | Severity 1 priority; Sev 2/3 selective | No — new fixes only for future versions |
| Security patches / CPUs | Quarterly (full) | Quarterly (full) | Existing patches only — no new CPUs |
| New OS certifications | Yes | Restricted — only OS versions available at start of Extended | No new certifications |
| New hardware certifications | Yes | Restricted | No |
| New Oracle product interoperability | Yes | Limited | No |
| My Oracle Support access | Full | Full | Existing content only |
| Technical SR support | Full | Full | Available (response times may vary) |
| Typical annual cost (% of NLV) | 22% | 22% + ~10% surcharge (negotiable) | 22% |
The table reveals a critical insight: Sustaining Support costs the same 22% of net license value as Premier Support, but delivers a fraction of the value. Enterprises paying full Oracle support rates for products in Sustaining Support are, in effect, paying for a knowledge base subscription and a technical support line — while receiving no ongoing security patches, no new certifications, and no bug fixes. This is the scenario where third-party support becomes economically compelling: companies like Rimini Street will provide security patches (developed independently) for Sustaining Support products at 50% of Oracle's annual support fee.
The following represents key Lifetime Support timeline milestones based on Oracle's published documentation. Enterprises should verify current dates directly through Oracle's Lifetime Support Policy pages, as Oracle updates timelines periodically.
| Version | Premier Support End | Extended Support End | Status (2026) |
|---|---|---|---|
| Oracle Database 12.1 | July 2018 | July 2021 | Sustaining Support |
| Oracle Database 12.2 | March 2022 | March 2025 | Sustaining Support |
| Oracle Database 18c | June 2021 | June 2024 | Sustaining Support |
| Oracle Database 19c | April 2024 | April 2027 | Extended Support |
| Oracle Database 21c | April 2024 | N/A (non-LTS) | Sustaining Support |
| Oracle Database 23ai | April 2028 (est.) | TBD | Premier Support |
| Product | Premier Support End | Extended Support | Status (2026) |
|---|---|---|---|
| Oracle E-Business Suite 12.2 | December 2031 | TBD | Premier Support |
| Oracle PeopleSoft 9.2 | December 2032 | TBD | Premier Support |
| Oracle JD Edwards E1 9.2 | December 2031 | TBD | Premier Support |
| Oracle Siebel CRM 23.x | TBD | TBD | Premier Support |
The applications picture is more benign than the database picture — Oracle has committed to extended Premier Support windows for EBS 12.2, PeopleSoft 9.2, and JD Edwards 9.2 to reduce customer urgency to migrate to Oracle Fusion Cloud. This is a deliberate commercial decision by Oracle: it needs these application customers to remain on Oracle support (and paying 22% annually) while Oracle builds out Fusion Cloud's functional depth.
Oracle WebLogic and Middleware: The Fusion Middleware suite has a more complex Lifetime Support picture. WebLogic 12.2.1.x is in Sustaining Support as of 2025. WebLogic 14.1.1.x remains in Premier Support through approximately January 2027. Enterprises running WebLogic on Extended or Sustaining Support face the same security patch gap as database customers. Our compliance review maps your full middleware estate against current Lifetime Support dates.
For enterprise IT and procurement teams, the Oracle Lifetime Support Policy creates three distinct planning challenges: security risk management for products in Sustaining Support (which receive no new security patches from Oracle), cost optimization for products in Extended Support (where Oracle's 10% surcharge is often negotiable or avoidable through strategic timing), and migration planning for products approaching the end of Premier Support (where Oracle's account team uses the impending support change as a migration catalyst).
Oracle's account teams are trained to use approaching Lifetime Support end dates as migration triggers. When a key database version is moving from Premier to Extended Support — or from Extended to Sustaining — Oracle will often initiate discussions about upgrading to the current version (which requires new licenses if you're moving to a product not covered by your existing entitlements), migrating to Autonomous Database or OCI (cloud migration), or signing a new Oracle master agreement or ULA to "simplify" the licensing situation. These discussions are commercially motivated. The Lifetime Support date is a fact; the response to that date is a commercial negotiation, not a technical inevitability.
Our contract negotiation service routinely helps enterprises use Lifetime Support transitions as negotiating leverage rather than accepting Oracle's framing. When Oracle needs you to upgrade or migrate (because you're on a version they want to end-of-life), they have an incentive to make the transition attractive. This is leverage — use it.
The Extended Support surcharge is one of Oracle's more negotiable line items. Oracle's standard position is that Extended Support costs an additional 10% of net license value per year. In practice, for accounts spending $500,000 or more on Oracle support annually, Oracle will frequently waive or cap the Extended Support surcharge as part of a broader support or Oracle agreement renewal negotiation. The worst outcome is paying the full surcharge without pushing back — which is exactly what Oracle hopes for when the renewal discussions focus on the Lifetime Support narrative rather than the commercial terms.
The Lifetime Support Policy is one of the primary commercial drivers for third-party Oracle support adoption. Enterprises in two specific situations find third-party support economically compelling: products in Sustaining Support, where Oracle is providing minimal new patches, and products approaching Extended Support renewal, where Oracle's surcharge is creating cost pressure without commensurate value.
Third-party support providers like Rimini Street and Spinnaker Support offer a different value proposition for both situations. For Sustaining Support products, they provide independently developed security patches — testing Oracle-equivalent fixes against the supported release — which addresses the primary objection (security patch gap) at 50% of Oracle's annual cost. For Extended Support products, they offer an alternative to Oracle's surcharge-inflated pricing while maintaining functional support.
The critical analysis — which our support cost reduction service performs — is matching the third-party support decision to your actual product roadmap. If you plan to migrate from Oracle Database 19c to 23ai within two years, the Oracle Extended Support surcharge may be worth paying for the seamless upgrade path Oracle provides. If you plan to run 19c for five more years with no planned Oracle upgrade, the third-party support economics become compelling in year two of Extended Support.
We model the full financial picture — Oracle support cost, third-party support cost, reinstatement risk, migration cost, and compliance risk — for your specific Oracle estate. No agenda: if Oracle support is the right call, we'll tell you that too.
There are several aspects of Oracle's Lifetime Support Policy that Oracle's account teams systematically underemphasise in support renewal conversations. Understanding these is essential for any enterprise making informed support decisions.
Oracle's commitment during Premier Support to provide bug fixes does not mean all bugs will be fixed. Oracle triages support requests based on severity, customer impact, and commercial context. Low-severity bugs in Premier Support products may wait years for a fix, or may be deferred indefinitely to a future release. The reality of Oracle support — regardless of tier — is that Oracle fixes the bugs that affect the most customers and the most severe production situations. Everything else goes into a queue that may or may not result in a fix during the supported period.
Oracle's quarterly CPU (Critical Patch Update) is a cumulative patch bundle — it includes fixes for security vulnerabilities across multiple Oracle products. Enterprises assume that installing the quarterly CPU means they are fully patched. This is not accurate. The CPU covers Oracle's documented vulnerabilities; it does not patch underlying operating system, third-party component, or Java vulnerabilities that Oracle's products depend on. A complete security posture requires layered patching beyond what Oracle's CPU provides. Third-party support providers often make this argument effectively: their security patches for Sustaining Support products are, in practice, as comprehensive as what Oracle provides in the CPU for supported versions.
Oracle markets Sustaining Support as an indefinite safety net — you can stay on it forever. What Oracle doesn't advertise: staying on Sustaining Support indefinitely, with no new security patches and no new certifications, creates a progressive compliance and security exposure that compounds over time. Each year on Sustaining Support, the gap between your Oracle patch level and current security standards widens. For regulated industries, this is not sustainable. The compliance review implications of Sustaining Support should be quantified annually, not accepted as a static baseline.
Our free guide covers the full Oracle support decision framework — Extended Support, third-party support, reinstatement risk, and negotiation tactics for reducing your 22% annual Oracle support bill.
Download the Playbook →Audit alerts, support policy changes, negotiation tactics, and Lifetime Support updates — delivered to enterprise Oracle stakeholders.