Oracle support continues at the ULA level after certification, set by the fee you already pay, not by the number you declare. A higher defensible count converts into more perpetual licenses at no extra support cost. The fear that certifying more raises support is a myth, and it quietly leaves value behind.
If you take one fact into your certification window, make it this one. Inside a ULA, the support fee is fixed at the agreement level and does not flex with the number you certify. So every additional license you can defensibly count is permanent entitlement you keep for free, with no increase to the annual support bill. Teams that certify conservatively to avoid a larger support charge are protecting against a cost that does not exist, and they pay for that misunderstanding in lost entitlement they can never recover.
Outside a ULA, Oracle support is normally billed as a percentage of the net license fee you paid, so buying more licenses raises the support line. That is the model most procurement and finance teams know, and it is the source of the worry. A ULA changes the arrangement. During the term you pay a fixed support amount tied to the agreement, not to deployment, which is the whole point of unlimited rights. When you certify at the end, your deployed quantities convert into perpetual licenses, and support continues at that same ULA level. The certified number does not retroactively reprice the support stream. You leave the term carrying the support you already had, now backed by a larger pool of owned licenses.
Certification is the one moment where more is genuinely free. The licenses are permanent, the support is flat, and the only ceiling on the number is the evidence behind it.
No. Support continues at the ULA level, set by the fee already in place, and a higher certified count does not raise it. This is the cleanest free value in the entire Oracle relationship. Two organisations with the same ULA support fee can certify very different counts, one capturing twice the perpetual licenses of the other, and both will pay the same support afterward. The organisation that counted fully simply owns more for the same money. Where a higher number carries any consequence at all, it is not in support cost. It is in whether each deployment can be defended, which is a separate discipline covered below.
The belief that a bigger count costs more comes from applying the standard support model to a situation where it does not hold. It is reinforced by a natural caution: certifying a large number feels like claiming a large liability, so a conservative instinct says keep it modest. In a normal purchase that instinct is sound. In a ULA certification it is exactly backwards. Holding the number down does not reduce any bill. It reduces the perpetual entitlement you walk away with, permanently, in exchange for nothing. The instinct that protects you everywhere else costs you here, which is why naming the myth explicitly matters so much.
Consider two anonymized organisations leaving similar database ULAs in the same year, each paying a comparable annual support fee. The first treats the count cautiously and certifies a modest number of processor licenses. The second runs a disciplined maximization, capturing production, test, disaster recovery, and qualifying cloud deployments, and certifies a much larger defensible number. The figures below are indicative and each real outcome turns on the specific contract, but the pattern is reliable: the support line is the same for both, and only the owned entitlement differs.
| Organisation | Certified processor licenses | Annual support after exit | Permanent value captured |
|---|---|---|---|
| Cautious count | 1,200 (indicative) | Flat at ULA level | Lower, gap lost for good |
| Maximized defensible count | 2,600 (indicative) | Flat at ULA level, same fee | Far higher, no extra cost |
The second organisation owns more than twice the perpetual licenses for the same support spend. Nothing about the higher count raised a fee. That is the maximization opportunity in one line, and it is why we say the certified count is the one number where bigger is simply better, as long as it stays provable.
If support is not the limit, what is? Evidence. A certified number is only as strong as your ability to prove each deployment was genuinely live within the term and falls inside scope. A count padded with instances you cannot document does not cost more in support, but it becomes audit exposure in the first two years after exit, when Oracle is most likely to look. The right approach is therefore not to keep the number small, but to push it as high as the evidence supports and to document every deployment behind it. Maximization and defensibility are the same work done properly, never a trade off. Set the ceiling by your evidence file, then reach it.
Maximizing the count means capturing every environment you are entitled to count and standing each one up in time. Read deploying into DR and standby environments for the deployments most often overlooked, and coordinating engineering for the final push for mobilising the estate before the cutoff. For the full method, the ULA deployment maximization guide brings counting, evidence, and timing together.
No. Support continues at the ULA level after certification, set by the fee you already pay, not by the number you certify. A higher defensible count converts into more perpetual licenses at no extra support cost, which is why it is treated as free permanent value.
Because outside a ULA, support is normally a percentage of license value, so more licenses means more support. Inside a ULA the support fee is fixed at the agreement level through certification, so that intuition does not apply and pushes some teams to certify conservatively for no reason.
The only real constraint is defensibility, not support. A count you cannot evidence becomes audit exposure. The discipline is to certify the highest number your evidence supports, because that number carries no extra support charge and locks in maximum perpetual entitlement.
Book a confidential assessment and we will push your certification as high as the evidence supports, with no effect on your support bill and full documentation behind every license.