Oracle’s Support Lifecycle: Premier, Extended, and Sustaining Support

Oracle’s Lifetime Support Policy defines how long its products receive updates and assistance, which is critical for Software Asset Management (SAM) and licensing professionals to understand. If support lapses, organizations risk security vulnerabilities, compliance issues, and unplanned costs.

This article provides an in-depth, advisory overview of Oracle’s support lifecycle stages – Premier, Extended, and Sustaining Support – and how they apply to major Oracle product families, including Database, Fusion Middleware, E-Business Suite, Fusion Applications, and Java.

We also discuss the cost implications of Extended Support and the risks of relying on Sustainable Support, as well as best practices for avoiding support gaps and unnecessary expenditures.

Oracle Support Lifecycle Overview

Oracle’s support lifecycle is split into three main stages, generally following a product’s release timeline:

• Premier Support is the initial full support period, typically 5 years from a product’s general availability. During Premier, Oracle provides comprehensive updates, patches, and technical support.
• Extended Support: An optional continuation (usually up to 3 additional years) after Premier Support ends, available for specific product releases and purchased for an extra fee (often 10–20% higher than standard support fees)​. Extended Support offers continued critical fixes and updates, but with some limitations.
• Sustaining Support is an indefinite support phase that begins once Premier (and any Extended Support, if applicable) ends. It allows customers to receive basic technical support and access to existing fixes, but no new updates or patches are created for products in this stage​.

The table below summarizes these support levels and their key characteristics:

Note: Oracle’s policy guarantees Premier Support for a defined period (typically 5 years for most products), after which Extended Support may be offered for certain releases, or customers may be downgraded to Sustaining Support.

If Extended Support is not offered (or not purchased), Sustaining Support is the fallback for as long as you maintain your support contract​.

Premier Support

• Comprehensive Updates and Fixes: Oracle provides regular patch sets, bug fixes, and Critical Patch Updates (security patches) as part of Premier Support. This ensures that any newly discovered vulnerabilities or bugs are addressed promptly.
• New Version Certifications: During Premier, Oracle certifies the product with new third-party software, operating systems, and other Oracle products. For example, a database in Premier Support will be certified to run on new OS versions or work with new Oracle middleware releases​. This keeps your environment compatible with evolving technology.
• Regulatory and Legal Updates: Oracle Applications, such as E-Business Suite, receive updates to address changing tax laws, payroll regulations, and other compliance needs during Premier Support. These updates are critical for businesses in regulated industries.
• Full Technical Support: Customers have 24/7 access to Oracle’s technical support team and the My Oracle Support portal for submitting service requests and seeking guidance. Issues of all severities will be investigated, and Oracle will develop new patches or workarounds as needed to resolve problems.
• Upgrade Rights: Premier Support entitles customers to upgrade to newer major releases (if they choose) under their existing support fees. This means you can plan an upgrade to the next version without buying a new license, as long as you have active support.

Premier Support is included in the annual support fee that organizations pay, typically around 22% of the license cost per year for Oracle product support. It is the default and most valuable period of support—Oracle actively improves the product and ensures it remains fully supported in current IT environments.

Extended Support

Extended Support extends the supportability of an Oracle product beyond the Premier period, typically for an additional three years​. It is optional and is offered for specific releases, usually long-term or widely used versions.

Extended Support is essentially an insurance policy for organizations that need more time before upgrading.

Key points include:

