A buyer side handbook for the one window that turns unlimited deployment into permanent value. The mechanics, the counting, the cloud and VMware traps, and a workbook to maximize your defensible count.
An Oracle ULA certification happens once, and the number you declare becomes your perpetual entitlement. This handbook walks the whole exit on the buyer side: how certification works, how processors are counted with core factors, where cloud and VMware deployments quietly help or hurt your count, and a workbook you can run against your own estate before the window closes.
The handbook is built to be acted on, not admired. By the end you will know how Oracle frames the certification, which of your deployments count and which depend on contract language, and how to assemble an evidence file that holds up in the audit sensitive years that follow. The chapters move from structure to mechanics to a practical workbook.
How a ULA grants unlimited deployment for a fixed term and fixed fee, what certification converts and what it ends, and why a PULA is different because it is perpetual with no certification exit.
Why there is no fee for certification, why support stays flat at the ULA level regardless of the count, and why the fear that certifying more raises support is a myth that costs buyers real entitlement every year.
Processor counting with core factors, Named User Plus where it applies, production plus test and disaster recovery deployed within the term, and the evidence file that matters as much as the number itself.
Why cloud counting is contract specific, why many agreements require 365 continuous days in AWS or Azure, why silence on GCP is not inclusion, and how Oracle's partitioning stance can sweep a VMware cluster into the count for better or worse.
The handbook works real numbers so you can repeat the method. The example below applies Oracle core factors to a mixed estate. Figures are indicative and your environment and contract govern the result.
| Server group | Cores | Core factor | Processor licenses |
|---|---|---|---|
| Production x86 cluster | 640 | 0.5 | 320 |
| Test and development | 240 | 0.5 | 120 |
| Disaster recovery (within term) | 160 | 0.5 | 80 |
| Defensible total | 1,040 | 520 |
Indicative only. Core factors and what counts depend on the product, the platform, and your contract language.
CIOs, IT asset managers, procurement leads, enterprise architects, and general counsel at organisations holding an Oracle ULA, usually within eighteen months of expiry. If you are inside that window, the handbook is built for the decision in front of you.
The handbook will take you a long way on your own. When the stakes warrant it, book a ULA assessment and we will apply the same method to your estate.