Executive Summary
New Look is a major fashion retailer headquartered in the United Kingdom, operating over 500 stores with a substantial e-commerce platform and thousands of employees globally. An internal compliance review in 2024 revealed significant Oracle licensing risks across both Java SE and Database. Oracle's new Java SE licensing model created unexpected subscription requirements across the estate, and Oracle Databases running on a shared VMware cluster created potential cluster-wide licensing exposure.
Oracle proposed an Unlimited Licence Agreement as the “solution” — a 3-year commitment covering Oracle Database Enterprise Edition and Java SE at a cost of approximately $3.5M. New Look engaged Redress Compliance for an independent Oracle licensing assessment. Redress identified that the actual compliance exposure was a fraction of Oracle's proposal, implemented targeted remediation, isolated VMware hosts, and negotiated a resolution that saved New Look $3 million while achieving genuine, defensible compliance.
Oracle's account teams frequently combine Java SE and Database compliance concerns into a single Unlimited Licence Agreement proposal. ULAs solve Oracle's revenue problem — not your compliance problem. An independent assessment almost always reveals that the genuine exposure is far smaller than Oracle's commercial framing suggests. Never accept a ULA as a compliance solution without independent analysis first.
Background and Context
Oracle's Role in Retail Operations
New Look is one of the UK's most recognisable fashion brands, founded in 1969 and operating over 500 stores across the United Kingdom, Republic of Ireland, and internationally through franchise partners. Oracle Database Enterprise Edition powers the company's point-of-sale (POS) transaction processing, inventory management across 500+ stores, e-commerce platform backend, and customer analytics. Oracle Java SE was even more pervasive: Java powered middleware integrations between POS systems and central databases, ran on in-store devices for inventory scanning, supported the e-commerce platform, and underpinned multiple back-office integration layers.
The central data centre ran a 10-host VMware ESXi cluster hosting Oracle databases alongside non-Oracle workloads. Under Oracle's policy that VMware is not approved hard partitioning, the company faced a potential requirement to licence all 10 hosts at full processor capacity — a dramatically inflated exposure versus the actual Oracle footprint.
Retail's Unique Oracle Licensing Exposure
Fashion retailers face a distinctive Oracle licensing profile. High transaction volumes require Enterprise Edition database features. Multi-site operations create distributed Java deployments that are difficult to track centrally. Oracle's Employee Metric pricing — introduced in January 2023 — calculates Java SE subscription costs based on the total number of employees in the organisation, regardless of how many actually use Java. For New Look with thousands of retail employees, this created a vastly inflated baseline that Oracle used as the foundation for its compliance claim.
The Challenges
Java SE Compliance Gap
Oracle's Employee Metric pricing treated every New Look employee as a Java licensing obligation. Java was deployed across servers, POS devices, middleware, and integration layers — but the vast majority of installations either did not require Oracle's commercial JDK or could be migrated to OpenJDK without business impact. Oracle's initial demand was approximately $600,000 per year under the Employee Metric model.
VMware Database Licensing Exposure
New Look's Oracle Databases ran on a 10-host VMware cluster at the central data centre. Oracle's cluster-wide licensing interpretation — claiming all 10 hosts required licensing at full processor count — produced a potential exposure of approximately $2M. This was the largest single driver of Oracle's compliance claim and the primary justification for the ULA proposal.
Oracle's ULA Push
Oracle's account team combined the Java and Database compliance concerns into a single commercial proposal: a 3-year Unlimited Licence Agreement covering Oracle Database Enterprise Edition and Java SE. This proposal — worth approximately $3.5M — would have locked New Look into a minimum 3-year commitment as a revenue maximisation tactic, not a genuine compliance solution.
Unlicensed Database Features
The internal review also revealed that several Oracle Database Enterprise Edition options and packs — including Advanced Compression, Partitioning, and Diagnostics and Tuning Packs — were enabled on production servers. Oracle's auditors had identified these as additional compliance exposure worth approximately $350,000 at full list price.
What Retail CIOs Facing Oracle Compliance Pressure Should Do
- Never accept a ULA as a compliance “solution” without independent analysis: ULAs solve Oracle's revenue problem, not your compliance problem — always quantify the actual gap before evaluating Oracle's commercial proposals
- Audit Java installations across all environments: Retail estates typically have Java on servers, POS devices, middleware layers, and internal applications — comprehensive discovery is essential before accepting Oracle's Employee Metric calculation
- Review VMware configurations for Oracle isolation: If Oracle databases can be confined to dedicated hosts with vMotion restrictions, the licensing exposure may be dramatically smaller than Oracle claims
- Check for unlicensed database features: Options and packs enabled without licences are a common hidden risk — disable or licence them before Oracle identifies them
Oracle combining Java and Database compliance into a ULA proposal?
How Redress Assessed and Resolved the Licensing Position
Phase 1: Effective Licence Position (ELP) Report
Redress conducted a comprehensive data collection across New Look's entire Oracle estate — deploying discovery tools to identify every Oracle Database instance (edition, version, features enabled, and deployment environment), every Java SE installation, and all VMware configurations relevant to Oracle's cluster-wide licensing interpretation. The ELP revealed that New Look's actual compliance gap was substantially smaller than Oracle's claims. The Java SE exposure could be reduced by over 80% through targeted remediation. The VMware database exposure could be eliminated entirely by isolating Oracle workloads onto dedicated hosts.
Phase 2: Java SE Remediation
Redress identified that the majority of New Look's Java installations — including middleware integrations, internal tools, and non-production servers — could be migrated from Oracle's commercial JDK to OpenJDK distributions without business impact. This migration reduced the Java SE compliance surface by over 80% while maintaining full functionality. For the remaining systems that genuinely required Oracle's commercial JDK — primarily specific POS integration components and e-commerce server processes — Redress negotiated a targeted subscription covering only the required installations. Annual Java SE cost was reduced from approximately $600,000 to $120,000 — an 80% reduction.
Phase 3: Database Licence Optimisation
Redress worked with New Look's infrastructure team to isolate Oracle Database workloads onto 3 dedicated VMware hosts within the 10-host cluster. vMotion was disabled for Oracle VMs via DRS affinity rules, creating a documented hard-partitioned boundary. This eliminated the cluster-wide licensing argument entirely: New Look's existing licences covered the 3 dedicated hosts. Redress also identified which Oracle Database options and packs were genuinely required for production operations and which had been enabled unnecessarily. Diagnostics and Tuning Packs were disabled on development and test environments. Remaining required features were licenced at a significant discount negotiated by Redress.
Phase 4: ULA Rejection and Negotiation
With the remediated compliance position documented, Redress managed all communications with Oracle. The corrected ELP was presented to Oracle's account team, demonstrating that the actual licensing requirement was approximately $470,000 — not the $3.5M ULA Oracle had proposed. Oracle's attempted path was a 3-year ULA at approximately $3.5M total. The Redress-optimised outcome was a targeted annual subscription of approximately $470,000 covering only genuine requirements — with no multi-year lock-in.
Results and Business Impact
| Area | Oracle's Claim / Proposal | Optimised Outcome |
|---|---|---|
| Java SE Subscription (Annual) | ~$600,000/year (Employee Metric) | ~$120,000/year (targeted — 80% reduction) |
| Database VMware Licensing | ~$2,000,000 (cluster-wide) | $0 (existing licences cover isolated hosts) |
| Database Options & Packs | Included in $3.5M ULA | ~$350,000 (targeted, 60%+ discount) |
| ULA Multi-year Lock-in | $3.5M over 3 years | Rejected — no lock-in commitment |
| Total Cost Avoidance | — | $3M+ across licensing and avoided commitment |
New Look achieved full Oracle compliance across Java SE, Database, and all enabled options and packs. The company avoided the $3.5M ULA commitment and replaced Oracle's inflated compliance demand with a targeted, right-sized annual spend. Governance improvements — including quarterly licence health checks, VMware host affinity controls, and centralised Java management — were implemented to prevent recurrence.
The Retail Sector's Oracle Licensing Blind Spots
Fashion and general retail enterprises consistently face the same Oracle licensing vulnerabilities. Distributed Java estates spanning stores, warehouses, and headquarters create a broad compliance surface under Oracle's Employee Metric model — but also a significant remediation opportunity if inventoried properly. VMware is pervasive in retail data centres, and Oracle's cluster-wide licensing position produces dramatic paper exposure that can almost always be addressed through host isolation. The significant hidden cost in retail Oracle estates is often not the headline database licensing — it is the combination of Java SE inflation and VMware exposure that Oracle leverages for ULA proposals.
Lessons Learned
A ULA Is Almost Never the Right Answer to a Compliance Problem
Oracle's ULA proposal was framed as a compliance solution. It was not. It was a multi-year revenue commitment that would have locked New Look into Oracle's highest-cost licensing model regardless of actual usage. Independent analysis is essential before evaluating any Oracle commercial proposal made in the context of a compliance concern.
Java SE Compliance Is Highly Manageable with Systematic Remediation
Oracle's Employee Metric pricing creates inflated paper exposure for any large enterprise. The remediation path — migrating non-critical installations to OpenJDK and licencing only genuine Oracle JDK dependencies — is well-established and achievable with limited disruption. New Look's 80% reduction in Java SE exposure is consistent with Redress's experience across comparable engagements.
VMware Host Isolation Is the Most Impactful Database Optimisation
Isolating Oracle databases onto dedicated VMware hosts is the single highest-value action available to enterprises facing Oracle's cluster-wide licensing position. The technical implementation — DRS affinity rules, vMotion restrictions for Oracle VMs — is straightforward and well-documented. New Look's isolation of 3 dedicated hosts eliminated a $2M exposure at zero incremental licence cost.
Negotiation Leverage Comes from Data, Not from Oracle's Timeline
Oracle's account teams use renewal deadlines and audit urgency to accelerate commercial decisions before customers can develop an independent view of their position. Understanding Oracle's contract levers requires time and expertise. Redress created the independent data platform that shifted the negotiation from Oracle's framing to a factual compliance discussion — which Oracle's team could not credibly contradict.