What ULA support fees actually cover
Technical support and maintenance is the recurring service that gives a customer the right to receive patches, security updates, and new releases, and to raise support requests with Oracle. It is licensed separately from the software right and is charged annually. Under a ULA the support fee is tied to the agreement and is usually expressed as a percentage of the net licence fees, commonly in the region of twenty two percent per year, in line with Oracle's standard support rate. The relationship between the licence fee, the support fee, and overall ULA economics is set out in the ULA cost guide, and the agreement mechanics in the Oracle ULA pillar guide.
The defining characteristic of support is that it is recurring and, in Oracle's commercial model, designed to be durable. Unlike the one time licence fee, support is paid every year for as long as the customer wants to remain supported, and Oracle's policies, including the reinstatement penalty for restarting lapsed support, are structured to keep that stream intact. This durability is what makes the support fee, rather than the headline licence fee, the more important number over the full life of an Oracle relationship.
Support pricing during the term
During the ULA term the support fee is generally fixed. The customer pays an agreed annual support charge that does not rise as deployment grows, which is part of the appeal of the model: an organisation can triple its in scope footprint and the support bill stays the same. This fixed support during a period of unlimited deployment is genuinely valuable, because under an ordinary licensing model each new deployment would add both licence and support cost. Within the ULA, the marginal support cost of additional in scope deployment is zero for the duration.
During the term the support bill is flat while deployment soars. After the term the deployment is locked in but the support bill stays flat too, which is the part customers forget to plan for.
This dynamic reinforces the case for aggressive deployment during the term, because the customer captures more entitlement against a support fee that does not move. It is the support side of the certification logic: the more you deploy and certify, the more entitlement you carry for the same fixed support stream, improving the effective value of every support dollar.
What happens to support fees after certification?
After certification the unlimited right converts to a fixed perpetual entitlement, and the support stream carries forward. Crucially, the support fee does not fall just because deployment growth has stopped or because the customer certified a particular quantity. The support obligation continues at broadly the level established under the agreement, and Oracle's repricing and matching service level policies are designed to prevent customers from cherry picking which licences to support or reducing the stream by dropping unused entitlement.
| Phase | Support fee behaviour | Implication |
|---|---|---|
| During term | Fixed regardless of deployment | Deploy aggressively, marginal support is zero |
| At certification | Stream carries forward | Support does not drop with growth stopping |
| After certification | Recurs annually, resists reduction | Long term cost driver to model |
| At renewal | Often the anchor of the offer | Oracle protects the stream in negotiation |
This is why a ULA should be evaluated on its lifetime support cost, not just its licence fee. A favourable licence fee tied to a large recurring support stream can be more expensive over ten years than a higher licence fee with a smaller support obligation. Modelling the support stream forward is part of any rigorous assessment, a discipline detailed in the ULA cost guide.
Why support fees are sticky
Support fees are sticky by design. Oracle's repricing policy generally means that if a customer terminates support on part of its estate, the support cost of the remaining licences can be repriced upward, eroding the saving. Matching service levels rules require related licences to be supported at the same level, preventing selective support. And reinstatement fees make it costly to drop support and later restart it. Together these policies make the support stream very difficult to reduce once established, which is the single most underappreciated feature of the Oracle commercial model.
For a ULA this means the support fee agreed at signing tends to define a recurring cost that persists long after the term, regardless of how the deployment evolves. An organisation that signs a ULA without modelling the perpetual support consequence can find itself paying a large annual fee indefinitely for an entitlement it no longer fully uses. The remedy is to treat the support fee as a long term liability from the outset and to negotiate it with the same care as the licence fee.
How support shapes the renewal decision
When a ULA approaches term end, Oracle typically offers a renewal, and the support stream is usually the anchor of that conversation. Oracle's preference is to keep the customer in a recurring relationship, and renewal proposals are often framed so that the cost of certifying and walking away, then continuing to pay support on the certified estate, is positioned against the cost of renewing for another term. Because support continues either way, the marginal economics of renewal can look more attractive than they are unless the support baseline is properly understood.
The decision to certify and exit or to renew therefore hinges substantially on the support stream, and it should be modelled explicitly: what support will be paid after certification on the perpetual estate, what it would be under a renewal, and how each path constrains future flexibility. This analysis is central to the ULA renewal guide and to the ULA negotiation service, where the support stream is treated as the long term cost it really is rather than a footnote to the licence discussion.
Options for reducing the support stream
Reducing an Oracle support stream is hard but not impossible, and the realistic options are limited and consequential. Terminating support entirely on a defined, separable set of licences can lower cost, but only where repricing and matching service level rules do not claw the saving back, which requires careful structuring at the licence set level. Moving to third party support is an alternative some organisations pursue to cut the fee substantially, accepting the loss of Oracle patches and new versions and the implications for future upgrades. Consolidating or right sizing the certified estate before certification can also limit the perpetual support base, provided it is done legitimately.
Each of these options carries trade offs and audit implications, because reducing support can change the customer's risk profile and the way Oracle engages, a dynamic that intersects with Oracle audit defence. None should be undertaken without modelling the full consequence, but the existence of these levers is why the support stream should never be treated as an immovable given.
The buyer side view
The buyer side view is that the support fee, not the licence fee, is the number that defines the long run cost of a ULA. It is fixed and favourable during the term, which rewards aggressive deployment, but it carries forward after certification as a sticky recurring obligation that Oracle's policies are built to protect. Evaluate any ULA on its lifetime support cost, negotiate the support fee as carefully as the licence fee, and model the support stream explicitly when deciding whether to certify and exit or to renew.
Build a ten year support model before you sign or renew, read the ULA cost guide for the full economics and the renewal guide for the endgame, and treat the recurring support stream as the central commercial fact of the agreement rather than a percentage line you accept by default.
Oracle ULA support fees: frequently asked questions
How are Oracle ULA support fees calculated?
Support is charged annually as a percentage of the net licence fees, commonly around twenty two percent, in line with Oracle standard support. During the term it is fixed regardless of deployment. See the ULA cost guide.
Do support fees fall after ULA certification?
Generally no. The support stream carries forward at broadly the same level even though deployment growth has stopped, and Oracle's repricing and matching service level policies are designed to prevent the stream from being reduced.
Why are Oracle support fees so hard to reduce?
Repricing policy raises the cost of remaining licences if you drop some, matching service levels prevent selective support, and reinstatement fees penalise dropping and restarting. Together these make the support stream very sticky once established.
How does the support stream affect the renewal decision?
Heavily. Because support continues whether you renew or certify and exit, the support baseline anchors Oracle renewal offers. Model the post certification support cost against the renewal cost explicitly. See the renewal guide.