A tier one Asian telecom group reached ULA expiry with deployment data it could not defend. This case study shows how a clean certification baseline turned a renewal trap into a controlled exit.
A leading Asian telecommunications group reached the end of an Oracle Unlimited License Agreement with deployment data it could not defend. This case study covers how a clean certification baseline turned a renewal trap into a controlled exit, and what other ULA customers can take from it.
The client is a tier one Asian telecommunications group serving tens of millions of subscribers across fixed and mobile networks. It ran a large Oracle Database estate under a multi year ULA. The identifying details are withheld.
The ULA was twelve months from expiry. The group had to decide whether to renew or certify and exit. It had no reconciled view of what it actually deployed.
The group faced a deadline, an estimate, and a vendor proposal built on that estimate. None of the three favored the buyer.
Oracle account contact intensified in the final two quarters. The message was consistent. Renew now to avoid a compliance gap at expiry.
Internal records counted licences by purchase order, not by live deployment. Nobody could state the certified database count with confidence.
Oracle proposed a renewal sized to a deployment estimate the group could neither confirm nor refute. The estimate became the negotiation anchor by default.
The work was a 14 week reconciliation. The goal was a defensible count, instance by instance, that the group could stand behind in front of Oracle License Management Services.
The discovered deployment was reconciled to ULA scope. Products inside scope counted toward certification. Products outside scope were flagged and remediated before exit.
Estimate versus certified baseline at the Asian telecom group
| Dimension | Oracle estimate | Certified baseline |
|---|---|---|
| Database processor count | Inflated by virtualization | Counted on production hosts |
| Enterprise Edition options | Assumed broadly deployed | Limited to confirmed use |
| Non production instances | Counted as production | Separated and right sized |
| Forward support basis | Renewal run rate | Fixed certified entitlement |
The largest exposure was virtualization. Oracle counting rules on shared clusters can sweep in hosts that never run a database.
The group ran Oracle Database on shared virtual clusters. Under aggressive counting, every host in a cluster can be claimed as licensable, even idle ones.
Diagnostics and tuning packs were installed by default on many instances but used on few. Installed is not the same as used, and against the Oracle technology price list the difference is real money.
Some workloads had moved to managed and cloud services. The counting rules for those differ from on premise and had to be handled separately.
The common advice is to certify out at the maximum measured deployment, on the logic that more certified entitlement is always better. We disagree. In this case, and in roughly six out of nine telecom exits we have run, the maximum count locked the buyer into perpetual support on instances that were idle, virtual, or non production. The buyer side move is to certify on the realistic production footprint plus a defensible growth band, then carry only that support stream forward. The group followed this and cut its forward support materially rather than freezing an inflated number.
Source: Redress Compliance advisory engagement file, 2024 to 2025.
The renewal was never the decision. The decision was whether the group could prove its deployment. Once the baseline was defensible, the exit was the easy part.
The group certified out on a production based footprint, passed certification with no findings, and moved to a fixed support entitlement.
The certified count was backed by instance level evidence. Oracle accepted it without an extended dispute, because the data answered the questions before they were asked.
Forward support dropped against the renewal Oracle had proposed. The group stopped paying for unlimited rights on an estate that had stopped growing.
The group kept the discovery tooling and the reconciled inventory. Future audits start from evidence, not from an estimate, which changes every later conversation with Oracle.
The case generalizes cleanly. The value did not come from a clever negotiation. It came from arriving with proof.
A defensible certification takes months. Begin the reconciliation at least 18 months before expiry so exit is a real option, not a bluff.
Certify on what runs in production plus a defensible growth band. Maximum measured deployment freezes cost you will carry for years.
Keep the inventory and tooling after exit. The same data that wins certification defends the next audit and frames the next renewal.
The client was a tier one Asian telecommunications group serving tens of millions of subscribers across fixed and mobile networks. Identifying details are withheld. It ran a large Oracle Database estate under a multi year Unlimited License Agreement that was twelve months from expiry.
The group had no reconciled view of its certified deployment. Internal records counted licences by purchase order, not by live deployment, so Oracle's renewal proposal was anchored to an estimate the group could neither confirm nor refute.
Oracle counting rules on shared virtual clusters can claim every host in a cluster as licensable, including idle hosts that never run a database. That inflated the apparent certified count by 20 to 40 percent before reconciliation separated real production from capacity.
Fourteen weeks. The work enumerated every host, virtual cluster, and database instance, mapped editions and options to actual use, and reconciled the result to ULA scope so the count was defensible instance by instance.
The group certified out on a production based footprint with no compliance findings and moved to a fixed support entitlement. Forward support dropped roughly 31 percent against the renewal Oracle had proposed, because the group stopped paying for unlimited rights on an estate that had stopped growing.
No. Exit wins when deployment has plateaued, as it had here. Renewal can still win when usage is growing fast or a major rollout is planned. The certified production footprint and the forward support math decide it, not a default preference.
Maximum measured deployment freezes support cost on instances that may be idle, virtual, or non production. Certifying on the realistic production footprint plus a defensible growth band carries a lower support stream forward, which is what cut this group's run rate.
Certification readiness, not negotiation flair, decides ULA value. Arrive with instance level proof of deployment and the exit becomes straightforward. Arrive with an estimate and the vendor's number becomes the anchor.
Oracle ULA exit moves, Java audit defense posture, certification framework, 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.
The group did not negotiate its way out of the ULA. It proved its way out. The certification baseline did the work the negotiation usually gets credit for.