• Continuation of Critical Updates: Under Extended Support, Oracle continues to deliver critical bug fixes, security patches, and regulatory updates for applications, just as it does in Premier Support. The product remains supported for severe issues. For example, if a security vulnerability is found after Premier Support ends, Extended Support ensures you still receive a patch for it.
• No New Features or Certifications: Extended Support generally does not include introducing any new features or product enhancements. It’s focused on maintaining the existing version. Additionally, Oracle may not certify the product on newly released third-party platforms during this phase. (You might not get official support running an old version on, say, a next-generation operating system released after Premier ended.)
• Limited Availability: Not all products or versions have extended support as an option, but Oracle typically offers it for major long-term releases. For instance, Oracle designates some database releases as “Long Term Support” (eligible for Extended Support) and others as “Innovation Releases,” which receive only Premier Support for a short period (no Extended Support)​. Always verify if your specific version is eligible.
• Additional Cost: Extended Support comes with an uplift fee on top of your normal support costs. Oracle’s official policy is an extra fee per year of Extended Support, often on the order of 10% for the first extended year and 20% for subsequent years, technology.amis.nl. For example, if your standard support cost is $100,000 per year, the first year of Extended Support might be $110,000, and subsequent years $120,000. (Oracle sometimes adjusts or waives these uplifts for strategic products – e.g., Extended Support uplifts for Java 8 and 11 were waived for several years – but such waivers are exceptions, not the rule.)
• Planning Aspect: Extended Support is designed to be a bridge, giving organizations time to upgrade. Oracle’s documentation emphasizes that while Extended Support is available, customers should use that time to plan their next move, such as an upgrade or migration, rather than staying indefinitely on an aging release. It’s a safety net, not a long-term solution.

In summary, Extended Support can keep your systems supported for a few more years after Premier ends, but it will increase support costs and may still have limitations.

SAM managers should budget for these uplifts and ensure the business is aware of the timeframe. Extended Support typically lasts three years, after which no further updates will be provided.

Sustaining Support

Sustaining Support is Oracle’s final, indefinite support stage for product releases that are past their Premier (and any Extended) Support periods.

Unlike Premier and Extended, Sustaining Support provides no new fixes or patches – it only allows you to continue accessing Oracle’s support resources for the product as they are.

Key characteristics:

• Indefinite Duration: You can remain on Sustaining Support for as long as you continue paying support fees. Oracle does not completely cut off support; you’ll still have access to the old fixes, documentation, and the ability to log service requests​. However, Oracle will not create new patches for issues on a Sustaining-supported release.
• What You Do Get: With Sustaining Support, customers retain access to My Oracle Support, Oracle’s knowledge base, and technical support assistance for troubleshooting​. You’ll also continue to have the right to upgrade to a newer version under your license. Essentially, Oracle will answer questions and help identify existing solutions or workarounds for problems.
• What’s Not Included: No new software updates, security patches, bug fixes, or regulatory updates are delivered under Sustaining Support. Any fixes or patches created during the Premier or Extended phase are available. Still, if a new defect or security vulnerability is discovered in the old release while it is in Sustaining Support, Oracle’s answer will be to upgrade to a newer supported release; they will not issue a patch for the old codebase. Additionally, Oracle stops certifying the product against new third-party software or platforms once it enters Sustaining Support​. This means over time, the product may become incompatible with newer technology or fail to meet new compliance standards.
• Operational Risk: Relying on Sustaining Support carries significant risk. Since you haven’t received any new patches, your system could become vulnerable to security threats. For example, if a critical security flaw is found in an Oracle Database version that’s in Sustaining Support, you would not get a patch, potentially leaving your database exposed. Similarly, business applications like E-Business Suite on Sustaining Support will not receive updates for new tax laws or payroll regulations, which can jeopardize business operations. Essentially, you are running on “frozen” software; any new issues must be solved by upgrading or other means.
• Costs: There is no additional fee uplift for being on Sustaining Support – you generally pay the same annual support fee. However, organizations might question why they are paying full support costs if they aren’t receiving updates. Some choose to drop Oracle support at this stage or seek support from third-party providers, but doing so has its trade-offs, including the loss of upgrade rights and Oracle assistance.

Sustaining Support is a last resort when upgrading is not immediately possible. If you need active maintenance, it’s always preferable to be on Premier or Extended Support. Running on Sustaining Support should trigger a discussion in IT about how to mitigate the lack of updates (such as tightening security or isolating the system) and accelerate upgrade plans.

Product Lifecycle Examples by Category

Oracle’s support policy applies across databases, middleware, applications, and even programming platforms like Java – but each category has its nuances.

Below, we outline how Premier/Extended/Sustaining support timelines play out for key Oracle product families:

