A German automotive manufacturer ran a heavy VMware estate under an expiring Oracle ULA. Oracle moved to count every host in the cluster. Here is how the buyer side defended the certified number and protected the saving.
A German automotive manufacturer faced an Oracle ULA certification with VMware virtualization in scope. The buyer side defended the host count, certified favorably, and protected a material saving at the exit.
An Oracle Unlimited License Agreement grants unlimited deployment of a named product set for a fixed term, usually three years. At the end the customer certifies how much was deployed.
That certified quantity converts into perpetual licenses. It is fixed for the life of the deployment, which makes certification the single most valuable event in the whole agreement. Oracle sets out the model in its Software Investment Guide.
During the term the customer deploys without counting. Most buyers treat this as a quiet phase. The buyer side view is the opposite. The term is when you build the certified position you will live with.
At expiry the customer declares deployed quantities. Oracle reviews the declaration through its License Management Services team. The number agreed becomes the permanent entitlement.
Once signed, the certification letter cannot be reopened in your favor. Under count and you lose deployment headroom forever. Over count and you carry shelfware you paid nothing extra to acquire but cannot monetize.
On a VMware estate the certified number is not driven by how many database instances run. It is driven by which physical hosts Oracle argues the software could run on across the cluster.
How Oracle and the buyer count Oracle on VMware
| Counting position | What it counts | Buyer side response |
|---|---|---|
| Every host in vCenter | All ESXi hosts the vMotion fabric can reach | Segment the cluster and pin Oracle to a defined host group |
| Cluster of record | Hosts in the cluster running Oracle | Document affinity rules and confirm in the contract |
| Contractual boundary | Only hosts named in the agreement | Hold the line on the signed product and territory scope |
Oracle does not recognize VMware as a hard partition. Its public partitioning policy treats soft partitioning as non binding for licensing. The audit team will therefore count every reachable host by default.
The signed agreement, not the policy document, governs the certified number. Where the contract names a product set and a territory, that language caps the count. The processor core factor table then converts physical cores into licensable processors.
The manufacturer ran a large VMware estate across two data centers. Oracle opened by counting every host in both vCenters. The buyer side narrowed that to the hosts the contract actually covered.
We pulled dated host inventories, affinity rules, and database deployment maps. The evidence showed Oracle ran on a defined host group, not the whole fabric.
We mapped the certification clause against the deployment. The signed scope did not extend to hosts that never ran an Oracle workload. That reading removed the disputed hosts from the count.
We drafted the certification letter to state the defended number precisely, with the supporting evidence attached. Oracle accepted the declaration after one review cycle.
The standard advice is to deploy as widely as possible before certification so the perpetual number is large. We disagree. In roughly three out of five VMware estates we certified, the wide deployment created audit exposure that cost more than the extra licenses were worth. The buyer side move is to deploy with intent onto a controlled host group, document the boundary as you go, and certify a clean defensible number. A smaller certified number you can prove beats a larger one Oracle can attack at the next audit. The certification is a legal event, not a land grab.
Source: Redress Compliance advisory engagement file, 2024 to 2025.
On VMware the certified number is decided by cluster design and contract language, not by how many databases you run. Win the boundary and you win the certification.
The manufacturer certified the defended number and protected a material saving against Oracle's opening count. The perpetual entitlement matched the real deployment.
The disputed hosts came out of the count. The certified processors reflected the dedicated Oracle host group, confirmed by the contract scope.
Measured against Oracle's opening position, the defended certification protected a saving in the 30 to 45 percent band. The number held at the following annual support review.
An Oracle ULA certification is the declaration of deployed quantities at the end of the unlimited term. Oracle reviews the declaration and the agreed number converts into perpetual licenses for the life of the deployment.
VMware matters because Oracle counts the physical hosts its software could run on, not the database instances actually running. On a shared cluster that can pull the count far above the real deployment.
No. Oracle treats VMware as soft partitioning under its public partitioning policy, so it does not limit the licensable scope. Buyers limit scope through cluster design and contract language instead.
No. The certification letter is permanent once signed. Under count and you lose deployment headroom forever, so the declaration must be accurate and defensible before it goes to Oracle.
Certification work should begin about 270 days before the ULA expiry. That window allows time to inventory the estate, capture affinity evidence, and model the defended number against Oracle's likely position.
Dated host inventories, vCenter affinity rules, and database deployment maps defend a smaller count. Evidence captured during the term carries far more weight than arguments made at the deadline.
A saving of 30 to 45 percent against Oracle's opening position is realistic on a well defended VMware estate. The exact figure depends on cluster design and the contract scope language.
No. Wide deployment can create audit exposure that costs more than the extra licenses are worth. Deploying with intent onto a controlled host group produces a cleaner, more defensible certified number.
Oracle ULA exit moves, certification framework, support reduction posture, and the buyer side moves across the Oracle Database, Java, and EBS estate.
Used across more than five hundred enterprise engagements. Independent. Buyer side. Built for procurement leaders running the next renewal cycle.
