The license is a headline. The support fee is the bill you actually pay, year after year, and it is the number that decides what your Oracle estate costs over its life. Most buyers negotiate hard on the license discount and then accept the support line as a fixed cost of doing business, which is exactly the framing that lets it grow unchallenged. The 22 percent figure is small enough to wave through and recurring enough to dominate everything. Understanding how it compounds, and where the levers actually are, is the start of treating support as a managed cost rather than an annuity you pay forever.
How much is Oracle support per year?
Oracle technical support runs at roughly 22 percent of the net license fee per year, with an annual escalation built into each renewal. The percentage is applied to what you paid for the licenses, and the escalation lifts the rate a little every year, so the number on the invoice is never flat. Because it recurs, the comparison that matters is not support against this year's budget but support against the original license purchase. A license bought once is paid for once. Support at 22 percent with escalation is paid every year for as long as you hold the licenses, and that recurring nature is what turns a modest looking percentage into the largest line in the total cost of ownership.
Why does Oracle support cost more than the license over time?
Oracle support costs more than the license over time because 22 percent recurring with annual escalation compounds, and within a handful of years the cumulative support paid passes the one time license fee and keeps climbing. The arithmetic is unforgiving: pay 22 percent a year and you have matched the license cost in under five years even before escalation, and escalation only shortens that. From that point everything is on top. This is why support, not license, is the dominant lifetime cost of a perpetual Oracle estate, and why a support strategy is worth more to the total bill than another point of discount on the next license purchase.
| Point in time | What you have paid | Against the license |
|---|---|---|
| Year 1 | Roughly 22 percent | About a fifth |
| Around year 5 | Support roughly equals license | Drawn level |
| Year 10 | Support well past the license | The dominant cost |
Can you reduce Oracle support without losing licenses?
You can sometimes reduce Oracle support without surrendering capability, but matching service levels constrain how, and the reduction must be modelled against the contract before any action. Matching service levels require every license in a set to carry the same support, so dropping support on part of a set can reprice the remainder toward list and cancel the saving. The levers that survive are structural: separating genuinely surplus licenses where the agreement allows, timing changes to the renewal when repricing actually happens, and modelling the net of the dropped portion and the repriced remainder together. Where Support Rewards is available, OCI consumption can offset a share of the support spend, but that is a relationship to model over the term, not a standalone cut.
A buyer treated the 22 percent line as fixed for years, paying it without review while escalation lifted it each renewal. A single modelling exercise showed that the cumulative support had quietly passed the original license cost and was now the largest Oracle line in the budget. The fix was not a blunt cut, which matching service levels would have repriced away, but a deliberate plan: map the sets, identify the genuinely surplus licenses, and work the next renewal to separate and reprice them explicitly. The escalation that had run unchecked became a number the buyer managed rather than absorbed.
What is the buyer move?
The buyer move is to treat the 22 percent as a managed cost, not a fixed one, and to model it across the full term before every renewal. Know what the cumulative support has reached against the original license, map your sets so you understand what matching service levels will and will not allow, and time any reduction to the renewal where repricing occurs. The objective is a support bill that reflects the estate you actually run, contained deliberately through the contract, rather than an escalating annuity you pay because no one ever modelled the alternative. The lever is real, but it is a contract lever first and a procurement one second.
For why dropping unused licenses often saves nothing, see the support mistakes that lock in cost. For the alternative support route and its audit considerations, see third party support and audit risk. The full method sits in the Oracle negotiation guide.