Why This Assessment Was Commissioned

The client — one of Europe's largest mobility and retail services groups, headquartered in Munich with operations spanning Europe, North America, Asia-Pacific, and the Middle East — had built a technology estate deeply dependent on Oracle. Oracle Database Enterprise Edition underpinned its central reservation systems, fleet management platform, and financial reporting infrastructure. Oracle E-Business Suite ran finance, procurement, and HR across the corporate group. Java SE was embedded throughout the customer-facing booking stack and a network of vendor integrations.

Three converging pressures made an independent Oracle licensing assessment urgent: Oracle had initiated a licensing review targeting the client's virtualised data centres, the incumbent Oracle support contract — valued at approximately €6.2M per annum — was approaching its three-year renewal point, and the client's CTO had commissioned an infrastructure refresh that would move significant Oracle Database workloads to a new VMware vSphere 8 environment and into the cloud.

The client had undergone an Oracle LMS-led review five years earlier. That review had focused on identifying non-compliance rather than optimising spend. No independent adviser had validated the current licence position, and the client had no structured methodology for assessing entitlement versus deployment across a technology estate spanning eight data centres and over 40 international subsidiaries.

"We knew we had Oracle complexity, but we had never seen it mapped end-to-end. When Redress showed us that our VMware configuration alone was creating a potential exposure of €2.3M — and that we could remediate it without changing our operational architecture — the value of the assessment was clear within the first two weeks."
— CTO, Global German Mobility Group

How to Use This Checklist

Each of the 20 checkpoints below corresponds to a discrete area assessed during the eight-week engagement. The risk rating reflects the frequency with which Redress identifies material exposure in this area across Oracle licensing assessments for global enterprise clients in mobility, retail, and technology-intensive sectors. The expert note captures the specific finding from this engagement. Use this checklist to structure your own internal Oracle licensing review, or as a brief before commissioning an independent assessment.

Section 1 — Oracle Database Processor Licensing
01 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 licence count had been calculated against an older server estate. Since that count was established, the organisation had refreshed three data centres to AMD EPYC processors. The Core Factor Table assigns 0.5 per core to Intel x86 multi-core processors but also 0.5 to AMD EPYC, yet the internal team was applying a factor of 1.0 to the AMD hardware — materially overstating the licence requirement. Correcting the calculation eliminated an apparent shortfall of 32 processor licences, avoiding a €1.52M unnecessary purchase that had been provisionally included in the renewal budget.
02 Are Oracle Database Options and Packs — including Diagnostics Pack, Tuning Pack, Partitioning, and Advanced Compression — deployed only on servers where they are explicitly licensed? High Risk
Expert Note — What We Found Oracle Database Enterprise Edition installs with CONTROL_MANAGEMENT_PACK_ACCESS defaulting to DIAGNOSTIC+TUNING, meaning AWR snapshots are collected and ASH data is logged from day one on every EE instance — regardless of whether the Diagnostics Pack is licensed. Across 22 Oracle Database EE instances in the client's estate, 14 had been logging AWR and ASH data for between two and six years without Diagnostics Pack entitlement. Oracle's DBA_FEATURE_USAGE_STATISTICS view retains this evidence permanently. We secured a negotiated settlement for the Options exposure at €310,000 — incorporated within the overall renewal at zero net incremental cost through commercial offset.
03 Are development, test, UAT, and QA Oracle Database environments properly licensed, or rationalised to operate within the entitlement of existing production licences? Medium Risk
Expert Note — What We Found Oracle does not provide free entitlement for non-production environments. The client was running 26 non-production Oracle Database instances across development, integration testing, and pre-production environments. Internal governance had historically treated development databases as exempt based on a misreading of the Oracle Technology Agreement. Rationalisation reduced the non-production estate from 26 to 11 instances — retaining environments required for active sprint cycles and compliance testing — and the remaining instances were brought within existing licence entitlement using a compliant hard-partition configuration on dedicated servers.
04 Are all licensed entities and subsidiaries within the Oracle Master Agreement scope correctly listed, including recently acquired or onboarded businesses? Medium Risk
Expert Note — What We Found Three subsidiaries acquired over the preceding four years had been onboarded to the Oracle Database and EBS environments under the parent entity's Oracle agreement without being formally added as licensed entities. Oracle's Master Agreement defines a "licensed entity" at signature — subsequent acquisitions require an amendment. We identified this gap before the Oracle review escalated and structured a single agreement amendment that added all three subsidiaries as licensed entities at no incremental licence cost, as part of a broader support renewal package.

