Why This Assessment Was Triggered

The client — a Tier 1 beverages group headquartered in Paris, with manufacturing, distribution, and commercial operations across Europe, Asia-Pacific, and the Americas — had operated Oracle JD Edwards Enterprise One as its primary ERP for over a decade. Oracle Database ran the JDE data layer, with additional deployments across development, test, and analytics environments spanning multiple data centres in France, the UK, Singapore, and the United States.

Three events converged to make an independent licensing assessment essential: a proposed cloud migration to Microsoft Azure involving Oracle Database workloads, an internal audit team flag on Java deployments following Oracle's January 2023 licensing model change, and an upcoming Oracle support renewal at a contract value of approximately €7M per annum.

The client had not commissioned an independent Oracle licensing assessment in six years. The last review had been conducted by Oracle LMS directly — a review designed to identify non-compliance, not optimise spend.

"Our Oracle support renewal was the largest single software contract we renewed that year. We had no independent view of whether we were overpaying, where our compliance exposure sat, or what leverage we could take into the negotiation. That was the gap Redress filled."
— VP Technology Procurement, Global French Beverages Group

How to Use This Checklist

Each of the 20 checkpoints below corresponds to a discrete area assessed during the six-week engagement. For every item, the risk rating reflects the frequency with which Redress identifies material exposure in this area across Oracle assessments for global FMCG clients. The expert note captures the key insight from this specific engagement. Use this checklist as a structured framework for your own internal Oracle licensing review or as a brief before commissioning an external assessment.

Section 1 — JD Edwards Licensing Scope
01 Have all JDE modules in production use been mapped against your current User and Module licences? High Risk
Expert Note — What We Found In this engagement, three JDE modules were in active use — Advanced Pricing, Blend Management, and Campaign Management — without corresponding module licences. These had been activated progressively over four years by functional teams unaware of the licensing implications. The exposure exceeded €620,000 in retrospective licence fees at Oracle list price. Negotiated settlement reached €180,000 after audit-defence preparation.
02 Are Named User Plus counts reconciled against active directory headcount including contractors, temporary staff, and third-party system integrators? High Risk
Expert Note — What We Found JDE Named User Plus licences had been provisioned based on permanent employees only. The client's use of approximately 340 external contractors accessing JDE through a third-party logistics integration had never been factored into licence counts. Oracle's Named User Plus metric explicitly includes all individuals accessing the system, regardless of employment status. Regularising this exposure through an amended entitlement at negotiated rates cost €95,000 versus an estimated Oracle LMS finding of €480,000+.
03 Are all legal entities and subsidiaries within scope of your Oracle Master Agreement correctly listed and licensed? Medium Risk
Expert Note — What We Found Two recently acquired subsidiaries in Southeast Asia had been onboarded to the JDE environment under the parent company's Oracle agreement without the subsidiaries being added as licensed entities. Oracle's standard agreement requires explicit naming of each licensed entity. We identified this gap early and structured an amendment that added all subsidiaries at zero incremental cost as part of the broader support renewal negotiation.
Section 2 — Oracle Database Licensing
04 Has the processor licence count for Oracle Database Enterprise Edition been validated against the current physical server estate using Oracle's Processor Core Factor Table? High Risk
Expert Note — What We Found The client's Oracle Database EE processor count had been calculated five years earlier on a server estate that had since been refreshed to newer Intel processors. The Core Factor Table assigns a factor of 0.5 for Intel multi-core processors, but the calculation methodology used by the client's internal team was applying a factor of 1.0 — effectively halving available licence entitlement against actual requirement. Correcting this eliminated the perceived shortfall of 24 processor licences, representing a potential €1.2M unnecessary purchase that had been budgeted for the renewal.
05 Are Oracle Database Options and Packs (Partitioning, Diagnostics Pack, Tuning Pack, Advanced Compression) deployed only where explicitly licenced? High Risk
Expert Note — What We Found Oracle Database Options are among the most frequent sources of audit exposure. In this engagement, Diagnostics Pack and Tuning Pack features had been enabled by DBAs through Oracle Enterprise Manager without awareness that accessing these features requires a separate per-processor licence. Fourteen servers were running queries against AWR and ASH repositories — Diagnostics Pack features — without licence entitlement. Options licence fees at negotiated rates amounted to €240,000 and were incorporated into the renewal agreement at zero net incremental cost through commercial trade-off.
06 Are Oracle Database Standard Edition 2 deployments confirmed to be within the socket and RAC restrictions? Medium Risk
Expert Note — What We Found Two non-production Oracle Database Standard Edition 2 instances had been deployed on servers with four sockets. SE2 is restricted to a maximum of two sockets per server. The violations were in test environments and had been inadvertently inherited from a server refresh. Remediation required migrating the databases to compliant hardware — completed within three weeks at no Oracle licensing cost by identifying underutilised two-socket servers already within the licensed estate.
07 Are development, test, and QA Oracle Database environments properly licensed or correctly configured to use existing production entitlement under the applicable licence rules? Medium Risk
Expert Note — What We Found The client maintained 18 non-production Oracle Database instances. Oracle's licensing rules do not provide a free non-production entitlement — every instance requires licence coverage unless it is a passive failover standby. The client was licensing six of the eighteen environments, relying on a misunderstanding that internal development environments were exempt. Rationalisation of non-production instances from 18 to nine — retaining only those required for active development and pre-production staging — enabled the remaining environments to be covered within existing entitlement with a compliant deployment model.

