A multi entity retailer reached the end of a three year ULA with significant deployment growth across acquired subsidiaries. The deployment count had been contested before our involvement.
The client was a multi entity retailer that had signed a three year Oracle Unlimited License Agreement covering Database Enterprise Edition and several options. Over the term, the group grew aggressively through acquisition, absorbing subsidiaries that deployed Oracle across their own data centres without central coordination. As the ULA neared its end date, the certification became the single most valuable event in the contract lifecycle.
At ULA exit, the customer certifies the number of processors deployed, and that count converts into a perpetual entitlement. Deploy more and certify accurately, and the customer locks in a larger perpetual licence at no additional cost. Certify low, through poor measurement or incomplete discovery, and the customer permanently forfeits entitlement it paid for. The stakes are asymmetric and final.
Before our involvement, the deployment count had already become contentious. Oracle's preliminary assessment, based on partial discovery data, ran well below the group's actual footprint. The acquired subsidiaries used inconsistent virtualisation, mixed physical and virtual deployment, and several environments had no clean inventory at all. A low certification would have cost the group tens of millions in forfeited perpetual entitlement.
The risk was compounded by time. Certification has a hard deadline tied to the ULA end date. A count that cannot be evidenced by the deadline cannot be certified. The group needed a complete, defensible, and documented deployment count across forty entities, built fast enough to meet the certification window.
We ran the certification as a structured discovery and evidence programme over fourteen weeks. The Measure phase began with a complete inventory of every environment in scope across all forty entities, reconciling the central CMDB against direct discovery on each host. The objective was to find every legitimate deployment the ULA entitled the group to certify, including environments that central IT had lost visibility of through acquisition.
Processor counting under a ULA is governed by precise rules. Each physical server's core count is multiplied by the applicable core factor, and virtualised environments must be counted according to Oracle's partitioning policy. We applied the core factor table line by line, documented the processor type of every host, and resolved each virtualised cluster against the contractual counting rules rather than against assumptions. Where the group ran approved hard partitioning, we evidenced it. Where it ran soft partitioning, we counted to the rule and did not overreach, because an indefensible count is worse than a conservative one at certification.
The discovery surfaced substantial legitimate deployment that Oracle's preliminary assessment had missed entirely, concentrated in the acquired subsidiaries. Each newly discovered environment was documented with its discovery evidence, its processor calculation, and its place in the group topology, so that every processor in the final count could be traced to a specific host with supporting data.
In the Negotiate phase we presented the certification as a complete evidentiary package rather than a number to be argued. Because every line was traceable to host level discovery and calculated against the contractual rules, Oracle had no basis to dispute the count. The preparation had anticipated the questions Oracle would ask and answered them in the package itself.
The certification declared 7,242 processors and Oracle accepted it without challenge. The Convert phase turned the certified entitlement into the baseline for the group's ongoing estate management, with a clean record of exactly what was certified and where, so that future deployment decisions could be made against a known perpetual position.
Certify low and you permanently forfeit entitlement you already paid for. The certification is the most valuable single event in the ULA lifecycle.
The certification declared 7,242 processors with zero disputes, locking in a perpetual entitlement valued at approximately $48M. The table compares Oracle's preliminary assessment with the certified count and shows where the recovered entitlement came from.
| Exposure category | Oracle claim | Settled |
|---|---|---|
| Oracle preliminary assessment | 5,100 | n/a |
| Acquired subsidiary deployment | +1,840 | certified |
| Reconciled core factor adjustments | +302 | certified |
| Final certified processor count | 7,242 | $48M |
The certified entitlement became a documented perpetual baseline rather than an open question. Every processor in the count is traceable to a specific host with supporting discovery evidence retained, so the group can defend the certification if it is ever revisited and can plan future deployment against a known position.
The group also exited the ULA with a clean topology record across all forty entities, ending the visibility gap created by acquisition. The next licensing decision, whether a renewal, a new ULA, or a move to cloud, now begins from a precise and evidenced understanding of what the group already owns in perpetuity.
For the buyer side perspective on this product line, our Oracle ULA negotiation team and our Oracle Database licensing practice work the same playbook on every engagement. Compare outcomes across the full case study library.
If a ULA is approaching its end date, certification preparation should begin twelve months out. A complete, traceable count is the difference between locking in entitlement and forfeiting it.
Request a Consultation