Want to run this checklist against your Oracle Database estate?

Redress Compliance has completed 250+ independent Oracle licensing assessments globally. Download the full guide.
Download Assessment Guide →
Section 2 — VMware Virtualisation Exposure
05 Are Oracle Database workloads running on VMware fully licensed for all physical processors in the VMware cluster, or properly isolated using Oracle-recognised hard partitioning? High Risk
Expert Note — What We Found This was the largest single exposure identified in the engagement. The client was running Oracle Database Enterprise Edition on VMware vSphere 8 clusters shared with non-Oracle workloads. Oracle classifies VMware as soft partitioning, requiring all physical processors in any cluster where an Oracle VM can migrate to be fully licensed. The client had licensed processors allocated to Oracle VMs — 18 processors — while the shared vSphere clusters comprised 144 physical processors across six hosts. The potential Oracle LMS exposure at list price approached €3.4M. Remediation involved migrating Oracle Database VMs to a dedicated VMware cluster with hard partitioning controls preventing vMotion across the Oracle boundary. This reduced the licensed processor count to 24, generating €2.3M of the €4M total saving.
06 Have Oracle workloads on VMware been reviewed in the context of the Broadcom acquisition, including changes to VMware licensing models and support arrangements that affect Oracle licensing risk? High Risk
Expert Note — What We Found Broadcom's acquisition of VMware and the transition to VMware Cloud Foundation subscription pricing has created a secondary Oracle licensing risk: organisations that migrate from traditional per-socket VMware licensing to VCF may inadvertently create new vSphere cluster boundaries that expand the Oracle licensing footprint. The client had begun a VCF evaluation. We engaged Oracle's licensing counsel on the cluster boundary definitions under VCF and confirmed that hard partitioning controls must be explicitly configured and documented before any VCF migration to preserve the existing licence position. This pre-empted a potential compliance exposure on migration.
07 Are Oracle Database workloads on VMware or Nutanix that have been designated as Disaster Recovery standby environments confirmed as passive and correctly excluded from licence counting? Medium Risk
Expert Note — What We Found Oracle's licensing rules permit a passive standby replica — one that performs no processing and accepts no user connections beyond the standby replication mechanism — to be excluded from processor licence counting. The client's DR configuration in its Munich secondary data centre included two Oracle Database EE instances designated as standby. Examination revealed that one of the two was being used for reporting queries by the finance team — a business-as-usual workload that disqualified it from passive standby treatment. Remediating this required migrating the reporting workload to a compliant licensed instance and formally documenting the remaining instance's passive configuration for Oracle's review.
Section 3 — Oracle Java SE Compliance
08 Has the organisation assessed its Oracle Java SE exposure under the January 2023 employee-based subscription model, including all production, development, and embedded Java deployments? High Risk
Expert Note — What We Found Oracle's January 2023 Java SE licensing change replaced per-processor and Named User Plus metrics with an employee-based universal subscription. The new model requires a single subscription covering every employee, contractor, and temporary worker in the enterprise if Oracle Java SE 8u211 or later is deployed anywhere in the environment. The client had not formally assessed its Java position since the model change. An estate scan identified Oracle Java SE deployments on 847 servers and approximately 2,100 endpoints across the group. Under the employee-based metric, the applicable subscription covered approximately 38,000 employees and contractors — at Oracle's standard rate, this represented an annual exposure of approximately €1.1M per year for unsubscribed usage prior to our engagement. A negotiated four-year subscription agreement secured 34% below Oracle's standard rate.
09 Have all embedded or bundled Java SE distributions within third-party applications and middleware been identified and assessed against Oracle's licensing requirements? High Risk
Expert Note — What We Found Many enterprise applications — including monitoring agents, integration middleware, and vendor-supplied SaaS connectors — install Oracle Java SE as an embedded dependency. The client's technology team had not inventoried embedded Java distributions as part of its Java assessment. A more complete scan revealed 14 third-party applications embedding Oracle Java SE, six of which were running versions beyond the January 2023 licence change threshold. Oracle's audit team treats embedded Java instances as deployment evidence regardless of whether the installation was deliberate. We worked with affected vendors to confirm which applications provided NFTC or no-fee distribution rights, reducing the in-scope Java count by approximately 22%.
10 Has the organisation evaluated migration from Oracle Java SE to OpenJDK, Eclipse Temurin, or Amazon Corretto for workloads where migration is commercially viable? Medium Risk
Expert Note — What We Found Oracle Java SE migration to OpenJDK-based distributions is technically straightforward for most Java 8 and Java 11 workloads and eliminates Oracle Java licensing cost entirely for migrated applications. The client's reservation and booking platform — a high-transaction, Java-heavy application — was assessed for migration feasibility. A phased migration roadmap was developed covering 68% of Java deployment volume over 18 months. Completion of the migration phases would reduce the Oracle Java subscription scope by approximately 58%, yielding annual savings of €360,000 against the negotiated subscription rate. The migration roadmap was factored into the Oracle subscription term negotiation to avoid penalty provisions.
Section 4 — Oracle E-Business Suite Licensing
11 Have all Oracle EBS modules in active use been mapped against current module licence entitlement, including modules activated by configuration or integration without a formal licence request? High Risk
Expert Note — What We Found Oracle E-Business Suite module licensing requires an explicit licence for every module accessed, regardless of whether access was intentional or resulted from a default configuration. In this engagement, three EBS modules — Project Costing, Advanced Procurement, and iSupplier Portal — were in active use without corresponding licence entitlement. The iSupplier Portal exposure was particularly significant: Oracle classifies portal access by external suppliers as Named User Plus consumption even when users are not direct employees. Approximately 1,200 supplier contacts were accessing the portal. Settlement of the EBS module exposure cost €185,000 at negotiated rates against an estimated Oracle LMS exposure of €580,000+.
12 Are EBS Named User Plus counts reconciled against all active users including contractors, temporary staff, and third-party integrators with direct or indirect system access? High Risk
Expert Note — What We Found The client's EBS Named User Plus count was based on permanent headcount in the licensing review conducted five years prior. Since that time, the client had expanded its use of third-party logistics partners with direct EBS integration access, automated workflow agents counted under Oracle's Named User Plus metric, and a workforce of approximately 420 seasonal and temporary employees who accessed EBS HR and payroll modules during peak periods. Regularising the count through an amended entitlement cost €72,000 at negotiated rates — significantly below the potential retrospective exposure of €390,000 calculated at Oracle list price.
13 Has EBS licensing been reviewed in the context of Oracle's cloud transition strategy, including the Oracle Fusion Cloud Applications migration path and associated licensing trade-in or credit provisions? Low Risk
Expert Note — What We Found Oracle has been actively promoting migration from EBS on-premises to Oracle Fusion Cloud Applications (Oracle Cloud ERP), offering licence credit provisions for customers who commit to a Fusion Cloud subscription. The credit mechanism — which can offset up to 100% of the net new Fusion Cloud ACV against existing on-premises support — represents a commercially meaningful pathway for organisations carrying a significant EBS support liability. The client's EBS support at renewal was €1.4M per annum. A Fusion Cloud evaluation was initiated as part of the broader renewal negotiation framework, creating competitive pressure that contributed to a 19% reduction in the EBS support renewal rate without requiring commitment to cloud migration.
Section 5 — Support Renewal Optimisation
14 Has the complete Oracle support portfolio been audited to identify inactive, redundant, or terminated product licences that are generating annual support cost without active use? High Risk
Expert Note — What We Found Oracle's technical support policies provide that support fees for remaining licences may be repriced if only a subset of licences within an order is terminated — but this restriction applies within a single order line, not across the portfolio as a whole. The client's Oracle support portfolio contained 14 distinct order lines, several of which included products no longer deployed in production. Terminating support on four entire legacy orders — covering Oracle Forms and Reports, Oracle Portal, Oracle Designer, and an Oracle Middleware stack retired in 2021 — reduced the annual support bill by €420,000 with no repricing consequence on the remaining active orders.
15 Has third-party support been evaluated as a strategic alternative for legacy Oracle products where Oracle's Premier Support roadmap offers no further value? Medium Risk
Expert Note — What We Found Third-party support providers including Rimini Street and Spinnaker Support typically charge 50% of Oracle's annual support rate while providing equivalent or superior incident response SLAs for on-premises Oracle workloads. The client's Oracle Database licences supporting legacy financial reporting applications — not targeted for cloud migration within the planning horizon — were assessed as candidates for third-party support transition. Transitioning three legacy Oracle Database EE environments to third-party support at 50% of Oracle's rate saved €210,000 per annum while maintaining equivalent patch and incident support coverage. Oracle was informed of the evaluation as part of the renewal negotiation, which influenced a more competitive Oracle proposal on the remaining portfolio.
16 Is the Oracle support renewal being negotiated as a unified portfolio package, with cross-product leverage applied to secure concessions across the full contract value? Medium Risk
Expert Note — What We Found Oracle's standard renewal approach treats each product line separately, which limits the buyer's ability to apply leverage from one product area to another. The client had historically renewed Oracle support product-by-product at Oracle's standard 8% annual increase. By consolidating all Oracle support lines into a single multi-year commercial discussion — backed by a credible third-party support evaluation and a cloud migration assessment that reduced Oracle's perceived lock-in — the client secured a three-year multi-product agreement with zero annual increase in years one and two, a 3% cap in year three, and a €180,000 credit applied against year-one support fees. The combined support optimisation across portfolio rationalisation, rate negotiation, and third-party migration represented €780,000 per annum.