Want to run this checklist against your Oracle estate?

Redress Compliance has completed 250+ Oracle licensing assessments globally. Download the full assessment guide.
Download Assessment →
Section 3 — VMware and Virtualisation Risk
08 Are Oracle Database workloads running on VMware clusters fully licensed for all physical processors in the cluster, or properly contained using Oracle-recognised hard partitioning? High Risk
Expert Note — What We Found This was the largest single exposure in the engagement. The client was running Oracle Database EE on VMware vSphere clusters. Oracle treats VMware as soft partitioning — requiring full licensing of all physical processors across the entire cluster, not just the processors allocated to Oracle VMs. The client had licensed only the processors allocated to Oracle VMs (16 processors), while the VMware clusters on which the VMs could run comprised 112 physical processors. The potential Oracle LMS exposure was approximately €2.8M. Remediation involved migrating Oracle Database workloads to a dedicated VMware cluster with no vMotion across the Oracle boundary — reducing licensed processor count from 112 to 28. This alone generated €2.1M of the €4M total saving.
09 Have Oracle workloads on VMware been reviewed in light of the Broadcom acquisition of VMware and resulting changes to VMware licensing and support commercials? High Risk
Expert Note — What We Found Broadcom's 2024 transition of VMware to subscription-only licensing significantly altered the cost calculus for Oracle-on-VMware deployments. Clients that had previously used VMware ELA agreements now face per-core subscription pricing that can increase VMware costs by 200 to 400 percent. Combined with Oracle's soft-partitioning position on VMware, several clients in this situation are accelerating migration of Oracle workloads to Oracle VM (OVM) or Oracle Exadata to achieve hard partitioning compliance and reduce VMware dependency simultaneously.
10 Are Oracle Database disaster recovery and standby instances configured and licensed correctly under Oracle's Data Guard rules? Medium Risk
Expert Note — What We Found Oracle's Data Guard licensing permits one passive physical standby instance per production licence for disaster recovery, provided the standby remains passive (not opened for reads or queries). The client's Singapore DR instance had been reconfigured to allow Active Data Guard read queries for reporting purposes — a feature requiring an additional Active Data Guard licence. This exposure (€110,000) was resolved by reverting the Singapore instance to passive standby mode and migrating the reporting queries to a separately licensed Analytics database.
Section 4 — Java Licensing Exposure
11 Has a complete Java inventory been completed across all servers, virtual machines, containers, and developer workstations covering Oracle JDK version and patch level? High Risk
Expert Note — What We Found Oracle's January 2023 shift to employee-based Universal Subscription pricing for Java made Java the fastest-growing Oracle licensing exposure across the Redress client base. In this engagement, Oracle JDK 17 and JDK 21 were deployed across 847 servers and 2,300 developer workstations. Under the new employee metric, the cost would be calculated against the client's 18,500-person workforce — generating a Java subscription fee of approximately €1.4M per annum at Oracle list price. Redress negotiated a Java subscription covering relevant deployment populations at €380,000 per annum, with confirmed savings of €1.02M annually versus Oracle's initial proposal.
12 Are any Oracle JDK deployments on versions eligible for free use under Oracle's OpenJDK builds (JDK 8u201 and earlier, JDK 11 GA), and have migration pathways been assessed for remaining paid deployments? Medium Risk
Expert Note — What We Found A subset of the client's Oracle JDK deployments ran on JDK 8u191 — a version covered by Oracle's No-Fee Terms and Conditions (NFTC) and therefore not requiring a subscription. Identifying and documenting these deployments as exempt reduced the subscription-eligible population and strengthened the client's negotiating position by demonstrating precise knowledge of their licensing position rather than accepting Oracle's blanket subscription proposal.
Section 5 — ULA, Support, and Commercial Strategy
13 If you hold an Oracle Unlimited License Agreement, have you modelled the certification position and assessed the gap between certified quantities and likely deployment at term-end? High Risk
Expert Note — What We Found The client held an Oracle ULA covering Oracle Database EE, WebLogic Server, and SOA Suite. The ULA was approaching its three-year term. Analysis revealed that actual deployment at certification would generate a certified quantity of approximately 180 processor licences for Oracle Database EE — 40 licences below the client's projected requirement post-cloud migration. Certifying at 180 processors and then purchasing 40 additional licences at list price would cost approximately €1.6M more than renewing the ULA and deploying to 220 processors before certification. This analysis directly shaped the renewal strategy.
14 Have you benchmarked Oracle support pricing against third-party support providers (Rimini Street, Spinnaker Support) for products on long-term maintenance or where Oracle roadmap investment is unlikely? Medium Risk
Expert Note — What We Found The client's Oracle support contract included legacy Oracle products — Forms, Reports, and certain Oracle Middleware components — where Oracle's development investment had effectively ceased. Third-party support providers offered equivalent functional support for these legacy components at 40 to 50 percent of Oracle support rates. Transitioning three legacy product lines to third-party support reduced the annual support bill by €280,000 while maintaining the Oracle Database and JDE support relationship for strategic products.
15 Has Oracle support been reviewed for licence lines where the underlying product is no longer deployed, and has a formal deletion request been submitted? Low Risk
Expert Note — What We Found Oracle does not proactively remove unused licence lines from support invoices. The client had five Oracle product lines for which deployment had been decommissioned between 18 months and four years previously, yet support fees continued to be paid. Identifying and submitting formal deletion requests for these lines eliminated €145,000 in annual support cost. Oracle support deletions are not automatic — they require written request and formal contract amendment.
Section 6 — Cloud Migration and Compliance
16 Has the planned migration of Oracle Database workloads to public cloud (Azure, AWS, GCP) been assessed for Oracle's Authorised Cloud Environment licensing rules? High Risk
Expert Note — What We Found Oracle's Authorised Cloud Environments policy governs how existing on-premises Oracle licences can be used on public cloud infrastructure. Licence mobility rules differ by cloud provider and product. The client's plan to lift-and-shift Oracle Database to Azure virtual machines required verification that existing processor licences could be applied without additional Oracle fees. We confirmed Azure's status as an Authorised Cloud Environment for Oracle Database and documented the compliant deployment configuration — preventing an unnecessary licence repurchase that had been assumed by the client's cloud migration budget.
17 For Oracle Database on Azure or AWS, has Bring Your Own Licence (BYOL) eligibility been confirmed and documented with Oracle, and have hyperscaler BYOL pricing terms been validated? Medium Risk
Expert Note — What We Found Azure's BYOL pricing for Oracle Database requires that the customer hold active Oracle support for the licences being brought. The client's planned reduction of Oracle support (through deletion of unused lines and third-party support migration) needed to be sequenced carefully to avoid invalidating BYOL eligibility for the licences earmarked for the Azure migration. We structured the support rationalisation to preserve BYOL eligibility for all production Database EE licences targeted for cloud deployment.
18 Has the Oracle Cloud Infrastructure (OCI) alternative been commercially evaluated, given Oracle's aggressive licence portability and discounting policies for customers migrating to OCI? Low Risk
Expert Note — What We Found Oracle's commercial incentives for OCI adoption — including licence portability at 2x density, Bring Your Own Licence discounts, and Universal Credit commitments — made OCI materially cheaper than Azure for pure Oracle Database workloads in certain configurations. The client's primary cloud was Azure (for M365 and broader application estate), making a full OCI migration impractical, but a selective OCI deployment for the most licence-intensive Oracle Database workloads was modelled. The analysis demonstrated €190,000 per annum infrastructure cost advantage for a specific analytics workload.
Section 7 — Audit Readiness and Negotiation Leverage
19 Is your Oracle licence position fully documented — ordering documents, assignment notices, support renewals, and deployment evidence — in a central, audit-ready repository? Medium Risk
Expert Note — What We Found The client's Oracle contract documentation was distributed across procurement, IT, and finance teams, with the oldest ordering documents held only in paper archives. A full contract reconciliation — matching entitlement to deployment — had not been performed since 2019. Reconstructing the complete licence position required six weeks and surfaced documentation gaps that, in an Oracle LMS audit, would have defaulted to Oracle's interpretation rather than the client's. Centralising documentation in a dedicated software asset management repository is the prerequisite for any Oracle negotiation — without it, Oracle holds the information advantage.
20 Has an independent commercial assessment of Oracle's renewal pricing been conducted against benchmarked market rates for comparable clients, and have negotiation levers been identified and sequenced? High Risk
Expert Note — What We Found Oracle's initial support renewal proposal represented a 7.4 percent increase on the prior year — framed as below Oracle's standard 8 percent annual uplift. The client's procurement team was inclined to accept. Benchmarking against Redress's database of comparable Oracle support contracts revealed the client's effective support rate (as a percentage of net licence value) was 22 percent — above the 18 to 20 percent achievable for clients of this scale and product mix. Combined with the commercial leverage created by the resolved compliance exposure, the ULA renewal modelling, and the confirmed third-party support migration, the negotiated renewal reduced annual Oracle spend from €7.0M to €5.3M — a €1.7M per annum reduction, representing 24 percent of the total €4M saving in year-one cash terms.

