Oracle charges 22% of net licence value every year for Oracle Software Update Licence & Support — regardless of whether you use a single feature of the support entitlement. For large Oracle estates, this is the single largest recurring IT cost after headcount. Former Oracle insiders explain how the charge works, how Oracle defends it, and how enterprises legitimately cut it.
Oracle's annual support charge — formally called Oracle Software Update Licence & Support — is 22% of the net licence value of all Oracle software you are on support. Net licence value is the price you paid for the licence, before any negotiated discounts were applied. This is a critical distinction: if you bought Oracle Database Enterprise Edition at $47,500 per processor and negotiated a 40% discount, paying $28,500 per processor, Oracle's 22% support charge is applied to the original $47,500 list price — not the discounted price you paid. In some contract structures, it is applied to the actual price paid; in others, to list. Always examine your specific Order Form and Master Agreement.
The support charge compounds. If Oracle negotiates an annual price increase into your support schedule — Oracle's standard position is 8% annual uplift, with a typical negotiated position between 0% and 4% — the base grows each year. An enterprise that signed a three-year support schedule with 4% annual increases is paying 22% × (1.04 × 1.04) = approximately 23.8% of original net licence value by year three, on top of any additional licences added during the term.
| Oracle DB EE Scenario | Processor Licences | List NLV | Annual Support (22%) | 5-Year Support Total |
|---|---|---|---|---|
| Small Deployment | 20 | $950,000 | $209,000/yr | $1,045,000 |
| Mid-Size Deployment | 100 | $4,750,000 | $1,045,000/yr | $5,225,000 |
| Large Enterprise | 500 | $23,750,000 | $5,225,000/yr | $26,125,000 |
| Global Enterprise | 2,000 | $95,000,000 | $20,900,000/yr | $104,500,000 |
For the global enterprise in this example, Oracle support is a nine-figure five-year commitment. Even at a 40% discount on the base support rate — which Oracle rarely grants to non-EA customers — this remains one of the largest recurring software costs in the enterprise. Understanding how to challenge, reduce, or restructure this obligation is one of the highest-return activities in Oracle cost management.
Our Oracle Support Cost Reduction service starts with a forensic analysis of your support schedule, identifying right-sizing opportunities, unused entitlements, and the full range of reduction options available for your specific Oracle estate.
Oracle Software Update Licence & Support entitles you to three primary things: access to software patches and security updates (including CPU — Critical Patch Updates — delivered quarterly), access to Oracle Support's service request system (formerly Metalink/My Oracle Support), and the right to use new product versions and releases within your licensed product family released during the support term.
The practical value of these entitlements varies enormously by product. For Oracle Database, security patches are critical — Oracle's quarterly CPU process delivers patches for newly discovered vulnerabilities, and being off support means those patches are not available. For legacy EBS (E-Business Suite) or PeopleSoft installations that are effectively frozen, Oracle's new version releases carry little value. The enterprise is paying 22% per year for the right to upgrade to versions it never intends to run.
Oracle also uses support as a commercial lever. Being on active Oracle support is a prerequisite for Oracle Software Assurance, a ULA certification, and access to certain OCI services with BYOL. Oracle's account teams use support status as a dependency in every commercial conversation. Dropping Oracle support is never a purely technical decision — it triggers commercial consequences that require careful management.
What Oracle support does not deliver: proactive support that anticipates your problems, meaningful SLAs with financial penalties, guaranteed problem resolution timelines, or on-site support. Oracle's standard support SLA is an 8-hour response target for critical severity-1 issues — a target that many customers report Oracle regularly misses without consequence. For organisations accustomed to best-in-class vendor support, Oracle's 22% charge represents poor value relative to what is delivered.
Oracle has spent years building dependencies that make dropping Oracle support feel impossible. Understanding Oracle's playbook is the first step to pushing back effectively.
The security patch dependency. Oracle's position is that without active support, you cannot receive security patches, and running unpatched Oracle Database in production exposes you to regulatory risk (GDPR, PCI-DSS, SOX IT controls). This is Oracle's most powerful argument for support retention. The counterargument — which third-party support providers make credibly — is that a third-party provider can backport security patches to your current version, maintaining your security posture without Oracle support.
The upgrade lock. Oracle frequently hints that your existing deployment will become unsupported ("extended support," then "sustaining support") without upgrades, and that those upgrades require active support. This creates an upgrade cycle that perpetuates the 22% charge indefinitely. Challenge this by identifying your actual version roadmap — many enterprises are running database versions that have years of premier support remaining.
The audit threat. Oracle's account teams occasionally suggest that enterprises who drop support become more likely to receive an Oracle audit. While Oracle does not formally confirm this, the pattern is real. Being off support removes a commercial relationship anchor and changes Oracle's perception of your organisation. This is a legitimate consideration — not a reason to stay on support, but a reason to plan your off-support transition carefully with expert support. Our Oracle Audit Defence team manages this risk throughout any support transition.
If you terminate Oracle support and later decide to reinstate it — whether because a third-party support arrangement didn't work, because you're planning an Oracle upgrade, or because Oracle conditions a new deal on reinstatement — Oracle charges a reinstatement fee equal to all the support fees you would have paid during the lapsed period, plus interest. For a three-year lapse on a large Oracle estate, this reinstatement fee can be tens of millions of dollars.
Oracle uses the reinstatement fee as both a deterrent and a negotiating weapon. When an enterprise discusses reducing or terminating Oracle support, Oracle's response frequently includes a reminder that reinstating support later will cost significantly more. This creates a lock-in effect that traps enterprises in continuous support renewals even when they derive minimal value.
Before dropping Oracle support, model the reinstatement cost: Calculate what reinstatement would cost at year 1, year 3, and year 5 of lapse. This gives you an accurate picture of the actual long-term cost of your decision — and the data you need to negotiate Oracle's position at renewal.
The reinstatement fee can be negotiated. Oracle has waived or significantly reduced reinstatement fees in exchange for new commercial commitments — ULA deals, EA renewals, OCI migration agreements. If you are planning to re-engage with Oracle commercially after a period of reduced spend, the reinstatement fee is a negotiating chip, not a fixed obligation. Our Oracle Contract Negotiation team has negotiated reinstatement fee waivers as part of broader Oracle commercial restructurings in multiple engagements.
Get independent advice before notifying Oracle. The sequence and timing of your actions determines the commercial outcome. Our Oracle Support Reduction practice manages the full process — from analysis to execution.
Enterprises have more levers to reduce Oracle support costs than Oracle's sales team acknowledges. The strategies below are evidence-based approaches we have successfully deployed across hundreds of Oracle support reduction engagements.
Right-size your licence position before renewal. Many enterprises pay 22% support on licences they are not actually deploying. If your licence count includes historical purchases that are no longer in use, you can — in many contract structures — terminate support on those licences at renewal and reduce your support base. Oracle will resist this, but it is contractually permissible in many cases. Terminating support on unused licences eliminates the corresponding 22% charge without triggering reinstatement risk on the remaining estate.
Negotiate a multiyear support discount at renewal. Oracle's standard practice is to offer support renewals at the prior year rate plus their requested uplift. By committing to a multiyear support term — two or three years — enterprises can negotiate a fixed rate with zero uplift, a one-time support credit, or both. A three-year deal at 0% uplift is worth 8% × 3 = 24% of your annual support bill in Year 3. For a $5M annual support obligation, that is $1.2M in Year 3 savings alone.
Eliminate Excluded Programmes. Review your support schedule for Oracle products covered under Extended Support or Sustaining Support. These products attract the same 22% charge but deliver reduced services — Extended Support does not include performance patches; Sustaining Support provides only existing patches. If you are paying full support rates for products in these degraded categories, you are significantly overpaying relative to value received. Negotiate rate reductions or migrate those workloads to products within Premier Support.
Transition to third-party support for stable, non-upgrading workloads. This is the highest-impact strategy for the right workloads — see below.
Third-party Oracle support providers — organisations that provide Oracle Database and middleware support services without Oracle's involvement — typically charge 50-70% less than Oracle's 22% annual rate. For a $5M annual Oracle support obligation, this represents $2.5-3.5M in annual savings. These savings compound over a multi-year commitment into a material improvement in Oracle total cost of ownership.
Third-party support is not appropriate for every Oracle workload. It works best for stable Oracle Database and middleware environments that are not actively pursuing Oracle upgrades, where the primary support need is break-fix, security patch management, and tax/regulatory updates rather than new feature access. It is not viable for Oracle applications (EBS, PeopleSoft, JD Edwards, Siebel) if you require Oracle-provided application patches or regulatory updates.
The security patch question is the primary objection Oracle raises to third-party support. Oracle's position is that third-party providers cannot create or deliver Oracle patches, and that running without Oracle patches exposes you to unacceptable risk. The mature third-party providers counter this with two mechanisms: backporting — they develop patches for known vulnerabilities that apply to your specific version — and advanced security services that mitigate the risk of unpatched vulnerabilities through compensating controls. Whether this approach meets your regulatory requirements depends on your specific compliance framework.
For a detailed analysis of the third-party support decision, including how to model the financial case and assess the compliance risk framework, see our Oracle Support Reduction Playbook white paper and the Insurance: Third-Party Support Transition case study where we achieved $2.8M in annual savings for one client.
Oracle support renewal negotiations follow a predictable pattern — Oracle's position is that the rate is non-negotiable and the only question is whether you apply the standard uplift. This is wrong. Oracle support rates are negotiable, and the leverage comes from understanding Oracle's economics and the alternatives available to you.
The most effective negotiating position is a credible third-party support alternative. If Oracle knows you have evaluated a third-party provider and obtained pricing, the commercial dynamic shifts. Oracle's account team is incentivised on support retention. Demonstrating that you are a genuine flight risk — rather than posturing — changes the conversation. We prepare clients for this by securing third-party support pricing before engaging Oracle, so the threat is documented and verifiable.
Timing matters. Oracle's fiscal year ends May 31. The Q4 window (March-May) is when Oracle sales teams are under maximum quota pressure. Support renewal negotiations initiated in this window — particularly for large support obligations — consistently yield better outcomes than renewals executed outside the fiscal year. Similarly, Oracle's Q3 (December-February) can be productive for enterprise-scale deals where Oracle needs to book revenue before February close.
Bundle the support negotiation with a broader commercial commitment when appropriate. If you are planning OCI migration, a new EA, or any incremental Oracle spend, use these as negotiating assets alongside the support renewal. Oracle's willingness to discount support increases materially when there is new revenue attached to the conversation.
A global insurance group had accumulated Oracle Database Enterprise Edition licences across twelve subsidiary IT environments over fifteen years of acquisitions. Annual Oracle support was £3.4M across 680 processor licences — with 22% applied on a historical net licence value base that included premium pricing from deals struck before significant Oracle price negotiation capability existed within the group.
Our Oracle Support Reduction engagement identified that 240 of the 680 licences were supporting environments on Oracle Database 12c R2 — a version Oracle had moved to Extended Support. The group was paying full 22% support rates for Extended Support coverage on workloads that had been stable for four years with no planned Oracle upgrades.
We structured a two-track approach: transition the 240 Extended Support licences to a third-party provider (saving £748,000 annually), and renegotiate the remaining 440-licence Premier Support position using the third-party engagement as leverage and a three-year commitment to secure a 12% rate reduction on the remaining Oracle support base (saving £449,000 annually). Combined annual saving: £1.197M — equivalent to $1.56M USD at the time of the engagement — on a direct comparison, with additional savings from eliminating Extended Support premium charges. The full case study is available at Insurance: Third-Party Support Transition.
Our white paper covers every lever for reducing Oracle annual support — from right-sizing to third-party support to renewal negotiation tactics — with worked financial models for three common enterprise scenarios.
Download Free White Paper →Support cost alerts, renewal tactics, and Oracle licensing intelligence for enterprise stakeholders.
Former Oracle licence managers, LMS auditors, and contract executives — now working exclusively for enterprise buyers. 25+ years of Oracle licensing experience. Not affiliated with Oracle Corporation. About us →
A confidential Oracle support analysis identifies reduction opportunities across your estate — whether through right-sizing, third-party transition, or renewal negotiation. Most clients recover the cost of our engagement in the first quarter of savings.
Not affiliated with Oracle Corporation. Independent advisory for enterprise buyers.
Free Research
Download our Oracle E-Business Suite Licensing Guide — expert analysis from former Oracle insiders, 100% buyer-side.
Download the Oracle EBS Licensing Guide →Free Research
Download our Oracle JD Edwards Licensing Guide — expert analysis from former Oracle insiders, 100% buyer-side.
Download the JDE Licensing Guide →