Approaching your Oracle support renewal in the next 12 months?

Redress Compliance has helped 250+ enterprises cut Oracle support costs by 20–40%. Start with the assessment guide.
Download Assessment →
Section 6 — Cloud Migration and BYOL Strategy
17 Has the organisation assessed Oracle's BYOL rules for each target cloud platform — OCI, AWS, Azure, and Google Cloud — before migrating Oracle Database workloads to the cloud? High Risk
Expert Note — What We Found Oracle's BYOL rules differ materially across cloud platforms. On OCI, Oracle permits full BYOL with no additional multiplier — one processor licence covers two OCPUs. On AWS, Azure, and Google Cloud, Oracle permits BYOL but with a different CPU mapping and without the OCI Support Rewards offset that allows cloud spend to reduce on-premises support fees. The client's cloud migration plan had been designed assuming AWS as the target. A modelling exercise demonstrated that migrating Oracle Database workloads to OCI instead — combined with the Oracle Support Rewards mechanism — would generate approximately €260,000 per annum in support fee credit against the on-premises Oracle support bill, improving the total cost of cloud migration materially against the AWS scenario.
18 If the organisation holds an Oracle ULA, has a pre-certification assessment been conducted to ensure all deployable and certifiable instances are correctly counted before the ULA term expires? High Risk
Expert Note — What We Found The client held a legacy Oracle Database ULA that expired during the assessment period. Oracle's ULA certification process requires the customer to declare all Oracle deployments in use at the certification date — the declared quantity becomes the perpetual licence entitlement. Under-counting deployments at certification creates immediate compliance exposure for any instance not declared. The client's draft certification count excluded three non-production Oracle Database instances that Oracle would treat as licensable. Correcting the certification prior to submission avoided a potential post-certification audit finding. Additionally, cloud deployments in OCI, AWS, and Azure are explicitly excluded from ULA certification counts — a point not understood by the client's internal team — and were addressed through a separate licence purchase at negotiated rates.
19 Is the organisation's cloud migration timeline aligned with Oracle's support roadmap for on-premises products, to avoid entering Extended Support or Sustaining Support at premium rates? Medium Risk
Expert Note — What We Found Oracle's Premier Support window for Oracle Database 19c extends to April 2027 under the Long Term Release policy, with Extended Support thereafter at a 10% premium and Sustaining Support at a 20% premium. The client's infrastructure refresh timeline had Oracle Database 12c R2 instances scheduled to remain in production until mid-2028 — beyond the Extended Support window into Sustaining Support territory. Accelerating the migration of 12c R2 instances to 19c (the current Long Term Release) ahead of the Premier Support boundary eliminated a projected Extended and Sustaining Support premium exposure of €95,000 over the out-of-support period.
20 Has the organisation established a formal Oracle governance framework — including quarterly licence position reviews, deployment controls, and pre-purchase sign-off — to prevent recurrence of the compliance exposures identified in this assessment? Low Risk
Expert Note — What We Found The majority of compliance exposures identified in this engagement had accumulated over three to five years due to the absence of a structured Oracle governance process. There was no formal mechanism for tracking Oracle deployments, no pre-purchase review for new Oracle product activations, and no annual reconciliation of entitlement versus deployment. Following the assessment, Redress implemented a lightweight Oracle Governance Framework for the client: a quarterly licence position dashboard, a deployment change log reviewed by the software asset management team, and a pre-activation checklist for any new Oracle product or feature enablement. The framework requires under four person-days per quarter to maintain and has materially reduced the client's Oracle compliance risk profile.

