Oracle audit and sales teams are asking Java customers to hand over a full list of their VMware hosts, including servers that have never run Java. Your Java bill does not depend on your VMware topology. Under the employee-based Java SE Universal Subscription, your headcount sets the price, not your servers. Outside counsel who defend Oracle customers report that the topology request serves a different purpose: it gives Oracle the data to build separate licensing claims against Oracle Database under its soft partitioning theory. Before you send anyone a server list, understand what that list can be used for.
What is Oracle asking Java customers for in 2026?
A list of every VMware host you run. Not every host running Java. Every host.
Attorneys at Tactical Law Group, a firm that represents enterprises in Oracle disputes, reported in April 2026 that Oracle has been conditioning Java subscription sales and renewals on customers disclosing “a full list of all VMware or other virtualized platform hosts, whether they have Java installed or not.”
Read that again. Whether they have Java installed or not.
Java audits used to be about where Java runs. Oracle’s traditional metrics needed to know which servers had the software. This request goes further. It asks for a map of your entire virtualized estate as the price of buying or renewing a Java subscription.
Why would a Java audit need servers that do not run Java?
It would not. That is the point.
Oracle changed Java licensing in January 2023. The current model, the Java SE Universal Subscription, is priced per employee. Every employee, not just the ones who use Java. If your company has 4,000 employees and 60 developers running Java, Oracle prices the subscription on 4,000. We broke down how that works in our guide to the Oracle Java employee metric.
You can dispute whether that metric is fair. Plenty of people do. But one thing about it is not in dispute: under a per-employee metric, your server topology is irrelevant to your Java cost. Ten VMware hosts or ten thousand, the Java price is the same.
So when a Java audit asks for your full VMware map, the honest question to ask is: what does this have to do with Java?
What does your VMware topology have to do with Oracle Database?
Everything. That is where the list gets used.
Oracle’s position on VMware is called soft partitioning. Under a policy document Oracle publishes, VMware virtualization does not limit licensing. In enforcement, per Tactical Law’s account, Oracle’s position is that every host connected to the same vCenter, or reachable by vMotion, must be licensed for Oracle software running anywhere in that environment, whether the software has ever touched those hosts or not.
Licensing specialists and outside counsel have noted for years that this partitioning policy is a policy document, not a term most customers ever signed. Attorneys at Scott & Scott LLP make the same point: Oracle’s standard Master Agreement nowhere expressly incorporates the partitioning policy. Oracle’s soft partitioning theory is Oracle’s interpretation, and it is the engine behind some of the largest audit claims in enterprise software.
Now connect the two. A complete VMware host list is exactly the evidence needed to price a soft partitioning claim against your Oracle Database estate. The Java conversation supplies the map. The Database claim uses it.
| What Oracle asks for in the Java conversation | What the Java subscription actually meters |
|---|---|
| Full list of VMware hosts, with or without Java | Total employee count |
| Cluster and topology details for your virtualized estate | Total employee count |
| Hosts running other virtualization platforms | Total employee count |
One column of that table prices your Java subscription. The other column prices something else entirely.
Can Oracle require a full topology disclosure?
That is a legal question, and we are not lawyers. This is not legal advice.
What we can tell you is that lawyers are contesting it. Tactical Law’s April 2026 analysis lays out three theories under California law: that conditioning a Java sale on unrelated topology disclosure may violate California’s Unfair Competition Law, that using audit rights from one product to build claims on another may breach the implied covenant of good faith, and that presenting customers with a choice between an expensive new metric, full disclosure, or business disruption may amount to economic duress.
Whether those arguments win is for courts and negotiations to decide. The practical takeaway is simpler. A topology demand attached to a Java deal is not routine paperwork. It is a decision point, and companies are pushing back on it.
What should you do before answering a topology request?
Know your own numbers before Oracle knows them. The sequence matters.
First, scope the request. What product is actually under audit or negotiation? A Java subscription discussion is about Java. Ask, in writing, how each requested data point relates to the license being discussed.
Second, know your real Java footprint. Which versions, which installations, which of them fall under paid terms versus older free-use terms. If your team cannot produce that list in 48 hours, assume there is exposure, and fix that before responding to anyone. Our guide to the first 48 hours of an Oracle Java audit covers the sequence.
Third, know your employee number and what the subscription would actually cost you. That is the number the Java deal turns on.
Fourth, bring licensing expertise in alongside counsel, not instead of counsel. Lawyers manage legal risk. Licensing specialists know how publishers construct claims, because the numbers are where audit claims are won or lost.
And if Broadcom pricing already has you rethinking the VMware estate Oracle wants a map of, start with our guide to your real VMware renewal options under Broadcom. The two conversations are more connected than they look.
Where UMS fits
We spent years running audits for the software publishers. We know what a topology list becomes once it leaves your hands. If Oracle is asking you for one, UMS Oracle audit defense will tell you what it is worth to them and how to respond on your terms.
Zero upfront. Paid only from what we save you. Book a free diagnostic before you send anyone a server list.
Frequently asked questions
Does VMware increase what I owe for Java? No. The current Java SE Universal Subscription is priced per employee. Your virtualization platform and server count do not change the Java price. If a Java conversation turns to your VMware estate, the cost at stake is likely Oracle Database, not Java.
Is Oracle’s partitioning policy part of my contract? In most cases the partitioning policy is a document Oracle publishes, not a term in the standard license agreement. Legal and licensing specialists have long drawn that distinction, and it matters in negotiations. Check what your agreement actually says before accepting a policy-based claim.
Do I have to respond to an Oracle audit letter right away? Audit clauses set notice periods and obligations, and they vary by contract. Do not respond, and do not send data, before you have read the audit clause and know your position. The first days set the tone for everything after. Our first 48 hours guide walks through it.
What if we only run free versions of Java? Verify it before you say it. Free-use terms changed across Java versions, and updates can quietly move an installation onto paid terms. “We only run the free version” is a sentence to prove, not to assume.
Source notes
- Oracle’s Newest Java Audit Demand: Your VMware Topology (Tactical Law Group, Pam Fulmer, April 19, 2026): the reported topology demand, the quoted language, and the California law analysis, all attributed.
- How to Understand Oracle’s Use of its Partitioning Policy for Virtualization (Scott & Scott LLP): the policy-not-contract distinction, corroborating source.
- UMS Oracle audit defense: the UMS service page for Oracle audit response.