Oracle Annual Technical Support (ATS) is one of the most consistently frustrating line items in an enterprise technology budget. The charge — 22% of net license fees per year — continues regardless of whether you are actively upgrading, actively using Oracle's support services, or even still running the product in production. It increases by 3–8% annually in most agreements. And Oracle's standard terms make cancelling or reducing support extremely difficult without jeopardising access to security patches and future upgrades.
For a large enterprise with a $20M Oracle license estate, this means $4.4M in annual support charges — for software that may be a decade old and running in maintenance mode. Over five years, that's $22M in support costs for software where the primary value is patch availability, not active development or innovation.
The good news is that Oracle support costs are reducible — in many cases by 30–55% — using strategies that are available to most enterprise Oracle customers. This guide covers every proven approach, with the commercial mechanics and the limitations that matter for real-world decisions.
Part of our Complete Oracle Licensing Guide. Related: Software Licensing Advisory and Oracle Practice.
Why Oracle Support Is So Expensive — and Why It Stays That Way
Oracle's 22% support rate is not arbitrary — it is a deliberate commercial model designed to generate predictable, recurring revenue that exceeds initial license fee revenue over the long term. A product licensed in 2012 for $2M has generated $10.5M in cumulative support revenue by 2026, assuming only 3% annual increases. Oracle's support revenue now represents a significant majority of the company's total software licence and support revenue.
The mechanism that maintains this position is the "de-support" threat: if you stop paying Oracle support, you lose access to critical security patches, bug fixes, and the right to reinstall licensed software. For most enterprises, this creates a practical inability to reduce or cancel support even for legacy systems — because the security risk of unpatched Oracle Database or middleware in production is real.
Understanding this dynamic is important because it shapes which reduction strategies are practical: the goal is rarely to eliminate Oracle support entirely, but to reduce its cost while maintaining appropriate coverage for business-critical systems.
Strategy 1: Third-Party Support
Switch to Rimini Street, Spinnaker Support, or Another Third-Party Provider
Third-party support providers deliver ongoing maintenance, security patches, and bug fixes for Oracle products at approximately 50% of Oracle's annual rate. The two largest providers — Rimini Street and Spinnaker Support — collectively support thousands of enterprises across Oracle Database, E-Business Suite, PeopleSoft, Siebel, JD Edwards, and other Oracle products.
Third-party support has matured significantly since Rimini Street's founding in 2005. The primary objections — support quality, patch availability, compatibility with upgrades — have been substantially addressed through a decade of investment in support capabilities.
How Third-Party Support Works
Third-party providers typically offer: a primary support engineer assigned to your account, response SLAs comparable to or better than Oracle Premier Support, interoperability patches for third-party integrations, tax and regulatory updates (for ERP products), and access to a knowledge base built from existing Oracle patches and support resolutions.
The critical limitation: third-party support providers do not provide upgrade paths to new Oracle versions. If you plan to upgrade Oracle Database from version 12 to 19, or migrate from EBS 12.1 to 12.2, you need Oracle support for that process. Third-party support is therefore most appropriate for stable, non-upgrading Oracle deployments — which describes a substantial portion of most enterprises' Oracle footprint.
The Oracle Response to Third-Party Support
Oracle has historically taken a combative position toward third-party support providers — most famously through the extended legal dispute with Rimini Street. The practical implication for enterprise buyers is that Oracle will often use an audit, ULA renewal, or new license purchase as an opportunity to pressure customers who have moved to third-party support. Having specialist advisory support when transitioning is advisable.
Strategy 2: Negotiate a Support Cap at Renewal
Cap Annual Support Increases at Renewal
Oracle's standard support terms allow annual increases up to 8% in many agreements. Negotiating a fixed cap — typically 3–4% annually — over a multi-year term is a consistently achievable concession that meaningfully reduces total support cost over the contract period.
The cap negotiation is most effective when combined with a multi-year commitment, which Oracle values as revenue predictability. A 3-year Oracle support commitment with a 3% annual cap typically allows Oracle to recognise the revenue over the term, which has internal reporting value that drives commercial flexibility.
In practice, Oracle's approval hierarchy will often agree to a cap in the 3–4% range in Q4 (March–May fiscal year-end) or at significant renewal milestones. Without a cap, enterprises with large Oracle estates are exposed to significant year-on-year increases — we have seen enterprises absorb 7–8% annual support increases for multiple consecutive years, compounding significantly over time.
Strategy 3: Support Base Reduction
Remove Unused Products from the Support Base
Oracle calculates ATS as a percentage of "net license fees" — the value of the licenses you own. If you have licenses for products you no longer use, you are still paying support on those licenses at 22% annually. Removing those products from your support agreement reduces the base and therefore the annual charge.
This strategy requires careful execution. Oracle's terms typically require that any product removed from support cannot be subsequently re-added at the original license value — creating a scenario where terminating support on a product you might use in the future creates future license exposure. Independent assessment of which products are genuinely decommissioned (versus dormant) is essential before executing this strategy.
The most productive areas for support base reduction include Oracle Middleware products (Oracle Application Server, Oracle Forms/Reports, Oracle SOA Suite) where enterprises have migrated to alternative integration platforms; Oracle ERP modules no longer in production use; and Oracle Options purchased historically but never deployed in production.
Strategy 4: ULA Restructuring for Support Optimisation
Use ULA Restructuring to Reset Support Economics
For enterprises with complex, fragmented Oracle license estates, a well-structured ULA negotiation can consolidate the portfolio and negotiate a new blended support rate that is lower than the aggregate of existing commitments. This requires detailed licence position analysis and specialist Oracle ULA expertise.
The mechanism works because Oracle's ATS calculation is based on "net license fees" — and in a ULA negotiation, the reference point for support can be set based on the ULA fee rather than the cumulative historical list value of the license estate. For enterprises whose licenses have been discounted from list over many years, the cumulative list value (which is typically what Oracle calculates support against) can be substantially higher than the economic value of the licenses. A ULA reset can reduce this base.
Strategy 5: Cloud Migration with Support Included
Migrate Oracle Workloads to OCI or Managed Cloud Where Support Is Included
Oracle Cloud Infrastructure (OCI) subscription pricing for Oracle Database, Oracle ERP Cloud, and other Oracle SaaS products includes all support and maintenance. Migrating on-premises Oracle workloads to OCI can effectively eliminate the separate ATS charge for those workloads, replacing it with a subscription that includes software, infrastructure, and support in a single fee.
This strategy is most compelling for Oracle E-Business Suite migrations to Oracle Fusion ERP Cloud, Oracle Database migrations to Oracle Autonomous Database on OCI, and Oracle Middleware replacements with Oracle Integration Cloud. The economics vary significantly by workload — cloud unit economics are not always favourable — but for specific workloads, particularly those requiring high availability and active Oracle development, the migration case is strong.
See our Oracle Licensing Playbook for detailed OCI economics analysis.
Comparing Oracle Support Reduction Strategies
| Strategy | Typical Saving | Complexity | Best For |
|---|---|---|---|
| Third-Party Support | 40–50% | Medium | Stable, non-upgrading deployments |
| Support Cap Negotiation | 15–25% over 5yr | Low | All Oracle customers at renewal |
| Support Base Reduction | 10–30% | Medium | Enterprises with unused licensed products |
| ULA Restructuring | 20–40% TCO | High | Complex, fragmented Oracle estates |
| Cloud Migration | Varies | High | ERP modernisation, active development |
Combined Approach: The most significant support cost reductions in our advisory practice have come from combining strategies — for example, migrating development and non-critical workloads to third-party support, negotiating a cap on remaining Oracle ATS, and removing decommissioned products from the support base simultaneously. A structured support reduction programme across all three levers typically delivers 35–55% total support cost savings for enterprises with large Oracle estates.
Oracle's Response to Support Reduction Attempts
Oracle is acutely aware of enterprise support reduction strategies and deploys specific counter-tactics to protect this revenue stream. Understanding these tactics is essential for successful execution:
- Re-audit on third-party support switch: Oracle frequently initiates an audit (or increases audit pressure) when an enterprise indicates it is evaluating third-party support. The implied message is that any unresolved compliance issues will be easier to resolve with Oracle support in place. Having a clean compliance position before announcing a third-party support transition is important.
- Upgrade pressure: Oracle's account team will emphasise upcoming end-of-Premier-Support dates to create urgency for upgrades (which require Oracle support). Understanding Oracle's Extended Support and Sustaining Support policies allows enterprises to maintain patch access longer than Oracle's "Premier Support" period.
- Support bundling in new deals: Oracle typically bundles new license purchases with extended support commitments, making it difficult to segment. Specialist advisors negotiate these separately.
Enterprises achieving the best Oracle support outcomes consistently engage specialist advisors — including firms like Redress Compliance, which has specific expertise in Oracle support economics and has managed numerous third-party support transitions — rather than relying on internal procurement teams to navigate Oracle's counter-tactics alone.
Action Plan: Reducing Oracle Support Costs in 2026
- Audit your current support base: List every Oracle product you are paying support on, its annual cost, and whether it is actively in production, in maintenance, or effectively retired.
- Identify third-party support candidates: Products that are stable, not planned for upgrade in the next 3 years, and not deeply integrated with Oracle upgrade workflows are strong candidates.
- Assess your renewal dates: Oracle support reductions are most negotiable at renewal. Identify which agreements renew in the next 12 months.
- Engage specialist advisory support before approaching Oracle: The framing of support reduction requests matters significantly. Oracle's response to a well-advised enterprise with a credible third-party support alternative is different from its response to an internal procurement team asking for a discount.
For a confidential analysis of your Oracle support cost reduction potential, contact our Oracle practice.