Oracle support fees continue at the ULA level no matter how high you certify. A bigger certified number is free permanent value, not a higher bill. The fear that certifying more raises support is a myth, and it quietly costs buyers entitlement they were due.
By the Meridian advisory team · Ex Oracle licensing analysts · Updated June 2026
No. This is the single most useful fact a ULA holder can carry into certification, and it is widely misunderstood. Your Oracle support fee is set by the ULA itself, as a fixed annual amount tied to the agreement. When you certify, you convert your deployed quantities into a perpetual entitlement, but the support line does not move with the count. Certify a conservative number and your support is one figure. Certify a far larger, fully evidenced number and your support is the same figure. The perpetual entitlement you walk away with is larger in the second case, at no additional recurring cost. That is why a higher certified count is free value: you are capturing more permanent licensing for the support you were already going to pay.
Support continues at the ULA level regardless of the certified count, so every legitimate deployment you certify is free perpetual entitlement. The belief that a higher count means higher support is a myth, and acting on it leaves value on the table. Certify every defensible deployment. The cost decisions that actually matter sit at renewal and around dropping licenses, not at certification.
The fear is intuitive, which is why it persists. In ordinary perpetual licensing, more licenses mean more support, because support is a percentage of license value. Buyers carry that mental model into the ULA and assume the same relationship holds at certification. It does not. The ULA already fixed the support fee at the front of the term, decoupled from any later count. Certification measures and locks the entitlement; it does not re price the support. The intuition that served a buyer well in standard licensing becomes a liability inside a ULA, because it pushes toward certifying conservatively to avoid a cost increase that cannot happen. The vendor has little reason to correct the misunderstanding, since a smaller certified count is a smaller perpetual entitlement and a weaker future position for the customer.
A buyer who certifies cautiously to protect against a phantom support increase certifies fewer licenses than they were entitled to. Those uncertified deployments do not become free later. They become licenses to buy, or compliance gaps to defend, the moment deployment is questioned. The myth therefore has a real price, paid not at certification but afterwards, when the conservative number proves too small for the estate that actually exists.
No. Certification itself carries no charge. It is a process, not a purchase: you assemble the evidence, count the deployment within the rules, and declare the result in a certification letter, often signed by a senior executive. There is no transaction fee for doing so, and the act of certifying does not by itself alter your support cost. This matters because buyers sometimes hesitate to maximise the count out of a vague sense that a larger declaration will cost more in some form. It will not. The only thing that scales with the certified count is the perpetual entitlement you keep, which scales in your favour. The work of certification is in the evidence and the counting, not in any fee.
| Scenario | Certified count | Annual support | Perpetual entitlement kept |
|---|---|---|---|
| Conservative certification | Lower | Set by the ULA, unchanged | Smaller |
| Fully evidenced certification | Higher | Set by the ULA, unchanged | Larger |
Illustrative only. Support is the same in both rows; only the entitlement differs.
Support moves when the agreement moves, not when you certify. Three moments are worth watching. First, annual uplift: support is typically subject to a yearly increase, which applies across the term independent of certification. Second, renewal: if you renew into a new ULA rather than certifying out, the new agreement can establish a higher support base that persists for years, which is a central reason to weigh certifying against renewing carefully. Third, dropping licenses: reducing the licensed estate can trigger repricing of the support on what remains, sometimes erasing the saving you hoped to make. Certification sits outside all three. It holds support flat while converting deployment into permanent ownership. The cost decisions that deserve real scrutiny are the renewal choice and any plan to shed licenses, not the certified count.
Consider a manufacturer, figures indicative only, that initially planned to certify a modest database count out of concern that a larger number would lift support. On review, the support fee was confirmed fixed by the ULA and independent of the count. The organisation then certified its full, evidenced deployment, including test and disaster recovery instances within the term. Its support fee did not change. Its perpetual entitlement landed well above the conservative figure first considered, at no extra recurring cost.
Understanding that support stays flat is the foundation for the cost decisions that come after the ULA. Read repricing risk when dropping licenses for the one move that genuinely can raise support, and selling the value of the certified position internally for how to make the case to finance once the entitlement is locked. Our post certification audit and cost guide is the pillar that frames the whole period after exit. When you want to confirm that your certified count is as complete as it should be, the next step is a confidential assessment.
No. Support fees continue at the level set by the ULA, regardless of how many licenses you certify. Whether you certify a modest count or a large one, the support line is the same. That makes a higher certified number free permanent value, because you gain more perpetual entitlement at no extra recurring cost. The fear that certifying more raises support is a myth.
No. There is no charge for the certification itself. Certification is the process of converting your deployed quantities into a perpetual entitlement, declared in a letter. It does not carry a transaction fee, and it does not by itself change your support cost. The value you capture comes from certifying every legitimate deployment, since each one becomes free perpetual entitlement.
Support changes when the agreement changes, not when you certify. Annual support is subject to uplift over time, and it can move if you renew into a new ULA, buy additional licenses, or drop licenses and trigger repricing. Certification on its own holds support flat. The cost decisions to watch sit around renewal and around any move to reduce the licensed estate.