Oracle Database

Oracle Database releases follow the 5+3 year support pattern for long-term releases. Oracle typically designates certain releases as Long-Term Support (LTS), which receive the full Premier and Extended Support periods, and other intermediate releases as Innovation Releases with shorter support periods.

For example:

• Oracle Database 19c – an LTS release – was released in 2019 and initially came with Premier Support for approximately 5 years (through the end of March 2023) and the option of Extended Support up to March 31, 2026. (Oracle later extended 19c’s support timeline further, recognizing its importance as a long-term release – as of late 2024, Premier Support for 19c is extended into 2026 and Extended Support into 2027 and beyond​.) Always check Oracle’s latest support roadmap for updates.) After Extended Support, 19c will no longer receive new patches – it will enter Sustaining Support.
• Oracle Database 21c – an Innovation Release – illustrates a different case. As an innovation release, it had Premier Support for a shorter period (two years from its 2021 launch) and no Extended Support phase; it transitioned to Sustaining Support by design. Oracle expects customers on innovation releases to upgrade to the next release (for example, to 23c, the next long-term support release) rather than staying on 21c in the long term.
• Older Releases—To put the lifecycle into perspective, Oracle Database 11g R2’s Premier Support ended in 2015, but Extended Support was offered through 2020 (with some fees waived in certain years), after which it transitioned to Sustaining. Oracle Database 12c (12.1) Premier ended in 2018. Extended Support ran for a few more years, with options like “Market Driven Support” extending limited fixes into 2022. Now, those versions are in Sustaining. Each version’s timeline is published in Oracle’s support matrices.

Implications for SAM Managers: For databases, it’s crucial to track which version is in use and its support dates. If your organization is running an Oracle Database version nearing the end of Premier Support, you should plan an upgrade to an LTS release (such as moving to 19c or 23c) before incurring Extended Support fees. Databases underpin critical apps, so running them without security patch support (Sustaining Support) is a high risk.

Budget for Extended Support only as a contingency or last resort – upgrading to a supported release is usually more cost-effective in the long run than paying 20% extra for support on an old version.

Oracle Fusion Middleware

Fusion Middleware (FMW) includes products such as WebLogic Server, Oracle SOA Suite, and Oracle Reports. These “middleware” products, which often serve as application servers or integration layers, also adhere to the Lifetime Support Policy.

• FMW product versions typically receive 5 years of Premier support and 3 years of Extended Support, similar to the database. For instance, Oracle WebLogic Server 12c (12.2.1.4, part of FMW 12c R2) had Premier Support through December 2021 and Extended Support was offered through 2023. Newer WebLogic releases (14c) would then take over. Another example: Oracle Forms and Reports 12.2.1.4 is slated to have Premier Support until 2026, with likely a limited Extended Support into 2027,​community. These timelines align with Oracle’s plan to update the middleware stack or encourage moves to cloud alternatives in that timeframe.
• Just as with the database, certain middleware versions are designated for long-term support. Oracle typically aligns Fusion Middleware support with the Database, where possible (e.g., a middleware release that supports Oracle Database 19c likely has a similar support window).
• It’s important to note dependencies: If your middleware is on a version that goes out of support, it may also limit the database or applications you can run on it. For example, an older WebLogic might not be certified with a newer Java version once it’s out of Premier Support.

For SAM and IT managers, the advice is to maintain your middleware on supported releases alongside your databases. If you plan a database upgrade, check compatibility with your middleware and vice versa.

Coordinate their lifecycles so you’re not stuck paying Extended Support for one because the other forces you to stay on an older version. Include middleware products in your Oracle support roadmap review, as they can sometimes be overlooked until a critical patch is needed and is found to be unavailable on an outdated version.

Oracle E-Business Suite (EBS)

Oracle E-Business Suite, a flagship ERP and enterprise applications suite, has a slightly unique lifecycle due to Oracle’s Applications Unlimited pledge.

Oracle has committed to support the latest EBS 12.2 version for an unusually long time under Premier Support:

• EBS 12.2 Continuous Innovation: Oracle EBS 12.2, released in 2013, follows a continuous innovation model, where Oracle delivers updates, such as new features and regulatory patches, without requiring a major version upgrade. Oracle has extended Premier Support for EBS 12.2 through at least 2035 (and likely beyond). This means EBS 12.2 users can stay on that release and continue to receive updates and patches for many years without needing Extended Support or an upgrade. Oracle’s support roadmap for EBS explicitly states Premier Support for 12.2 is available through 2035. There is currently no defined end date for 12.2 Sustaining Support because it is so far in the future.
• EBS 12.1 and earlier: In contrast, EBS 12.1.3 went out of Premier Support in December 2021 and entered Sustaining Support in 2022. claremont.co.uk​claremont.co.uk. Oracle did offer Extended Support for 12.1 for a few years (up to 2021) and even a paid Market Driven Support extension for 2022-2023 for critical fixes. However, as of 2022, EBS 12.1 no longer receives new updates. Customers remaining on 12.1 face a significant risk (no new security, tax, or regulatory patches after 2021). The clear best practice was to upgrade to 12.2, which many organizations have done to regain Premier Support.

Key points for EBS: Oracle’s strategy is to encourage users to upgrade to 12.2 and keep them there with continuous patches, effectively staying in Premier Support indefinitely. If you are on 12.2, ensure you apply the regular update patches that Oracle releases.

This will keep you compliant and allow you to access the newest features, which are released as updates, not as a new version. If you are on an older EBS release, consider that staying on Sustaining Support is not viable in the long term, especially for financials and HR modules that must be kept up to date with legislation.

The cost of Extended Support for EBS 12.1 (before 2022) was high, and now the only options are costly, limited support or upgrading – a situation to avoid by timely upgrades in the future.

Oracle Fusion Applications

“Fusion Applications” refers to Oracle’s next-generation application suites, such as Oracle Fusion ERP, HCM, and CRM, which eventually evolved into Oracle Cloud Applications. These products were introduced around 2011–2012 as on-premises or hosted solutions and have since largely transitioned to Oracle’s SaaS (Software as a Service) model.

The support lifecycle for Fusion Applications had some key differences:

• Oracle provided Premier Support for on-premises Fusion Applications 11g releases for several years. For example, Fusion CRM 11.1. x or Fusion HCM 11.1.x, released in 2011, had Premier Support until approximately 2019. However, Oracle did not offer Extended Support for most of these early Fusion Application releases – the official policy showed “Extended Support: Not Available” for them​. The expectation was that customers would move to the newer cloud-based versions or continuous innovation releases rather than stick with the old version beyond Premier. After Premier Support ended, those with on-premises Fusion Apps could only obtain Sustaining Support (or custom support arrangements).
• Now that Fusion Applications are primarily delivered as cloud services (Oracle Cloud Applications), Oracle handles updates using a continuous delivery model. For instance, incremental updates occur quarterly. In the cloud context, customers don’t directly deal with Premier or Extended support phases – Oracle ensures the service is always on a supported version. But for licensing professionals dealing with any remaining on-premises Fusion Application installations, be aware that those legacy versions are likely in Sustaining Support by now if not upgraded. Oracle Fusion Apps customers should plan a transition to Oracle’s cloud services or to Oracle’s latest release train to avoid running unsupported systems.

Bottom line: If your organization has Oracle Fusion Applications on-premises, check their support status immediately – many have already fallen out of Premier Support.

It may be necessary to plan a migration to Oracle’s cloud (Fusion SaaS) or another supported platform, as Extended Support is not an option for most of these products.

For cloud/SaaS Fusion users, ensure you understand Oracle’s update policies, which functionally replace the old support timelines. These policies require you to take updates on Oracle’s schedule to remain supported.

Oracle Java (Java SE)

Oracle Java is a special case, but it is very important for license management. Oracle’s Java SE (Standard Edition) platform now follows a support model similar to other Oracle products, especially after Java 8:

