£0
Oracle compliance fees paid — down from an initial claim exposure of £2.4M
100%
Claim eliminated through technical evidence and licensing restructure
14 Weeks
From Broadcom audit notification to full resolution of Oracle exposure
£340K
Annual run-rate savings achieved through post-engagement optimisation
Client Background
The client is a UK-headquartered media and entertainment group operating across television production, digital content distribution, and advertising technology. With approximately 2,800 employees across the UK and Europe, the organisation runs a substantial technology estate supporting high-volume content workflows, real-time ad-serving platforms, and enterprise business systems.
The technology infrastructure included a significant VMware virtualisation environment—approximately 340 hosts across three data centres—supporting both production workloads and enterprise applications. Within this VMware estate, the client operated Oracle Database Enterprise Edition and Oracle WebLogic Server across multiple clusters, supporting a content management platform, a financial reporting system, and a legacy ad-trafficking application.
The client had a longstanding Oracle licence agreement comprising a mix of Processor-based and Named User Plus licences, last renewed in 2021. The Oracle deployment had grown organically, with databases provisioned by application teams without centralised licensing oversight.
The Trigger: Broadcom’s VMware Audit
In mid-2025, the client received a formal compliance audit notification from Broadcom following its acquisition of VMware. Broadcom had been systematically auditing VMware customers to verify licence compliance under the new subscription-based licensing model, which replaced VMware’s legacy perpetual licensing. The audit requested a full inventory of the client’s VMware deployment: hosts, vCPU allocations, vSAN configurations, and all workloads running within the virtualised environment.
The Broadcom audit itself, while commercially challenging, was manageable. The more dangerous consequence was what the VMware infrastructure inventory revealed about Oracle licensing exposure.
When the client’s IT team compiled the VMware host inventory for Broadcom, they discovered that Oracle Database workloads were running on VMware clusters containing far more physical cores than their Oracle licence entitlement covered. This is the single most expensive licensing trap in enterprise IT: Oracle does not recognise VMware as a “hard partitioning” technology. Under Oracle’s licensing policy, every physical core in a VMware cluster that could theoretically run an Oracle workload must be licensed—regardless of whether Oracle is actually running on those cores.
The client’s Oracle databases were deployed on two VMware clusters totalling 48 hosts with 1,152 physical cores. Their Oracle licence entitlement covered 96 Processor licences (192 cores with the 0.5 core factor for Intel processors). The potential Oracle compliance gap was 960 cores—representing approximately £2.4 million in back-licence fees plus ongoing support costs, based on Oracle’s list pricing for Database Enterprise Edition.
The client’s CTO contacted Redress Compliance for immediate advisory support.
Our Assessment: Separating Real Risk from Oracle Theatre
Our first action was to conduct a rapid technical and contractual assessment to determine the actual Oracle licensing position versus the theoretical worst-case exposure.
The assessment revealed three critical findings that fundamentally changed the risk profile.
Finding 1: The Oracle footprint was smaller than feared. Two of the four Oracle Database instances identified were test/development environments that had been provisioned years earlier and were no longer in active use. One had not processed a transaction in 14 months. These instances could be decommissioned immediately, removing their associated hosts from the licensing calculation.
Finding 2: Affinity rules were partially in place but undocumented. The client’s VMware administrators had implemented DRS anti-affinity rules that restricted Oracle VMs to a specific subset of hosts within the larger clusters. However, these rules were not documented as a licensing control, and Oracle’s licensing policy requires “hard partitioning”—which VMware DRS does not satisfy. Nonetheless, the existence of these rules demonstrated operational intent that supported our negotiation position.
Finding 3: The Oracle contract contained a favourable “designated system” clause. Buried in the 2018 ordering document was a clause that defined the licensed environment as specific server hardware identified by serial number. While this clause had not been updated when the workloads were virtualised, it provided a contractual argument that the licence grant was tied to specific physical capacity, not the entire VMware cluster. This was a negotiation lever, not a definitive defence—but it was a lever Oracle would need to address.
The Strategy: A Three-Phase Approach
Phase 1 • Weeks 2–4
Reduce the Technical Footprint
We worked with the client’s infrastructure and application teams to immediately decommission the two unused Oracle Database instances and uninstall Oracle software from the associated servers. We then migrated the two remaining production Oracle workloads from the shared VMware clusters onto a dedicated, isolated VMware cluster containing only 8 hosts (192 physical cores). We configured this cluster with strict DRS rules preventing Oracle VMs from migrating to any other cluster, and disabled vMotion between the Oracle cluster and the broader VMware environment. While VMware DRS still does not qualify as “hard partitioning” under Oracle’s policy, the physical isolation of Oracle workloads onto a dedicated, bounded cluster with no VM mobility to other hosts created a defensible technical position. The licensable core count was reduced from 1,152 to 192—exactly matching the client’s existing Processor licence entitlement of 96 licences (192 cores at 0.5 factor).
Phase 2 • Weeks 4–8
Build the Compliance Evidence Package
We compiled a comprehensive evidence package documenting the client’s current Oracle deployment in granular detail: the dedicated VMware cluster topology, the DRS isolation rules, the vMotion restrictions, the decommissioned instances with uninstallation evidence, the current licence entitlement mapped against the reduced core count, and configuration screenshots with timestamps. This evidence package was designed to be audit-grade—the same standard we would present if Oracle initiated a formal licence audit. We also identified and remediated the Enterprise Edition options (Diagnostics Pack and Tuning Pack) that had been activated without corresponding licences, either by disabling them or by sourcing existing unused option licences from the client’s entitlement stack that had been purchased but never tracked.
Phase 3 • Weeks 8–14
Manage the Oracle Relationship
Rather than waiting for Oracle to discover the exposure (which the Broadcom audit data could have triggered if shared or leaked), we proactively engaged the client’s Oracle account team with a carefully managed communication strategy. We presented the current, compliant state of the Oracle deployment—not the historical non-compliance. We demonstrated that the client’s Oracle licence entitlement fully covered the current deployment on the dedicated VMware cluster. We provided the evidence package as a voluntary compliance demonstration, positioning the client as a responsible, well-managed Oracle customer. We invoked the “designated system” clause from the 2018 ordering document to support the position that the licence grant was always intended to cover a defined physical capacity, and that the current dedicated cluster was the natural successor to that designated system. Oracle’s LMS (Licence Management Services) team reviewed the evidence, asked several clarifying questions over a 4-week period, and ultimately confirmed the client’s compliance without any additional licence requirement or back-fee claim.
“When the Broadcom audit uncovered our Oracle exposure, we genuinely believed we were facing a seven-figure compliance bill. Redress showed us that the actual risk was far more contained than Oracle would have had us believe, and their structured approach turned a potential disaster into a clean compliance position with zero additional cost. They saved us from a panic-driven settlement that would have cost millions.”
— Chief Technology Officer, UK Media Group
Additional Outcomes: Beyond Zero Fees
Resolving the Oracle compliance exposure was the primary engagement objective, but the work produced several additional outcomes that delivered ongoing commercial value.
£340,000 Annual Run-Rate Savings
The licence audit revealed that the client was paying Oracle support on several licence SKUs that were no longer deployed or needed. Two WebLogic Server licences had been retained from a decommissioned application, and the Named User Plus count for one database included 180 users who had not accessed the system in over two years. We negotiated the removal of these surplus licences at the client’s next Oracle support renewal, reducing the annual Oracle support bill by approximately £340,000.
Broadcom/VMware Audit Resolution
While the Oracle work was the highest-value intervention, we also supported the client through the Broadcom VMware audit. We reviewed the client’s VMware licence entitlements against the new Broadcom subscription model, identified legitimate areas of under-licensing that had resulted from organic growth, and negotiated a Broadcom compliance resolution that brought the client into full VMware compliance at a cost significantly below Broadcom’s initial position. The combined Broadcom and Oracle engagement gave the client a clean compliance position across both vendors.
Ongoing Oracle Governance Framework
We established a governance framework to prevent the client from drifting back into Oracle non-compliance. This included documented procedures for provisioning any new Oracle workloads (requiring licensing sign-off before deployment), quarterly VMware cluster reviews to verify Oracle VM isolation, an Oracle licence position dashboard that maps entitlements against actual usage, and a policy prohibiting Oracle workload deployment on shared VMware clusters without explicit licensing approval.
Lessons for Other Organisations
This engagement illustrates several principles that apply to any organisation running Oracle on VMware.
The Broadcom audit is not just about VMware. When Broadcom audits your VMware environment, the infrastructure inventory they request reveals your entire virtualised application landscape. If Oracle workloads are running on shared VMware clusters without proper isolation, the data produced for Broadcom creates a roadmap for Oracle licensing exposure. Treat any VMware audit as an Oracle licensing event as well.
Oracle’s “soft partitioning” policy is a negotiation position, not an absolute. Oracle’s official policy that VMware is not recognised as hard partitioning is well-documented and legally defensible on Oracle’s part. However, in practice, Oracle’s enforcement of this policy is influenced by the quality of your technical evidence, the contractual terms in your specific agreements, and the strength of your advisory representation. A well-documented, physically isolated VMware cluster with proper controls is a significantly stronger negotiating position than Oracle workloads scattered across shared clusters with unrestricted vMotion.
The first 48 hours matter. When the client discovered the Oracle exposure, their initial instinct was to contact Oracle directly and “self-report.” Had they done so without preparation, Oracle would have assessed the compliance gap based on the full 1,152-core VMware cluster—a £2.4 million starting position. By engaging independent advisory before contacting Oracle, the client had time to remediate, build evidence, and present the engagement from a position of demonstrable compliance rather than confession.
Old contract clauses have value. The “designated system” clause in the 2018 ordering document was a forgotten provision that the client’s procurement team did not even remember existed. It proved to be a material negotiation lever. Every Oracle licence review should begin with a forensic analysis of every historical contract document—not just the current order form.
Decommission before you negotiate. Removing unused Oracle instances and reducing the licensable footprint before engaging Oracle transformed the negotiation from a dispute about historical non-compliance into a confirmation of current compliance. Oracle cannot charge back-fees for software that is no longer installed.
Frequently Asked Questions
Can Oracle really require me to licence every core in a VMware cluster?+
Under Oracle’s published partitioning policy, yes. Oracle does not recognise VMware (or any software-based virtualisation) as “hard partitioning.” This means Oracle’s licensing policy requires all physical cores in a VMware cluster capable of running Oracle workloads to be licensed. In practice, the enforcement of this policy is influenced by the technical controls in place, the specific contract terms, and the strength of your negotiating position. Physical isolation of Oracle workloads onto dedicated clusters with restricted VM mobility creates a defensible position, though it does not eliminate the theoretical risk.
Does a Broadcom VMware audit expose Oracle licensing risk?+
Yes, indirectly. A Broadcom audit requires you to produce a detailed inventory of your VMware environment, including all hosts, clusters, and workloads. This inventory reveals exactly where Oracle workloads are running and on how many physical cores. If Oracle workloads are on shared clusters, the audit data documents the licensing gap. Even if Broadcom does not share this data with Oracle, your own internal teams now have documentation that could be discoverable in a future Oracle audit.
Should I self-report to Oracle if I discover a compliance gap?+
Not before you have remediated and built your evidence package. Self-reporting a compliance gap to Oracle before you have reduced the licensable footprint, decommissioned unused instances, and prepared audit-grade documentation gives Oracle maximum leverage. Remediate first, document the compliant state, then engage Oracle proactively from a position of demonstrable compliance. An
independent advisory can manage this process and the Oracle relationship on your behalf.
How quickly can Oracle licensing exposure be resolved?+
Typically 8–16 weeks for engagements of this complexity. The timeline depends on the size of the Oracle estate, the number of VMware clusters involved, the complexity of the migration to dedicated clusters, and the responsiveness of Oracle’s licence management team. The critical path is usually the technical remediation (migrating workloads and decommissioning instances), not the Oracle negotiation itself.
What does an engagement like this cost?+
Redress Compliance operates on a fixed-fee model—the fee is agreed before the engagement begins and does not change regardless of the outcome. For an engagement of this scope and complexity, the advisory fee was a fraction of the £2.4 million exposure that was eliminated. We do not take success fees or percentages of savings, ensuring our advice is commercially impartial.
Can this approach work for other virtualisation platforms?+
The Oracle licensing risk applies to any “soft partitioning” virtualisation technology, including VMware, Hyper-V, KVM, and Nutanix AHV. Oracle only recognises a limited set of “hard partitioning” technologies (Oracle VM, Solaris Zones, IBM LPAR) for licensing purposes. The remediation strategy of isolating Oracle workloads onto dedicated, physically bounded clusters applies regardless of the virtualisation platform. The specific implementation details vary, but the principle is the same.