Oracle audit defense case study: How a firm with 100,000+ employees closed a Java dispute and a full Oracle audit without paying Oracle anything
In this Oracle audit defense case study, Oracle asked a global professional services firm for $42.5M for Java and, at the same time, claimed more than $12M in a license audit. We ran Oracle’s audit before Oracle could, took the Java requirement to zero, and the firm paid Oracle nothing on either.
Oracle demanded and claimed
$54.5M
$42.5M for a Java subscription, and $12M+ claimed in the audit
The firm paid
$0
Nothing for Java, and nothing for the audit
Client
A global professional services firm
Workforce
100,000+ employees
Oracle estate
74+ products, about 40 years of buying
Timeline
Java dispute for 3 years, then the audit from June 2025 to July 2026
The situation
Oracle came at the firm on two fronts at once: A $42.5M Java demand and a full license audit
Front 1Java SE subscription
$42.5M
Oracle’s opening ask for a five-year subscription
Oracle had pushed for years for a Java SE subscription priced on the firm’s total employee count. We were already advising the firm on Java under a separate engagement.
The employee metric was applied to the whole workforce of more than 100,000 people, and every Java install on servers and endpoints was treated as licensable.
Under challenge, Oracle came down to $20M, which was still a large spend that nobody had budgeted for.
Front 2Oracle license audit
$12M+
Oracle’s claim, repeated orally while the audit ran
A formal audit notice arrived in June 2025.
It covered Database and its options, WebLogic and other middleware, E-Business Suite, GRC, IDM, Hyperion, Oracle SaaS and, once again, Java.
Our own count found license gaps worth about $70M at list price, and more than $7M even at a 90% discount.
Even at Oracle’s best numbers, the firm faced more than $27M of spend. At Oracle’s opening positions, the exposure was much higher.
How we did it
We ran Oracle’s audit before Oracle could, across every server, endpoint and product
01
Collect
Scripts equivalent to Oracle’s own, Euladox and PowerCLI, run across every server and endpoint.
02
Entitlements
Every master agreement (OMA and OLSA), ordering document, support renewal and third-party bundle from about 40 years of buying.
03
Policy study
The licensing rules for each of the 74+ products deployed, studied one product at a time.
Technical and contractual fixes, and licenses the firm already owned moved to where they were needed.
06
Defend
Every letter to Oracle drafted, a strategy for every meeting, and a technical defense for every number.
Oracle audits with scripts, so we did too. The firm went into every Oracle conversation already knowing its numbers, and Oracle’s scripts had nothing new to find.
What we scanned, and how
Area
How we found it
What it produced
Database and options
Our own scripts, which match Oracle’s audit scripts
A server worksheet and a database feature-usage report
WebLogic and middleware
Scripts that check edition and feature usage
The edition in use, confirmed instance by instance
Virtualization
PowerCLI for VMware; auto-discovery for AIX, Solaris, HP-UX, Exadata and Hyper-V
A map of virtual machines to hosts, showing the licensable cores
Java SE
Euladox standalone on Windows, pushed through BigFix and SCCM; our scripts on Unix, Linux and macOS
An inventory of every install, classified by license
E-Business Suite
Separate scripts for each EBS product family
A report of responsibilities and usage
Oracle SaaS and OCI apps
Usage reports from the OCI admin consoles
Usage compared with what the firm subscribes to
Cross-check
ServiceNow SAM Pro hardware and software reports
The gaps in the SAM tool’s data, exposed
The firm’s ServiceNow data was used only as a cross-check, because of its known gaps.
Oracle Java
The Java demand fell from $42.5M to a contract worth $0
Oracle’s opening ask, five years$42.5M
Oracle’s best offer, once its count was challenged$20M
The contract the firm signed$0
−$20M avoided: no subscription was needed−$22.5M conceded by Oracle under challenge
Five levers took the Java requirement to zero
1
Move to OpenJDK
Oracle JDK replaced with OpenJDK builds wherever Oracle’s commercial features were not needed.
2
Third-party apps off Oracle Java
Vendor applications moved to non-Oracle Java runtimes, which took them out of Oracle’s count.
3
Exclude entities
Entities outside the licensable scope taken out of the employee count.
4
Covered by other Oracle products
Java used by licensed Oracle products is covered by those products' own rights.
5
Rights to older versions
Java versions released under earlier license terms kept in use where their conditions were met.
Every Java install was classified, one by one
This was an inventory of every install on every server and endpoint, with its host, path, publisher, version and product. On Windows, the Euladox standalone tool was pushed through BigFix and SCCM; on Unix, Linux and macOS, our own scripts did the work.
Non-Oracle Java
Vendor and other third-party builds
No Oracle license
OpenJDK
Open-source builds, including the systems we migrated
No Oracle license
Oracle Java on earlier terms
Versions under older licenses, such as the BCL and the NFTC
Free where the conditions are met
Covered by other Oracle products
Java bundled with Oracle products the firm had licensed
Already licensed
Oracle Java needing a commercial license
For example, OTN-licensed versions or use of commercial features
Remediated
Paid licenses needed
No commercial Java SE subscription for any of the 100,000+ employees Oracle wanted to count
0 systems
The audit
Three findings undercut Oracle’s audit position, and Oracle never put a claim in writing
01
Gaps in the SAM tool’s discovery
What we found
ServiceNow under-reported or misreported Database options, WebLogic editions and Java.
What it meant
Our Oracle-equivalent scripts gave the true picture first, so nothing Oracle’s scripts found would come as a surprise.
02
E-Business Suite over-use
What we found
Heavy E-Business Suite usage in places where the business did not need it.
What it meant
Access was cleaned up and rebalanced before any usage figures went to Oracle.
03
Duplicate purchases over about 40 years
What we found
The same products had been bought more than once, across decades of direct, partner and acquired-company contracts.
What it meant
Licenses the firm already owned covered deployments that would otherwise have looked unlicensed.
Underneath all three: a separate licensing-policy study for each of the 74+ Oracle products deployed.
The audit ledger, with Oracle’s numbers struck out
Item
Oracle’s position
Outcome
Oral audit claim
$12M+
$0
License true-up at list price (implied, approximate)
$70M
$0
License true-up at a 90% discount
$7M+
$0
Java SE subscription, five years
$42.5M, then $20M
$0
Written audit findings issued
Expected
None
Thirteen months from audit notice to closure
Prior yearsThe Java dispute runs; we advise the firm on Java
June 2025Oracle sends the audit notice
16 to 27 June 2025Scope agreed with the firm
2025Discovery and a baseline license position, in four streams
2025 to 2026Oracle repeats its $12M+ claim orally; we draft every response
July 2026The last discussion with Oracle
ClosureOracle goes silent, and the firm’s binding letter closes the audit with $0 paid
The results
$27M+ of exposure removed, counted at Oracle’s own best numbers
$27M+Saved at the least, counted at Oracle’s own best numbers
$20M+
Java subscription avoided
$7M+
License fees avoided, even at a 90% discount
$0
Paid to Oracle, on Java or on the audit
How we counted, conservatively
Java
Measured from Oracle’s best offer of $20M. Against its $42.5M opening ask, the saving is far larger.
Licenses
Valued at an assumed 90% discount: $7M+, against about $70M at list price.
Oral claim
The $12M+ Oracle claimed orally is not added on top.
Audit closed, $0 paid
Facing an Oracle Java demand or an audit?
Send us Oracle’s letter, the Java quote or the audit notice. A senior advisor will tell you within 24 hours where you stand, and how an Oracle audit defense or a Java license review would answer it.
1Discovery equivalent to Oracle’sOur own scripts and Euladox covered every server and endpoint. We did not rely on the SAM tool.
2A policy study for every product74+ products, each licensed differently, each studied on its own terms.
3Knowing how Oracle worksLed by a former Oracle Vice President. We know how Oracle India works, and how Oracle’s global approval and discount processes run.
4Partner-led and independentDelivered by partners, with no commercial ties to any publisher. Rythium earns only from its clients.
Managing Partner of Rythium Technologies. A former Oracle Vice-President (1998 to 2015) who now sits on the buyer’s side, and author of “Licensing Oracle”.
Vice President, Delivery and Operations at Rythium Technologies. Former CIO of Indian Oiltanking, with a 25-year career implementing Oracle applications.
The firm gave no formal testimonial. It has since taken calls from many of our prospects as a reference, and recommends us to others without being asked.
Questions about this case study
How did the firm avoid paying Oracle $42.5M for Java?
We challenged Oracle’s count first, and Oracle came down to $20M. We then showed that no subscription was needed: Oracle JDK moved to OpenJDK wherever Oracle’s commercial features were not needed, vendor applications moved to non-Oracle Java, entities outside the licensable scope came out of the employee count, Java used by licensed Oracle products was covered by those products, and older versions stayed in use under their earlier terms where the conditions were met. The final contract value was $0.
Did Oracle complete the audit?
No. Oracle repeated a claim of more than $12M orally through 2025 and 2026, but it never completed the audit or put a claim in writing. After the last discussion in July 2026, Oracle stopped responding, and the firm closed the audit with a binding letter. It paid Oracle nothing.
How long did the Oracle audit take?
Thirteen months, from the audit notice in June 2025 to the last discussion with Oracle in July 2026. The Java dispute had run for about three years before that.
How is the $27M+ saving calculated?
Conservatively. Java is measured from Oracle’s best offer of $20M, which is less than half of its $42.5M opening ask. Licenses are valued at an assumed 90% discount, $7M+ against about $70M at list price. The $12M+ that Oracle claimed orally is not added on top.
What did the discovery cover?
Every server and endpoint in the agreed scope, up to 2,500 servers and 120,000 endpoints, across on-premises data centers, AWS, Azure and OCI. We used our own scripts, which match Oracle’s audit scripts, Euladox for Java on Windows, PowerCLI for VMware and usage reports for Oracle SaaS, and the firm’s ServiceNow data only as a cross-check.
We use essential cookies to make this site work, and additional cookies to measure visits and our ads. You can reject the additional ones or choose which to keep. Privacy Policy