Engagement Outcomes — €4M Total Saving

€2.3M VMware Remediation Saving
€780K Support Renewal Optimisation (annual)
€920K DB, Java & EBS Exposure Settlement

The Compounding Risk of Inaction

Oracle's licensing compliance posture has hardened significantly since 2023. Oracle LMS initiated formal audit proceedings against a record number of European enterprise clients in 2024 and 2025, with average audit-related true-up demands across Redress's client base exceeding €3.2M per engagement. The root causes seen most frequently — VMware soft partitioning misconfiguration, unlicensed Database Options usage, and Java SE deployment without a subscription — are all areas where proactive assessment delivers remediation cost vastly lower than retroactive settlement.

For organisations in technology-intensive industries — mobility, retail, financial services, energy — where Oracle Database underpins mission-critical transaction systems and Java is embedded throughout customer-facing platforms, the annual cost of not knowing the licensing position routinely exceeds the cost of a full independent assessment by a factor of ten or more.

The German mobility group's €4M saving was achieved without any reduction in Oracle functionality, without operational disruption, and without weakening the organisation's technology platform. It was achieved by understanding the rules, correcting the configuration, and negotiating from a position of verified entitlement data rather than anxiety about an unknown compliance gap.

"The Redress assessment paid for itself within the first week when we understood the VMware exposure and the remediation path. The support renewal negotiation and Java strategy extended the return well beyond what we initially expected."
— VP Technology Procurement, Global German Mobility Group

Commission Your Assessment

Redress Compliance has completed more than 250 independent Oracle licensing assessments across Europe, North America, and Asia-Pacific. Our assessments cover Oracle Database, Java SE, Oracle E-Business Suite, Oracle Middleware, Oracle Cloud Infrastructure, and all major Oracle licensing constructs including ULAs, PLAs, and enterprise agreements. Engagements are scoped to the client's specific estate and commercial situation, and all findings are validated against Oracle's current licensing policy documentation before any commercial recommendation is made.

Download the Oracle Licensing Assessment Guide to understand the full assessment methodology, or contact Redress Compliance to discuss your Oracle licensing position.

Download the Oracle Assessment Guide →