Oracle Licensing Assessment
Sixt Germany — $4M Saved

Executive Summary: $4M Oracle Audit Claim Eliminated for European Mobility Leader

Sixt SE is one of Europe's leading mobility service providers, headquartered in Pullach near Munich, Germany. Founded in 1912, Sixt operates in over 100 countries with a fleet of hundreds of thousands of vehicles, supported by digital platforms serving millions of customers annually.

When Oracle's License Management Services (LMS) initiated a formal audit, Sixt faced a compliance report suggesting nearly $4M in licence shortfalls. The claim was driven by two primary vectors: Oracle's assertion that Sixt's entire VMware virtualised environment required licensing at peak capacity across all hosts, and a blanket enterprise-wide Java SE demand based on employee headcount.

By engaging Redress Compliance for an independent licensing assessment and audit defence, Sixt eliminated nearly the entire $4M claim. Only minor additional licences were required for a few genuine gaps — a 96% reduction in the claimed exposure.

Key takeaway: Oracle's audit claimed $4M based on peak-capacity virtualisation assumptions and blanket Java demands. Independent analysis reduced the genuine exposure to approximately $160K. The difference was Oracle's overestimation of virtual environment licensing and overcounting of Java deployments that required no commercial licensing.

The Challenge: Peak-Capacity VMware Claims and Java SE Exposure

Sixt's Oracle licensing situation reflected a common pattern for European enterprises operating large-scale digital operations on virtualised infrastructure. Rapid technology scaling had outpaced licensing governance, creating gaps that Oracle's audit process would exploit using their most aggressive methodology.

1. Oracle Database on VMware — The Peak-Capacity Dispute

Sixt ran Oracle Database Enterprise Edition across multiple data centres in Germany supporting its global reservation platform, fleet management systems, and business intelligence. The database infrastructure was hosted on VMware vSphere clusters — standard architecture for enterprises needing elastic, highly available compute. Oracle's audit introduced a particularly aggressive variant of the standard VMware licensing dispute: rather than simply claiming all hosts in a cluster required licensing (the standard soft partitioning argument), Oracle's LMS team assessed Sixt's environment at peak capacity — the maximum number of CPU cores ever observed across the entire cluster.

Sixt's VMware production environment comprised approximately 20 physical hosts. Oracle's peak-capacity methodology required licensing all 20 hosts at maximum core count — approximately 320 processor cores, translating to 160 Oracle Processor licences at the standard 0.5 core factor. At list price, the claim exceeded $2.8M in licence shortfalls.

2. Database Options and Feature Flags

Oracle's LMS tools also detected licensable database options — Diagnostics Pack, Tuning Pack, and Advanced Compression — across multiple instances. These features are commonly auto-enabled during Oracle Database installation and flagged by audit tools regardless of whether they are actually used. Oracle's initial claim for database options totalled approximately $400K.

3. Java SE — The All-or-Nothing Demand

Java was deployed across Sixt's environment — on application servers, development environments, desktop workstations, kiosk systems, and embedded within third-party applications. Oracle's audit identified hundreds of installations and demanded enterprise-wide Java SE subscriptions at approximately $15 per employee per month. For Sixt's workforce, this totalled approximately $800K annually.

Phase 1: Independent Database Assessment — Challenging Peak-Capacity Methodology

The highest-priority phase focused on Oracle's $2.8M database claim — specifically, dismantling the peak-capacity licensing methodology that inflated the scope far beyond Sixt's actual Oracle usage.

Comprehensive Discovery and Actual Usage Mapping

Redress Compliance deployed independent data collection across Sixt's entire Oracle estate, mapping every database instance to its physical host, VMware cluster assignment, and actual resource allocation. Critically, the team collected historical VMware performance data — vCenter statistics showing actual CPU allocation over a 12-month period, not theoretical peak capacity.

Dismantling the Peak-Capacity Argument

The advisory team built a three-layered defence against Oracle's peak-capacity methodology. First, VMware resource pools and DRS configuration restricted Oracle VM workloads to a dedicated cluster of 6 physical hosts. Affinity rules prevented Oracle VMs from migrating to the other 14 hosts. vCenter performance data confirmed that Oracle VMs had never exceeded their allocated resources or migrated outside the designated cluster.

Second, Sixt's Oracle licence agreement defined licensing based on the Processor metric — "the number of processors where the Oracle programs are installed and/or running." Oracle's peak-capacity interpretation extended this to processors where Oracle could theoretically run at maximum resource allocation — an interpretation not supported by the contract language itself.

The advisory team referenced prior audit resolutions where Oracle had accepted VMware segmentation as a valid licensing boundary. While each engagement is distinct, the pattern of Oracle ultimately accepting properly documented segmentation is well-established across the industry.

Database Options — Zero-Usage Defence

For the $400K database options claim, the team queried DBA_FEATURE_USAGE_STATISTICS across all database instances. The results confirmed that Diagnostics Pack, Tuning Pack, and Advanced Compression had been auto-enabled during installation but showed zero actual usage over the trailing 12-month period. The entire $400K options claim was withdrawn.

Phase 2: Java SE Assessment — From $800K to $60K

Oracle presented Java licensing as a company-wide obligation: because Oracle Java SE was installed across Sixt's environment, Oracle asserted that every employee required a Java SE subscription. For Sixt's workforce, this totalled approximately $800K annually.

Granular Java Inventory and Classification

The advisory team conducted a comprehensive Java inventory across Sixt's entire IT estate. Each installation was classified by version, distributor, commercial use context, and licensing obligation. Pre-April 2019 legacy builds, Java bundled with third-party software (vendor redistribution), and Java deployed as a component of other licensed Oracle products were documented with evidence of their exempt status.

