Oracle ULA exit & certification: how to certify a defensible deployment (2026)

An Oracle Unlimited License Agreement (ULA) lets you deploy certain products without counting during the term. At the end, you certify— you declare your deployed quantities, and those numbers convert into your perpetual entitlement. That one declaration is the whole game, and it’s where a defensible count matters most.

What certification locks in

The quantities you certify become your licenses going forward. Under-count and you permanently lose entitlement you paid for; over-state and you may carry support costs on more than you need. Either way, the number is fixed at the moment you certify — there’s no re-do.

The virtualization trap

If your Oracle workloads run on VMware or other soft-partitioned infrastructure, Oracle’s position is that the count includes every host the VMs couldrun on — not just where Oracle is actually installed. At certification, that can inflate the deployed number dramatically. Knowing where Oracle is installed, and on which hosts, before you certify is essential.

Reach certification with your own number

• Inventory every Oracle installation and the cores behind it well before the term ends.
• Understand how your virtualization topology affects the count under Oracle’s policy.
• Walk into certification with a traced deployment figure you can defend — not a last-minute scramble.

RenewalIntel gives you a traced deployment count across your estate that you can use as your own evidence going into a certification. It does not file or certify on your behalf, and it is not legal or licensing-advisory services — the certification decision, and the negotiation around it, belong with you and your advisor. What RenewalIntel provides is the measured number behind them.