• Oracle designates certain Java versions as LTS (Long-Term Support), currently including Java 8, Java 11, and Java 17, among others. These have Premier Support for at least 5 years after release and Extended Support for up to 8 years or more. For example, Java SE 8, released in March 2014, had Premier Support until March 2022, and Extended Support is available until at least December 2030. Java SE 11 (released in 2018) had Premier Support through September 2023, with Extended Support offered until January 2032. Oracle’s Java roadmap continues this pattern (Java 17 is LTS with Premier until 2026, etc.).
• Importantly, Oracle changed Java licensing for business use such that only customers with a Java SE Subscription (or another Oracle license that covers Java) receive updates beyond the public update period. Essentially, paying for a Java subscription is similar to having Premier or Extended Support entitlements. When Java 8’s public (free) updates ended in 2019, only those with support contracts could get further security patches. With the LTS schedule, once Premier Support ends for a Java version, you must have Extended Support (via subscription) to continue receiving patches. Oracle has generously waived the Extended Support uplift fees for Java 8 and 11 for several years. This means that customers with an active subscription pay the standard rate, not an extra fee, through those dates. However, you still need a subscription to receive any updates.
• If you choose not to pay Oracle for Java support, you are effectively on Sustaining Support (or out of support) for that Java version, meaning no new security fixes. This can be risky, as Java is a common target for vulnerabilities. Alternatives include moving to newer free releases more frequently (which can be disruptive) or using third-party OpenJDK distributions that provide updates. However, many enterprises stick with Oracle’s long-term support (LTS) releases and budget for Java support to ensure continuous patching.

For SAM managers, managing Oracle Java means tracking those LTS dates and ensuring the organization either upgrades in time or maintains subscriptions.

For example, since Java 11’s Premier Support ended in 2023, if the company is still running Java 11 in production, you should verify you have the Extended Support (Java SE Subscription) in place to receive patches through 2032 – or plan the upgrade to Java 17 or 21 (next LTS versions) before support lapses.

Treat Java like any other Oracle product regarding lifecycle planning; it’s widely installed and can become a compliance and security pain point if overlooked.

Cost Implications of Extended Support

Extended Support can significantly increase the cost of maintaining Oracle systems, which is a major concern for IT budget planning.

Some key cost considerations include:

• Uplift Fees: As noted, Oracle typically charges a premium on support fees during Extended Support. The standard uplift is 10% for the first year after Premier, and 20% for the second and third years​. If your annual support bill for a product is large, this percentage increase can amount to a substantial dollar figure. Multiply that across multiple Oracle products that fall out of Premier Support, and the budget impact becomes notable.
• Compound Costs Over Time: Extended support fees are usually calculated based on the current support fee. This means that if your support costs rise year over year (due to inflation adjustments or increased license counts), the 10–20% uplift is based on an increased base in later years. Essentially, the longer you stay on Extended Support, the more you may pay cumulatively, especially in years 7 and 8. It often costs tens of thousands, or even millions, extra to prolong support for an aging system.
• Budget vs. Upgrade Trade-off: Organizations should weigh the cost of Extended Support against the cost of performing an upgrade. In many cases, the money spent on 1–2 years of Extended Support fees might equal or exceed the cost of a migration project to a new version, when factoring in resource time, testing, and other expenses. While upgrades carry upfront costs and effort, they restore you to Premier Support, with no additional fees and all the benefits of new features and optimizations. Extended Support is purely a cost to delay that upgrade.
• Unplanned Extended Support: Sometimes, organizations find themselves forced into Extended Support because an upgrade project falls behind schedule or a legacy system cannot be updated in time. This unplanned expense can mess up IT’s financials. It’s much better to anticipate it. For instance, if you know your Oracle Database or EBS will reach end-of-Premier support next year, decide now whether you will upgrade or require a year of Extended Support, and secure the budget in advance. It is easier to justify funding an upgrade when you can compare it to the high alternative cost of not upgrading.
• Volume Discounts or Waivers: Oracle occasionally offers concessions – for example, they might waive Extended Support fees for a year as a courtesy, as seen with some database versions and Java​, or for customers who quickly adopt a cloud service. Don’t rely on this, but SAM managers can always ask Oracle reps if any fee waivers or promotions apply (especially if the product’s next version was delayed by Oracle, as happened with Database 19c’s timeline). This could save money, but still assume the worst-case (full fees) in planning.