Remediation and Cost Optimisation

The approximately 500 desktop and kiosk installations were the largest volume contributor to Oracle's headcount argument. The team coordinated with Sixt's desktop management team to deploy Eclipse Adoptium (OpenJDK) as the default runtime across all end-user devices, uninstalling Oracle JRE. This eliminated the headcount basis for Oracle's demand entirely. For the approximately 70 production servers running Oracle JDK with post-April 2019 updates in active commercial use, the team negotiated a targeted Processor-based Java subscription — not the employee headcount model. Annual cost: approximately $60K versus $800K demanded. A 92.5% reduction.

Phase 3: Audit Defence — Countering Oracle and Closing the Audit

The advisory team prepared a comprehensive response document — over 50 pages with supporting evidence — addressing each Oracle LMS finding systematically. Oracle LMS initially resisted the VMware segmentation defence, repeating their standard position that VMware constitutes soft partitioning. The advisory team's counter-response emphasised three points Oracle found difficult to dispute: the contract language does not reference Oracle's Partitioning Policy; vCenter performance data objectively contradicted the peak-capacity claim; and the segmentation configuration predated the audit, demonstrating it was not created after the fact.

After two rounds of formal response over approximately 10 weeks, Oracle LMS progressively conceded. The peak-capacity database claim was reduced to the 6-host scope. The options claims were withdrawn entirely. The Java claim was narrowed to the targeted scope Sixt had already addressed. Final resolution: approximately $160K in genuine additional licences required — representing a 96% reduction from the initial $4M claim.

Results Summary and Long-Term Impact

Sixt rejected Oracle's proposed multi-million dollar "settlement" package — a well-known Oracle tactic using audit urgency to drive purchasing decisions before the customer can independently validate claims. With the audit resolved factually, the proposed bundle lost its justification. Sixt avoided a multi-year commitment that would have locked in significant unnecessary spend.

Post-audit, Sixt implemented a formal change-management process for any modifications to VMware clusters hosting Oracle workloads. All new Java deployments default to OpenJDK (Eclipse Adoptium). Oracle JDK installation on any system requires explicit procurement approval with licensing justification. Quarterly automated scans detect and flag unauthorised Oracle Java installations.

"When Oracle auditors reported massive compliance gaps, we sought expert help. Redress Compliance came in and changed the outcome. Their in-depth knowledge of Oracle Database licensing in virtualised environments and Java licensing rules enabled us to demonstrate that we were not under-licensed, as Oracle claimed. The outcome was a fraction of what Oracle demanded."

Key Lessons: What European Enterprises Should Know About Oracle Audits

Question the licensing methodology, not just the numbers. Oracle's choice of methodology (peak capacity, full cluster, per-host) determines the claim size more than any individual finding. Challenge the methodology itself before accepting any numbers.

Reject "settlement" pressure during active audits. Any proposal presented during an audit should be evaluated independently — after you understand your actual position. Oracle's sales team earns commissions on these deals.

Engage independent expertise immediately. The window between receiving findings and responding is critical. Independent analysis before your first response prevents accepting flawed assumptions that compound through the negotiation.

Document actual Oracle resource consumption. Gather VMware performance data showing actual CPU allocation over time — not theoretical peak capacity. Historical vCenter data is your primary evidence against peak-capacity claims.

For European companies, GDPR data minimisation principles provide a legitimate framework for controlling what information you share during Oracle audits. Provide only contractually required and technically necessary data.

How Redress Compliance Supports Oracle Audit Defence

Redress provides end-to-end Oracle audit defence: independent assessment, data submission management, LMS finding challenges, formal response preparation, and settlement negotiation. All fixed-fee with no Oracle commercial ties. European presence (Dublin office) with global delivery. 80+ enterprise Oracle audit defences completed, with an average claim reduction exceeding 72%.

Sixt's outcome is consistent with results across Oracle licensing assessments in diverse industries and geographies. The pattern of Oracle LMS overstating compliance exposure — and independent assessment dramatically reducing claims — is remarkably consistent across engagements spanning mobility, energy, telecom, retail, SaaS, and beverages sectors.

See also: NOV Inc. $22M ULA certification, Pernod Ricard $4M audit resolution, and ADNOC $6M assessment.

Frequently Asked Questions

What is Oracle's peak-capacity VMware licensing methodology?

Oracle's standard VMware claim is that all hosts in a cluster require licensing. The peak-capacity variant goes further: licensing at maximum theoretical resource allocation — as if Oracle could consume every CPU in the cluster at once. This methodology is not supported by Oracle's contract language, which defines licensing based on where software is "installed and/or running." VMware DRS affinity rules that restrict Oracle VMs to designated hosts limit the licensing scope to those hosts only.

Can auto-enabled Oracle database options be excluded from audit claims?

Oracle Database Enterprise Edition automatically enables several licensable features during installation. Oracle LMS flags these as "in use." However, DBA_FEATURE_USAGE_STATISTICS shows actual usage. Zero usage means the option has never been actively invoked — and zero-usage evidence has consistently been accepted as grounds for excluding options claims from audit settlements.

How much can enterprises save on Oracle Java licensing?

Enterprises typically save 70 to 93% compared to Oracle's enterprise-wide headcount subscription. The approach: migrate desktop and endpoint Java to OpenJDK, document exempt installations (legacy versions, third-party bundles, Oracle product components), and licence only production servers running commercial Oracle JDK using Processor-based pricing.

📑

Oracle Audit Defence Playbook

Step-by-step guide to challenging Oracle LMS audit claims on VMware licensing, database options, and Java SE. Used by enterprise IT and procurement teams across Europe and North America.

Download Free →