Confirmed Outcomes From This Assessment

€4.0M Total Year-One Savings
€1.7M Annual Support Reduction
6 wks Assessment to Negotiated Outcome

What Happens Without an Independent Assessment

Oracle's largest commercial risk to enterprise clients is not the formal LMS audit — it is the combination of incremental overpayment and missed optimisation that accumulates between audits. Without an independent baseline, Oracle support fees increase at 8 percent per annum compounding, unused licence lines remain on invoices indefinitely, and VMware virtualisation risks quietly expand as server estates are refreshed and VM migration policies evolve.

For this client, the €4M saving in year one was achieved without a single Oracle audit notification — the engagement was initiated proactively, before Oracle had any visibility into the client's estate. Proactive assessment is structurally advantageous: it generates the forensic documentation that neutralises Oracle's audit leverage, and it creates the commercial momentum that a reactive negotiation — triggered by an audit notice — rarely achieves.

Gartner estimates that 72 percent of Oracle customers experience significant licensing compliance issues when formally audited, with average audit-related true-up demands exceeding €5M. Redress Compliance data from 250+ Oracle assessments shows that clients who commission proactive assessments resolve exposure at an average of 28 cents on the dollar compared to clients who enter formal Oracle LMS proceedings without independent preparation.

Ready to run this assessment against your Oracle estate?

Download the full Oracle Licensing Assessment guide used in this engagement, including data collection templates.
Get the Full Guide →

Next Steps: Running This Assessment Yourself

The 20-point checklist above covers the most frequently material Oracle licensing risk areas for global FMCG and manufacturing enterprises. To run a credible internal assessment, you will need four capabilities: a complete licence entitlement inventory (all Oracle ordering documents, support renewals, and contract amendments from the past ten years), a deployment discovery capability that can identify Oracle software across physical servers, VMware clusters, containers, and cloud instances, benchmarking data on Oracle support rates and renewal pricing for comparable contract sizes, and experience of Oracle's negotiation mechanics — including the sequence in which commercial levers should be deployed to maximise outcome.

The first three capabilities can be assembled internally with sufficient time and SAM tool investment. The fourth is almost always the limiting factor — Oracle's sales organisation negotiates Oracle agreements every day. Most clients negotiate once every three to five years.

Stay Informed on Oracle Licensing

Oracle's licensing policies and audit tactics change frequently. Subscribe to the Redress Oracle knowledge hub for quarterly updates on Java, Database, JDE, and ULA strategy.

Visit Oracle Hub →