Work through all 20 items. Mark each as compliant (✓), gap (✗), or unknown (?). HIGH-risk items represent the most common virtualisation audit triggers. Download our Oracle Audit Defence Kit for VMware licensing templates.
Section 1
Virtualisation Technology Classification
01
You have confirmed Oracle's classification of every virtualisation technology in your estate — specifically whether each technology is classified as hard or soft partitioning in Oracle's published Partitioning Policy.
High
Expert note: Oracle's Partitioning Policy is the definitive reference for virtualisation licensing. VMware ESXi, Microsoft Hyper-V, KVM, and Citrix XenServer are all classified as soft partitioning — meaning Oracle does not accept them as limiting the number of licences required. Only Oracle VM Server for x86 (with CPU pinning), Solaris Zones (with Solaris containers), IBM LPAR (AIX and Linux), HP vPar, Hitachi Virtage, and a small number of other technologies qualify as hard partitioning. Confirm every virtualisation technology in your estate against the current published policy.
02
For every VMware ESXi host running any Oracle software, you have determined whether Oracle's cluster-licensing rule applies — requiring licence coverage for all physical cores in the vSphere cluster, not just the host where Oracle resides.
High
Expert note: Oracle's position on VMware clusters is that all physical hosts in a vSphere cluster must be licensed if Oracle VMs can migrate between hosts via vMotion. A single 4-vCPU Oracle Database VM on a 10-host cluster with 32 cores per host requires 10 × 32 × 0.5 = 160 processor licences — not 4 × 0.5 = 2. This cluster-licensing interpretation can expand licence requirements by a factor of 80 or more in large VMware environments. If you have Oracle on VMware, this is almost certainly your largest single compliance risk.
03
You have documented the physical core count, processor model, and core factor for every VMware host in clusters where Oracle VMs can reside or migrate — including via DRS (Distributed Resource Scheduler) rules.
High
Expert note: Licence exposure in VMware environments is calculated on physical host capacity. DRS rules can limit VM migration to specific hosts within a cluster, which some organisations use to argue for a reduced licence scope. Oracle does not universally accept DRS-based host restrictions as equivalent to hard partitioning. However, DRS affinity rules combined with vSphere licensing restrictions can reduce the defensible scope in some circumstances. Document your DRS configuration and obtain specialist advice on whether it reduces your VMware licence scope before asserting it in any audit.
04
VMware vMotion has been explicitly disabled for Oracle VMs — or DRS affinity rules have been configured to prevent Oracle VM migration across the full cluster — and this configuration is documented and enforced by policy.
High
Expert note: If Oracle VMs cannot migrate to certain hosts, the licence obligation may be limited to the hosts they can reach. However, Oracle's audit methodology will review vMotion logs to determine whether Oracle VMs have ever moved to non-licensed hosts. A single historical vMotion event to an unlicensed host creates a compliance gap for the period of that deployment. Configure, enforce, and document VM migration restrictions before claiming a reduced licence scope — and retain vMotion logs to evidence compliance history.
05
You have assessed whether physically separating Oracle workloads onto dedicated, non-clustered VMware hosts — or migrating to Oracle VM (OVM) with CPU pinning — would reduce your licence obligation and at what cost.
Medium
Expert note: The most effective long-term solution to VMware licensing risk is physical segregation: Oracle VMs on dedicated hosts that are not part of a broader VMware cluster. This eliminates the cluster-licensing problem entirely. Oracle VM Server for x86 with CPU pinning is Oracle's preferred hard partitioning solution and is accepted as limiting the licence requirement to the pinned CPUs. Assess the infrastructure cost of either migration path against the licence saving to determine whether segregation is economically justified.
Oracle on VMware? Your exposure may be larger than you think.
Independent virtualisation licensing assessment. Buyer-side only.
Section 2
Specific Environment Risk Assessment
06
Oracle Database instances running on KVM hypervisors have been assessed against Oracle's partitioning policy — noting that KVM is classified as soft partitioning and requires full physical host licensing.
High
Expert note: KVM is increasingly common in Linux environments and private cloud deployments. Oracle classifies KVM as soft partitioning, requiring full physical host licensing. Organisations that deploy Oracle on Red Hat Enterprise Linux with KVM virtualisation — particularly in OpenShift or OpenStack environments — frequently underestimate their licence exposure. Confirm the KVM classification in the current Partitioning Policy and calculate your licence requirement based on full physical host capacity, not allocated vCPU count.
07
Oracle Database deployments in container environments (Docker, Kubernetes, OpenShift) have been assessed for their licence implications — noting that Oracle considers containers running on a host to require licensing of the full physical host.
High
Expert note: Containerised Oracle deployments are a growing area of compliance risk. Oracle's position is that containers do not constitute hard partitioning: if Oracle runs in a container on a host, the entire physical host must be licensed. Kubernetes pod scheduling — which can run Oracle containers on any node in the cluster — extends this exposure to every node in the Kubernetes cluster. Map every containerised Oracle workload against the physical infrastructure it can run on, and calculate the full physical host exposure.
08
Oracle deployments on AWS EC2 instances have been licensed using Oracle's Authorised Cloud Environment ratios (1 processor licence per 2 vCPUs for Intel/AMD, not the on-premises Core Factor Table), and only on EC2 instance types listed in Oracle's Authorised Cloud Environment document.
High
Expert note: Oracle licences BYOL workloads on AWS EC2 at a ratio of 1 processor licence per 2 Intel/AMD vCPUs — not using the Core Factor Table. The Core Factor Table applies only to on-premises deployments. Additionally, Oracle BYOL is permitted only on specific EC2 instance types listed in Oracle's Authorised Cloud Environments document. Deploying Oracle Database BYOL on an unapproved EC2 instance type — regardless of the licence count — constitutes a licensing policy violation. Confirm every AWS instance type against the current authorised list.
09
Oracle deployments on Microsoft Azure have been confirmed as running on Azure Dedicated Host or Bare Metal instances where required — and that BYOL licensing is applied correctly.
Medium
Expert note: Azure virtual machines share underlying physical hosts with other customers. Oracle's BYOL licensing on standard Azure VMs requires the same 1 processor licence per 2 vCPU calculation as AWS. However, Azure Dedicated Host (where you have exclusive use of the physical host) may allow for different licence calculations in some scenarios. Confirm your Azure Oracle licensing approach against the current Oracle Authorised Cloud Environments document and validate whether dedicated host configurations alter your licence obligation.
10
Oracle Fusion Middleware (WebLogic Server, SOA Suite) deployed in virtualised environments has been licensed for the full physical server capacity, not just the virtual machine allocation.
High
Expert note: Middleware licensing in virtualised environments carries the same risks as Database licensing. WebLogic Server and SOA Suite deployed on VMware hosts require licensing of the full physical cluster capacity — not just the VMs to which they are allocated. Middleware licensing is frequently overlooked in virtualisation assessments that focus exclusively on Oracle Database. Include every Oracle Fusion Middleware product in your virtualisation licensing analysis.
Section 3
Financial Quantification and Controls
11
You have run Oracle's LMS Collection Tool (OLCT) in your environment — under controlled conditions with specialist oversight — to understand what Oracle's audit team would discover if they ran it themselves.
High
Expert note: Oracle's LMS team uses the OLCT to enumerate every Oracle software installation, virtualisation configuration, and processor count in your environment. Running the OLCT before an audit — in a controlled manner with licensing specialist oversight — reveals your true compliance position before Oracle reveals it to you. The OLCT output shows exactly which deployments Oracle would identify, which virtualisation technologies it detects, and the resulting licence count Oracle would assert. Do not run the OLCT without specialist oversight: the output must be reviewed before any data leaves your environment.
12
Your virtualisation licensing risk has been quantified in financial terms — with a worst-case, base-case, and best-case exposure model — to inform the business case for remediation investment.
Medium
Expert note: VMware licensing risk is frequently described in qualitative terms ('we may have an exposure') rather than quantified financially. A 10-host VMware cluster with 24 cores per host running a single Oracle Database VM generates: 10 × 24 × 0.5 = 120 processor licences × Oracle Database Enterprise Edition list price of ~£40k = £4.8M in unlicensed exposure. When the financial exposure is quantified, the investment required to remediate it — through physical segregation, OVM migration, or licence purchasing — becomes a straightforward business decision.
13
You have a documented policy that prevents new Oracle software from being deployed in non-hard-partitioned virtualised environments without an explicit licensing review and approval.
Medium
Expert note: The most common cause of virtualisation licensing exposure is organic growth: DBAs deploy new Oracle instances on existing VMware infrastructure without triggering a licence review. Once the Oracle VM is live, the full cluster must be licensed. A change management gate that requires licensing sign-off before any Oracle software deployment in a virtualised environment prevents new exposure from accumulating. Implement this control in your ITAM and change management processes.
14
You have assessed the licensing implications of your VMware Broadcom migration — specifically, whether the migration introduces new host configurations, cluster boundaries, or VM mobility options that change Oracle's licence calculation.
High
Expert note: The Broadcom acquisition of VMware in 2024 caused many organisations to restructure their VMware environments — consolidating licences, changing subscription models, and in some cases moving to alternative hypervisors (KVM, Nutanix AHV, Proxmox). Any change to your VMware environment may alter Oracle's licensing calculation: new cluster boundaries, additional hosts, or changed VM mobility rules all affect the licence scope. Review Oracle licensing implications every time your VMware estate changes significantly.
15
Your IT asset management tool is configured to track Oracle software deployments at the virtualisation layer — including which VMware cluster each Oracle VM resides in — and generates alerts when Oracle VMs migrate to hosts outside the licensed scope.
Medium
Expert note: Standard ITAM tools track software deployments but do not typically model Oracle's cluster-licensing rule. Configure your ITAM platform to track Oracle VMs at the cluster level, flag any vMotion events that move Oracle VMs to hosts outside the licensed scope, and generate compliance alerts when new Oracle deployments are detected in virtualised environments. Without this visibility, VMware licensing exposure can grow undetected for months before an audit exposes it.
Section 4
Advanced Scenarios and Remediation
16
You have specifically assessed Oracle Java SE licensing in your virtualised environment — noting that under the 2023 employee-based model, Java on VMware is no longer calculated by host or vCPU but by total employee count.
Medium
Expert note: Oracle's 2023 Java SE employee-based model changed the virtualisation licensing calculus for Java significantly. Under the old Processor or Named User Plus model, Java on VMware required cluster-level physical host licensing. Under the employee model, Java is licensed per employee regardless of deployment configuration. If you transitioned Java to the employee model, the VMware cluster-licensing rule no longer applies to Java. However, any legacy Java Processor licences remaining on old contracts still require the full physical host calculation. Confirm which Java SE metric applies to each contract.
17
Oracle Exadata deployments are excluded from the general virtualisation licensing assessment — recognising that Exadata uses its own engineered system licensing model that differs from the standard partitioning policy.
Low
Expert note: Oracle Exadata uses a rack-based licensing model rather than the standard processor core factor and partitioning rules. Exadata customers license specific rack configurations (Full, Half, Quarter, Eighth rack) and are not subject to the VMware cluster-licensing rule in the same way as conventional server deployments. However, if Oracle Database licences from an Exadata are BYOL'd to other cloud or virtual environments, the standard partitioning rules apply to those off-Exadata deployments. Maintain a clear distinction between Exadata and non-Exadata Oracle deployments in your compliance documentation.
18
You have evaluated whether migrating Oracle workloads from VMware to Oracle Cloud Infrastructure (OCI) would eliminate the VMware licensing risk — noting that OCI Dedicated Region removes the partitioning problem entirely.
Medium
Expert note: Migrating Oracle workloads from VMware to OCI eliminates the VMware licensing risk, since Oracle licences OCI-based workloads on a subscription or BYOL basis with no partitioning policy complications. OCI Dedicated Region (a private cloud managed by Oracle on your premises) removes the compliance complexity of VMware cluster licensing for on-premises workloads. If your VMware licensing exposure is large, evaluate OCI migration economics against the cost of VMware licence compliance — for some organisations, OCI migration is the most cost-effective resolution.
19
You have retained all vMotion logs, DRS configuration records, and VMware cluster topology documentation for at least 3 years — to enable a historical compliance defence if Oracle audits past periods.
Medium
Expert note: Oracle's audit scope typically covers the current period and up to 3 years of historical deployment. If Oracle asserts that Oracle VMs have historically occupied unlicensed hosts, vMotion logs and DRS configuration records are your primary evidence for challenging that assertion. Retain these logs in a format that can be presented to Oracle's LMS team — and confirm that your VMware infrastructure team understands their obligation to preserve this data.
20
You have engaged independent Oracle licensing specialists — with specific VMware and virtualisation expertise — to assess your current virtualisation licence position and design a compliant, cost-optimised remediation strategy.
High
Expert note: Oracle's LMS team understands VMware licensing better than most IT departments. An organisation that self-assesses its VMware Oracle licensing without specialist support consistently underestimates its exposure. Independent Oracle specialists with virtualisation licensing expertise will calculate your actual exposure, identify the most cost-effective remediation path, and prepare the documentation needed to defend your position in an audit. At Redress, we have resolved VMware Oracle licensing disputes ranging from £500k to £8M — always from the buyer side.
"A single Oracle Database VM on a 10-host VMware cluster can generate £5–8 million in unlicensed exposure. We see this scenario in almost every Oracle audit involving VMware. The fix is straightforward — but only if you identify the problem before Oracle does." — Fredrik Filipsson, Redress Compliance
Interpreting Your Assessment Score
Count fully compliant items. Unknown answers should be treated as gaps for scoring purposes.
17–20
Strong Position
Controls mature. Schedule annual review to maintain as your estate evolves.
12–16
Moderate Exposure
Material gaps identified. Prioritise HIGH-risk items immediately and commission an independent review within 90 days.
0–11
High Exposure
Significant risk present. Do not engage Oracle commercially until independent specialists have assessed your position. Contact Redress immediately.
Oracle Virtualisation Licensing in 2026: The Highest-Value Audit Target
Oracle's LMS team regards VMware environments as the highest-value audit target in enterprise software licensing. The gap between how most organisations think about VMware Oracle licensing (vCPU-based) and how Oracle calculates it (full physical cluster) generates the largest single audit finding in our practice — regularly exceeding £1 million and frequently reaching £5–10 million for large enterprise environments. Unlike many compliance gaps that result from complex contractual interpretation, VMware licensing is clearly defined in Oracle's published Partitioning Policy: soft partitioning technologies cannot limit the licence requirement.
The remediation options — physical segregation, Oracle VM migration, or conventional licence purchase — all have a cost. But in every case we have assessed, the cost of remediation is lower than the cost of carrying the unquantified exposure into an Oracle audit. Contact Redress for an independent VMware Oracle licensing assessment before Oracle contacts you.