Certifying does not change your support fee, but the annual uplift in your support contract keeps compounding for as long as you pay it. The cost to manage after a ULA is not the certification, it is the support line that grows quietly every year regardless of how many licenses you actually use.
Support is fixed at the ULA level at certification and does not rise because you certified a larger number. What rises is the annual uplift, year on year, on the whole fee. Managing that escalation, and avoiding the repricing trap when you try to cut it, is the real cost discipline after exit.
No. This is the single most important and most misunderstood fact about a ULA exit. Your support fee is set at the ULA level and continues unchanged when you certify, whatever count you declare. Certifying more licenses does not increase support by a single dollar. The widespread fear that a bigger certified number means a bigger support bill is simply wrong, and it costs organisations real value when it makes them certify conservatively. A higher defensible count is free perpetual entitlement carried at the same support cost.
What does change over time is the uplift. Most Oracle support agreements apply an annual increase, commonly in the region of four percent, to the existing fee. That percentage is small in any one year and large across a contract life, because it compounds.
Certify the largest defensible number you can. It is free value carried at a support cost you are already paying. Then manage the uplift as a separate, ongoing line of work.
The arithmetic is what makes support the dominant long term Oracle cost. The table below is indicative and assumes a four percent annual uplift on a starting support fee, with no other change to the estate.
| Year | Indexed support fee |
|---|---|
| Year 1 | 100 |
| Year 3 | 108 |
| Year 5 | 117 |
| Year 10 | 142 |
Over a decade a four percent uplift adds more than forty percent to the fee with nothing deployed differently. The figures are indicative and your actual uplift clause governs, but the shape holds: the longer you carry the support set unmanaged, the more it grows.
The obvious response to a growing support line is to stop paying support on licenses you no longer use. The obstacle is repricing. Oracle prices support as a set under its policy, and dropping part of that set can trigger a repricing of the licenses you keep to their standalone rate. The headline saving from terminating support on shelved licenses is therefore often smaller than expected, and in some matrices it is wiped out entirely. This is contract and policy specific, so the matrix has to be modelled on your actual support set before any reduction is attempted, never assumed.
There are legitimate levers. Consolidating support sets, timing reductions, and modelling the repricing impact in advance all help. The point is that none of them should be pulled blind. A reduction that looks like a saving on a spreadsheet can cost more once Oracle applies its repricing policy to the remainder.
Support is the cost that outlives the ULA, so it deserves its own plan. Certify large, because support does not move with the count. Then model the uplift and the repricing matrix before you touch anything. The companion notes go deeper on the two live decisions: the support negotiation at exit time and shelving versus using certified licenses. The wider context sits in our post certification guide.
No. The support fee is set at the ULA level and continues unchanged at certification regardless of the count you certify. A higher certified number does not raise support. That is why a larger defensible count is free value.
Most Oracle support agreements carry an annual uplift, often around four percent, applied to the existing fee. Over a multi year period that compounding is the main reason the support line grows even when nothing in your estate changes.
Oracle support is sold as a bundle priced by policy. If you drop part of a support set to save money, Oracle can reprice the remaining licenses to their standalone rate, so the saving is smaller than expected. The matrix must be modelled before any reduction.
We model your uplift, test the repricing matrix, and show you where support cost can be reduced safely. Book a confidential assessment to start.