A UK media group faced Oracle Database exposure on VMware and a steep Broadcom subscription restructure at once. This buyer side case study shows how both risks were contained in a single coordinated move.
Oracle Database on VMware and a Broadcom subscription restructure hit the same estate at once, and handling them together avoided 18 million dollars of exposure.
Oracle treats VMware clusters as soft partitioning, so its audit position is that you license every host the database could ever run on. This stance flows from Oracle's partitioning policy, which is not contractual but is asserted in audits.
On a large cluster, that turns a handful of needed licenses into a full estate claim. For this media group, the gap was about 18 million dollars.
Pinning Oracle workloads to defined hosts and isolating them in a dedicated cluster narrows the footprint. The wider Oracle Database licensing rules then apply only to that boundary.
Broadcom moved VMware from perpetual licenses to subscription bundles centered on VMware Cloud Foundation. Standalone products were folded into the bundle and priced per core.
For many estates the restructure raised cost sharply. The media group faced a renewal that bundled capacity it did not fully need.
VMware perpetual versus Broadcom subscription
| Dimension | Perpetual era | Broadcom subscription |
|---|---|---|
| Licensing basis | Per socket perpetual | Per core subscription |
| Packaging | Standalone products | VCF bundle |
| Cost trajectory | Support renewals | Subscription uplift |
| Buyer lever | Maintain or drop support | Right size the core count |
The key decision was to treat Oracle and Broadcom as one problem on one estate. Isolating Oracle onto a dedicated cluster also shaped the VMware core count the group needed from VMware Cloud Foundation.
That single architectural change cut the Oracle footprint and reduced the Broadcom subscription scope at the same time. Public Broadcom acquisition context is tracked on Broadcom news.
Handled separately, each vendor would have sized to a worst case. Handled together, the same hosts solved both problems, and neither vendor set the scope alone.
The common advice is to either buy enough Oracle licenses to cover the whole cluster or rip Oracle off VMware entirely. We disagree. In the Oracle on VMware cases we reviewed, both extremes cost far more than needed. Buying full cluster coverage pays for hosts the workload never touches, and a forced migration carries its own large bill. The buyer side move is architectural containment: isolate Oracle onto a defined, license bounded cluster so the footprint matches the workload. For this media group that approach contained roughly 18 million dollars of exposure without buying a single additional Oracle license.
Source: Redress Compliance advisory engagement file, 2024 to 2025.
We stopped treating Oracle and Broadcom as separate negotiations. One cluster redesign shaped both, and the eighteen million dollar Oracle exposure never turned into a purchase.
Oracle treats VMware as soft partitioning, so its audit position is that you license every host the database could run on, including hosts vMotion could reach. The position rests on Oracle policy rather than contract, but it is asserted aggressively in audits.
Yes, with architecture. Pinning Oracle workloads to defined hosts and isolating them in a dedicated cluster narrows the licensable footprint to that boundary. Containment, documented and enforced, is what holds the position in an audit.
Roughly 18 million dollars. A full cluster licensing position would have required that spend. Architectural containment matched the Oracle footprint to the actual workload, so no additional Oracle licenses were purchased.
Broadcom moved VMware from perpetual licenses to per core subscription bundles built around VMware Cloud Foundation. Standalone products were folded into the bundle, which raised cost for many estates unless the core count was right sized.
Because the same hosts drove both problems. Isolating Oracle onto a dedicated cluster also shaped the VMware core count needed. Handled separately, each vendor would have sized to a worst case, so coordination avoided a double squeeze.
No. The estate stayed on VMware Cloud Foundation but with a redesigned layout and a right sized core count. The savings came from architecture and bundle discipline, not from a disruptive platform migration.
It is when it is documented and enforced. The defensible position requires hard host affinity, isolation, and evidence that the workload cannot move outside the licensed boundary. Loose or undocumented pinning does not hold up.
The architecture redesign and dual vendor negotiation ran over a few months. The sequencing mattered more than the speed, because each vendor decision informed the other and neither set the scope alone.
A buyer side framework for the VCF bundle, the per core conversion, and the Broadcom renewal cycle. Includes the core count worksheet, the bundle interpretation guide, and the renewal leverage map used across recent VMware engagements.
Independent. Buyer side. Built for CIOs and procurement leads carrying VMware estates moving onto Broadcom subscription terms. No vendor influence. No sales kickback.
Open the playbook in your browser. Corporate email only.
Open the Playbook →
We have served 500+ enterprise clients across 11 publishers. Every engagement starts with one conversation.
VCF bundle movement, per core subscription pricing, Oracle on VMware audit patterns, Broadcom renewal data, and the wider commercial leverage signals across every engagement.
Once a month. Audit patterns, renewal benchmarks, vendor commercial signals across Oracle, Microsoft, SAP, Salesforce, IBM, Broadcom, AWS, Google Cloud, ServiceNow, Workday, Cisco, and the GenAI vendors. No follow up sales pressure.
Free providers (Gmail, Yahoo, Outlook) cannot subscribe. Work email only. Unsubscribe in one click.