In summary, Extended Support can protect your operations at a price. It should ideally be part of a deliberate strategy (i.e., “we choose to pay for one extra year of support while completing our upgrade”) rather than a surprise.

Manage this by tracking support end dates and quantifying the cost of not upgrading on time. Also, remember to account for all Oracle products – it’s not uncommon to upgrade the database but forget that an associated middleware component or older Java version might also incur extended support fees if left behind.

Operational Risks of Sustaining Support

Running mission-critical systems on Sustaining Support is fraught with risk. While it might be tempting to avoid the cost of upgrades or Extended Support, the downsides include:

• Security Vulnerabilities: Perhaps the biggest risk, no new security patches on Sustaining Support means your system will accumulate known vulnerabilities over time. Oracle releases Critical Patch Updates quarterly under Premier or Extended; if you stop receiving them, any newly discovered exploit in Oracle or related components can be used against your environment. This is especially dangerous for databases, which hold sensitive data, and Java, which is ubiquitous on user desktops and servers. Being on Sustaining Support could eventually violate security policies or regulations (e.g., PCI-DSS, HIPAA) that require up-to-date vendor support.
• Compliance and Regulatory Gaps: Many Oracle applications, such as EBS and PeopleSoft, require regular updates for legal compliance, including tax codes, financial regulations, and HR laws by country. If you’re on Sustaining Support, Oracle will not deliver those updates​to you. Your system could become non-compliant, forcing you to use manual workarounds or exposing the company to legal penalties. For example, tax calculation in EBS might be wrong if you haven’t applied updates reflecting new tax law changes post-2021, because Sustaining Support clients didn’t get those patches.
• Lack of Bug Fixes: If a serious bug is discovered in your software (especially a Severity 1 issue that takes a system down), Oracle will not create a patch for you once you’re in Sustaining Support. At best, they might suggest an existing patch (if the bug was known earlier) or a workaround. You might have to invest internal effort to fix or mitigate the issue, or be forced into an emergency upgrade. This unpredictability can wreak havoc on operations. During Premier/Extended, you have an assurance that Oracle will address new issues; under Sustaining, that safety net is.
• Unsupported Environment: Over time, the rest of your IT environment advances – new browsers, new operating systems, and new integrations. An Oracle product on Sustaining Support will not be certified or supported on these new technologies​. For instance, you might not be able to apply an OS upgrade or a new Java update on a server because Oracle won’t guarantee the old application works with it. This can freeze your entire stack on older versions, compounding technical debt. Eventually, you may hit a wall where hardware or other software forces a change that the old Oracle version can’t accommodate.
• Diminished Support Help: Even though you can contact Oracle Support under Sustaining, their ability to help is limited. They will refer to existing knowledge and likely advise upgrading. In effect, you’re largely on your own for any new challenges. Third-party support providers (such as Rimini Street and Spinnaker) often target this scenario by offering support for older Oracle versions, sometimes with the promise of creating new fixes themselves. Some companies consider third-party support to save costs, as Oracle only offers Sustaining Support. However, moving to third-party support typically means ending your Oracle support contract (and losing future upgrade rights), so it’s a decision to weigh carefully from a licensing perspective.

In short, relying on Sustaining Support introduces operational risk that can far outweigh the short-term savings of deferring an upgrade. It should be seen as a temporary state, if it’s used at all. If you find a system in Sustaining Support, prioritize developing an exit plan, such as upgrading to a supported version or retiring and replacing the system.

Best Practices for Managing Oracle Product Lifecycles

Managing Oracle product lifecycles is a proactive process that involves coordination between technical teams and asset management.

Here are some best practices to ensure you stay in supported status without overspending:

• Maintain an Oracle Support Calendar: Keep an up-to-date inventory of all Oracle products in use, including database versions, middleware components, application versions, Java versions, and more, along with their corresponding Premier Support end dates. Many organizations create an “Oracle support timeline” dashboard. Review Oracle’s Lifetime Support Policy documents annually for changes. This way, there are no surprises – you can see, for example, that “Database X will leave Premier Support in Dec 2025” well in advance.
• Align Upgrade Plans with Support Deadlines: Use the support calendar to drive upgrade project timelines. Aim to complete upgrades before Premier Support expires. For large applications, such as EBS or database upgrades, that can take many months, start planning one to two years of the deadline. This lead time ensures you’re not scrambling and paying for Extended Support just because the project slipped. Many companies have an internal policy that all systems must be either under Premier Support or in an active upgrade process at all times.
• Prioritize Long-Term Support Releases: When choosing which version to upgrade to, opt for the releases with the longest support period. For instance, if Oracle designates a version as an LTS (like Database 19c or 23c, Java 17, or WebLogic 14c), adopting it means you’ll get the full five years of Premier support and the option for Extended support if needed. Avoid deploying an innovation release or a 0.0 version that may have shorter support, unless you have a specific need and a plan to move off it quickly.
• Budget for the Inevitable: Despite best efforts, you might occasionally need Extended Support. Treat Extended Support fees as a risk in your budget forecasts. It’s better to have funds earmarked “just in case” than to be caught off guard. If you manage to upgrade in time and don’t need Extended Support, that budget can be freed up for other projects or saved. But if something like an unexpected dependency delays an upgrade, having budget ready for an extra year of support ensures continuity.
• Leverage Oracle’s Continuous Innovation (for Applications): If you use Oracle Applications Unlimited products (e.g., EBS 12.2, PeopleSoft 9.2, JD Edwards 9.2), understand the continuous release model. Apply regular update patches that Oracle provides (usually released annually or quarterly) to stay up to date. This avoids ever facing a hard end-of-support deadline because you’re essentially always in Premier Support on the latest update of that release. The trade-off is that you must keep up with patching, but Oracle packages these to be easier than a full upgrade. Many enterprises have adopted a routine patch cycle for EBS 12.2, for example, treating it as a maintenance activity to avoid falling behind.
• Consider Cloud/SaaS for Certain Workloads: Oracle is promoting its cloud offerings, including Database Cloud Services and Oracle Cloud Applications for ERP and HCM, which come with the benefit of Oracle handling the infrastructure and updates. If keeping up with on-premises upgrades is burdensome, evaluate whether moving to Oracle’s cloud versions could alleviate the lifecycle management burden (while still meeting requirements). Be mindful of licensing impacts, but in some cases, SaaS can eliminate the need to track support dates for that product (Oracle ensures it’s up to date). This doesn’t work for all scenarios, but it can be part of a modernization strategy.
• Stay Engaged with Oracle Account Teams: Oracle often communicates support policy changes, new product roadmaps, or upgrade advisories through account representatives or webinars. By staying engaged, you may learn about extensions, such as the extension of Database 19c support, or new upgrade tools that ease the process. Oracle also sometimes provides incentives or workshops for customers to upgrade, as it’s in their interest too. Use those resources – they can help reduce cost and effort for you.
• Testing and Compatibility Checks: When planning an upgrade, also plan sufficient testing, especially for complex environments. One reason companies avoid upgrading is the fear of breaking integrations or customizations. A best practice is to establish a testing environment and process well in advance for new Oracle versions. This builds confidence that upgrades can be done with minimal disruption, making the organization less inclined to procrastinate past support deadlines.
• Contingency Plans: If an upgrade absolutely cannot be completed on time (due to business constraints or application vendor support issues, etc.), have a contingency plan. For example, decide if you will a) pay for Extended Support for a defined period, b) seek a third-party support provider for interim support, or c) accelerate the decommission/replacement of that system. This kind of decision should involve risk assessment (security, operational impact) and cost analysis. It’s better to consciously choose a path than to drift into Sustaining Support without a plan.

