Certification is your one chance to convert unlimited Oracle deployment into a permanent entitlement, and Oracle has refined the mechanics to its own advantage. This guide explains what a ULA is, how certification works in 2026, and where the value is won or lost.
An Oracle ULA, an Unlimited License Agreement, grants unlimited deployment of named Oracle products for a fixed term, usually three to five years, for a fixed fee. When the term ends you either certify or renew. Certification converts your deployed quantities into a perpetual entitlement, declared in a letter the contract typically requires a C level executive to sign. The unlimited right then ends.
Whatever you fail to count, you lose. Whatever you cannot defend becomes audit exposure. Enter the window already knowing your number, measured independently and reconciled to your contract.
At the end of the term you declare how many Oracle processors, and where relevant Named User Plus, you have deployed. That declaration is the basis for your perpetual licenses. Production, test, and disaster recovery instances deployed inside the term all matter, and the count rests on processor counting with core factors. The evidence behind the number matters as much as the number itself: server lists, tool output, and methodology documentation that hold up under later scrutiny.
Oracle LMS scripts are one way to gather that data, but running them is a choice rather than an obligation, and the decision deserves analysis. The point of preparation is to reach the window with a count that is both complete and defensible.
Not every unlimited agreement behaves the same way. A capped ULA limits the otherwise unlimited right. A hybrid ULA folds in cloud rights. A PULA, a perpetual ULA, is perpetual with no certification exit at all, which makes it a fundamentally different commitment. Knowing which you hold shapes every decision that follows.
There is no fee for certification itself. Support fees continue at the ULA level regardless of the count you certify, so a higher defensible number is free value. The common fear that certifying more will raise your support bill is a myth worth stating plainly, because it causes organisations to under count and surrender entitlement they already paid for.
A manufacturer first estimated 800 processors from production. Counting disaster recovery, non production, and a documented virtualized cluster lifted the defensible count to roughly 1,900 processors. Support was unchanged. The extra perpetual entitlement carried significant list value at no additional cost. Figures are indicative and depend on the specific contract language.
Certified counts often land 1.5 to 2.5 times higher than a first estimate once cloud, disaster recovery, and non production are handled properly. Most under counting comes from treating only production as real and ignoring everything else.
Cloud counting is contract specific. Many ULAs require deployments in AWS or Azure to run 365 continuous days to count toward the baseline, and some exclude public cloud entirely. Contracts are often silent on GCP, and silence is not inclusion. Where cloud does not count, eligible workloads can be repatriated on premises or moved to OCI before exit.
Under Oracle's partitioning stance, soft partitioning does not limit scope, so entire VMware clusters can be swept into the count. Isolation, dedicated clusters, and documentation are the defense, and in a maximization context the same rule can work in your favour.
Customer definition, entity lists, and territory clauses bite at exit, especially after a merger or acquisition. Deployments in an entity or territory outside scope can trigger remediation demands, so corporate change during the term must be managed against the ULA clock.
If your ULA ends within 18 months, the work starts now. Build an independent baseline, resolve the cloud and virtualization questions, decide deliberately whether to certify or renew, and assemble the evidence file that protects the position afterward. Start with the pillar, the Oracle ULA certification guide, then read the products commonly covered by a ULA and when a ULA is the right deal.
There is no fee for certification itself. Support fees continue at the ULA level regardless of the count you certify, so a higher defensible number is free value. The belief that certifying more raises your support bill is a myth.
No. The certified count becomes your perpetual entitlement and the unlimited deployment right ends. That is why the number must be complete and defensible before the letter is signed, usually by a C level executive as the contract requires.
Begin 9 to 12 months before the term ends. That gives time to baseline the estate, resolve virtualization and cloud questions, stand up legitimate capacity, and assemble the evidence file that defends the count afterward.
Book a confidential assessment and we will tell you what your certification is really worth and how we would protect it.