Support
Oracle Support Renewal: Key Commercial Questions

Executive takeaway
Oracle support is often the largest recurring line in an Oracle relationship, and its rules reward preparation. Understanding license sets, repricing, reinstatement and support levels before the invoice arrives is what turns a routine renewal into a real decision.
Key takeaways
- Support renewals build on last year's fees plus a renewal adjustment. A written cap in your agreement limits that adjustment.
- Oracle requires all licenses in a license set to be supported at the same level, so you cannot drop support on just part of a set.
- Terminating some licenses on an order can trigger repricing of the rest. Model it before you send notice.
- Letting support lapse and coming back later carries a reinstatement fee of 150% of the last annual fee, prorated.
- Sustaining Support keeps you supported but excludes new fixes and security patches. It is a decision about rights, not only cost.
For many enterprises, annual Oracle technical support costs more than any single new purchase. Yet the support renewal often receives less scrutiny than a new license deal, because it looks like a continuation of something already decided.
It is worth treating it as a decision. The questions below are designed for CFOs, procurement and legal teams preparing for the next support invoice. Each refers to Oracle’s own published policies, which apply alongside the terms of your agreements.
1. How is our support fee calculated, and how has it grown?
On Oracle’s Technology Global Price List, the first-year Software Update License & Support fee shown for each technology product equals 22% of that product’s license list price. What you actually pay depends on the net terms in your ordering documents.
After the first year, the same price list explains that a support renewal is based on the support fees paid for the same licenses in the prior year, increased by an inflationary adjustment rate. Because each year builds on the last, increases compound. Reviewing how your support base has evolved over several years is the starting point for any serious discussion.
2. Do we have a written cap on annual increases?
Oracle’s price list states that any valid technical support cap included in a license agreement or ordering document limits the renewal adjustment. Caps are not automatic; they are negotiated.
Find out whether you have one, which licenses it covers, and when it expires. If you do not, consider whether the next renewal or a related purchase is the right moment to request one. Over a multi-year horizon, a cap on future increases is often worth more than a one-time discount.
3. Which licenses are no longer used?
Reconcile your support records, organized by customer support identifier (CSI), against actual deployments and usage. Licenses that support retired systems, discontinued projects or abandoned options are candidates for termination.
Identifying them is the easy part. Understanding the consequences of terminating them requires the next two questions.
4. Can we drop support on just some licenses?
Usually not in the way finance teams expect. Oracle’s Software Technical Support Policies define a license set, which includes all of your licenses of a program, including its options, and licenses of programs that share the same source code (for example, the different editions of Oracle Database).
Under the matching service levels policy, all licenses in a license set must be supported at the same technical support level. You may not support a subset of licenses within a set; the set must be reduced by terminating the unsupported licenses, documented by a termination letter.
In other words, reducing support means giving up licenses, not just suspending a service.
5. Will terminating licenses actually reduce our bill?
Not always as much as expected. Oracle’s policy on pricing following reduction of licenses or support level states that when a subset of licenses on a single order is terminated, support for the remaining licenses on that order is priced at Oracle’s list support price in effect at the time, minus the applicable standard discount. The policy sets limits on that recalculation in both directions.
Where the original order carried a substantial discount, repricing the remaining licenses can absorb much of the saving from the termination. The way licenses are grouped across orders, and whether whole orders or whole license sets can be terminated, makes a significant difference.
Model the outcome before any notice is given, using the policy version that applies to your orders.
6. What would it cost to leave support and come back?
Oracle’s reinstatement policy is explicit. If technical support lapses, the reinstatement fee is 150% of the last annual technical support fee paid for the relevant program, prorated back to the date support lapsed. On top of that, you pay the support fee for the new support period, and renewal adjustments may apply.
That cost should be part of any evaluation of dropping support, moving to an alternative support model or simply delaying a renewal.
7. Is Extended or Sustaining Support acceptable for this system?
Oracle’s Lifetime Support model has three levels:
- Premier Support, documented on orders as Software Update License & Support, generally available for five years from a release’s general availability.
- Extended Support, offered for specific releases for up to three additional years, for an additional fee. Oracle’s price list describes the additional fee as a percentage of the current year’s support that increases from year six to year eight.
- Sustaining Support, available for as long as you continue to pay annual support.
Sustaining Support is not a discount tier. According to Oracle’s policies, it does not include new program updates, fixes, security alerts or critical patch updates, new tax, legal and regulatory updates, certification with new third-party products or versions, or the 24-hour response commitment for Severity 1 requests.
For a stable system nearing retirement, that may be acceptable. For a system exposed to security or regulatory change, it may not be. Treat the choice as a risk decision with an owner, not only as a budget line.
8. Are alternative support models worth evaluating?
Some enterprises evaluate third-party support for stable systems that no longer need new releases, or a mixed model by product. Whether that makes sense depends on the systems involved, your upgrade plans, security and regulatory requirements, and the contractual consequences.
If you consider it, document your license and compliance position thoroughly beforehand, include the reinstatement cost in the comparison, and understand how the license set and repricing policies affect the support you keep with Oracle.
9. Can cloud consumption offset our support bill?
Possibly. Under Oracle Support Rewards, customers with a Universal Credits order earn rewards on eligible OCI consumption (25%, or 33% for customers with a current Unlimited License Agreement) that can be applied to support invoices for Oracle technology programs. Rewards expire 12 months after they are deposited, cannot pay taxes and cannot be used for applications support.
If OCI is already part of your plans, rewards can reduce support costs. They should not, on their own, justify a cloud commitment.
10. Which policy version applies to our renewal?
Oracle’s Technical Support Policies state that they are subject to change at Oracle’s discretion, while also stating that policy changes will not result in a material reduction in the level of services provided for supported programs during a support period already paid for. Each support period is typically 12 months, and once placed, a support order is non-cancelable unless the order provides otherwise.
When you negotiate significant terms, ask how they will be preserved across future policy versions and future orders, and make sure new ordering documents do not silently replace protections in older ones.
Practical implications
- For the CFO: see support as a multi-year cost curve, not an annual invoice.
- For procurement: build a CSI-level view and model terminations before negotiating.
- For legal: confirm caps, price holds and how new paper affects earlier protections.
- For IT: own the deployment evidence and the risk assessment for any change in support level.
In Latin America, support is commonly invoiced in US dollars while budgets are set in local currency, so increases compound alongside currency movements. Clarify the invoicing entity and currency, how local taxes and withholding apply, and whether your tax position affects the comparison between support options.
Practical checklist: support line review
- List every CSI with product, license set, order, quantity and annual fee.
- Mark each line as deployed and used, deployed but unused, or not deployed.
- Identify existing caps and price holds, and their expiry dates.
- Model repricing for each potential termination before giving notice.
- Price the reinstatement cost for any line you might leave.
- Assign a risk owner for any move to Sustaining Support.
- Check Support Rewards eligibility if OCI is in use or planned.
- Confirm how new ordering documents interact with existing protections.
Common pitfalls
- Partial terminations that save little. Repricing can offset most of the reduction.
- Accepting a one-time credit instead of a cap. The credit disappears; the increases continue.
- Changing support without a compliance baseline. Document your position before any change.
- Treating Sustaining Support as a discount. It is a different set of rights.
- Missing the renewal window. Late decisions limit the options available.
Frequently asked questions
Why does our support bill rise every year?
Oracle’s price list describes support renewals as the prior year’s fees for the same licenses increased by an inflationary adjustment rate, limited by any valid cap in your agreement. Without a cap, increases compound.
Can we stop paying support on licenses we no longer use?
Yes, by terminating those licenses. Under Oracle’s matching service levels policy, you cannot keep a subset of a license set unsupported. Model repricing first.
What happens if support lapses?
Under Oracle’s policy, reinstatement costs 150% of the last annual support fee for the program, prorated back to the lapse date, plus the support fee for the new period.
Is moving to Sustaining Support a saving?
Not in itself. Sustaining Support continues to be paid annually and excludes new fixes, security alerts and critical patch updates. It is a decision about what support you need.
Official Oracle sources
- Oracle Software Technical Support Policies (effective 9 October 2026) (opens in a new tab)
- Oracle Technology Global Price List (15 September 2026), Support Renewals and Extended Support (opens in a new tab)
- Oracle Lifetime Support Policy (opens in a new tab)
- Oracle Support Rewards FAQ (opens in a new tab)
Oracle policies, price lists and programs change. Always confirm against the current version and the terms of your own agreements.
This article is general information, not legal, tax or licensing advice for a specific situation. RedTech Experts is independent and is not affiliated with or endorsed by Oracle.