By following these practices, SAM managers and IT leaders can avoid the scramble for last-minute support extensions or the peril of unsupported systems. The key is proactive planning and communication—knowing what’s coming and having a strategy in place.

Recommendations

In summary, Oracle’s Premier, Extended, and Sustaining Support stages require careful navigation.

Here are actionable recommendations to manage your Oracle assets effectively in line with support timelines:

• Map Your Oracle Portfolio: Create a detailed list of all Oracle products and their corresponding versions in use, noting their Premier Support end dates. Update this list at least annually using Oracle’s official Lifetime Support documentation. This visibility is the first step in preventing surprises.
• Plan Upgrades Well Ahead: Treat the 5-year Premier Support window as a countdown. Initiate upgrade projects 12 to 24 months before a product’s Premier Support expires. This ensures you complete the transition while still covered, avoiding costly Extended Support or risky Sustaining periods.
• Use Extended Support Strategically (If At All): If you must utilize It, time-box it. For example, plan to use Extended Support for no more than one budget cycle while finishing an upgrade. Secure the necessary approvals for the extra fees as soon as possible. Always compare the cost of Extended Support vs. accelerating the upgrade – in many cases, the upgrade is the better investment.
• Avoid Running Critical Production Systems on Sustaining Support: As a policy, avoid running critical production systems on Sustaining Support. If you find any system has slipped into Sustaining Support, flag it as high risk and prioritize remediation. The business should be made aware that continuing to run without vendor patches is an exception that requires sign-off due to its potential impact on security, compliance, and reliability.
• Stay Current on Patches: Even within the Premier Support phase, apply Oracle’s patches and updates regularly. This not only keeps you secure but also makes future upgrades easier, since you’ll have the latest patch set as a baseline. For applications like EBS 12.2 or databases, incremental patching can often be done in a rolling or online manner. Regular maintenance helps avoid technical debt that can complicate upgrades down the road.
• Leverage Oracle’s Long-Term Support Releases: Standardize on versions like Oracle Database Long-Term Releases (e.g., 19c, 23c) or Java LTS (11, 17) for your deployments. These give you the maximum support duration and stability. Skip interim versions unless you specifically need their features. Even then, have a plan to move to the next Long-Term Support (LTS) version when it becomes available. This approach reduces the frequency of major upgrades.
• Monitor Oracle’s Announcements: Oracle occasionally extends support timelines or changes policies (for example, the extension of EBS 12.2 Premier Support to 2035, or adjustments to Database release schedules). Keep an eye on Oracle support notices, blogs, or user group announcements. Adjust your plans if Oracle provides a longer runway, but don’t assume extensions will always be available.
• Coordinate with the Licensing Strategy team: When planning upgrades, involve your licensing team. Ensure that your licenses cover the new versions. Usually, they do if you have support, but for example, moving to a cloud service might require a new contract. Verify if any end-of-support means an older product can be terminated to save maintenance fees (for instance, after migrating off an old Oracle product, don’t forget to cancel its support contracts). Aligning lifecycle and licensing can also present opportunities to optimize costs.
• Educate Stakeholders: Communicate these support timelines and strategies regularly to business and IT stakeholders. Often, leadership outside of IT might not understand why an upgrade is needed “so soon” after the last one. Explaining the Oracle support policy and the costs and risks of not upgrading can help secure buy-in and budget for timely projects. It’s much easier to get funding for an upgrade when the alternative is highlighted as either paying 20% more for support or risking unsupported systems.

By following these recommendations, SAM managers and IT leaders can stay ahead of Oracle’s support deadlines, optimize support costs, and avoid the pitfalls of lapsing into unsupported territory.

The goal is to maximize the value of Premier Support (which you’re entitled to as part of maintenance) and minimize reliance on Extended or Sustaining Support.

Through prudent planning and proactive management, you can ensure your Oracle environment remains both fully supported and cost-effective throughout its lifecycle.

Do you want to know more about our Oracle Advisory Services?

Please enable JavaScript in your browser to complete this form.

Name *

Email *

Company

Message *

Submit