Oracle License Review 2026: What to Expect and How to Prepare

What is an Oracle License Management Services Review?

Oracle License Management Services (LMS) — rebranded within Oracle as the License Management team — is Oracle's internal unit responsible for verifying that customers are using Oracle software in compliance with their licence agreements. In practice, this means sending a letter requesting that you allow Oracle to run diagnostic scripts on your infrastructure, compare the output against your licence entitlements, and present you with a compliance gap — usually expressed as a dollar amount owed.

What Oracle's outreach letter does not tell you is that the initial gap analysis is almost always overstated. Oracle's scripts are configured to catch the broadest possible deployment footprint. They count processor threads rather than physical cores where your contract specifies cores, they identify every server where Oracle software touches memory regardless of whether it's actively used, and they flag installations from years-old deployments that were decommissioned but never formally removed. The initial finding is not a final number — it's an opening position.

Enterprises that engage an experienced Oracle negotiation adviser before responding to LMS consistently reduce their exposure by 40-70% compared to those who engage Oracle directly or who retain general legal counsel without specific Oracle licensing expertise.

Why 2026 Is a Particularly Active Year for Oracle LMS

Oracle's fiscal year ends on 31 May. The period from January through May is when LMS activity peaks, as Oracle's sales and compliance teams push to close deals before year-end. If you have received an LMS letter between January and April 2026, you are not alone — this is precisely when Oracle deploys the most resources toward compliance reviews.

Several factors are accelerating LMS activity in 2026 specifically. First, Oracle's Java SE licensing change in January 2023, which moved from a per-processor metric to an employee-count metric, created a generation of retroactive compliance exposure that Oracle is now actively pursuing. Companies that transitioned to OpenJDK or alternative distributions after January 2023 but did not formally terminate their Oracle Java SE agreements may still owe fees for the period they held active agreements.

Second, Oracle's cloud migration push — particularly OCI and Oracle Fusion — means that Oracle is using LMS findings as leverage to convert on-premise customers to cloud subscriptions. The conversation frequently moves from "you owe us $4M in compliance fees" to "or you could move to Oracle Cloud and we'll credit $3M against your first-year subscription." This is not charity. The cloud contract economics are more favourable to Oracle over a multi-year term.

Third, many Oracle ULA (Unlimited Licence Agreement) periods that were signed in 2018-2021 are now in their certification phase. ULA certification is one of the most consequential Oracle licence events a company faces — and Oracle is extremely motivated to certify usage at the highest possible level before the ULA term ends.

What Oracle LMS Is Specifically Looking For

Oracle's compliance reviews are rarely random. LMS typically already has intelligence on your estate before they contact you. This intelligence comes from several sources: Oracle database call-home telemetry, usage patterns from Oracle support renewal data, third-party data brokers who track enterprise software installations, and increasingly from scanning public cloud environments like AWS and Azure where Oracle software is deployed on infrastructure that Oracle's licence terms specifically restrict.

The most common findings in a 2026 Oracle LMS review fall into five categories:

1. Oracle Database Processor Licensing Shortfalls

Oracle's Processor metric requires that you licence every physical core on a server running Oracle software, using Oracle's Core Factor Table. Virtualisation rules are complex — Oracle does not accept most hypervisors as partitioning technology, meaning that if Oracle Database is installed on a physical host running VMware vSphere, Oracle typically requires you to licence all cores on the physical host, not just the virtual cores assigned to the Oracle VM.

This is the single largest source of compliance exposure for most enterprises. A server with 64 physical cores, running Oracle Database on a single 4-core VM, can generate a licence obligation for 32 processor licences (64 cores × 0.5 Core Factor for Intel) — worth $1.5-3M in list price, even before support fees.

2. Named User Plus (NUP) Metric Violations

Where companies use NUP licences rather than Processor licences, Oracle checks whether the minimum users-per-processor minimums are met, whether every user who accesses Oracle (directly or through application tiers) has a NUP licence, and whether application deployments that feed data from Oracle databases are themselves licenced. Many middleware integrations and BI tools that query Oracle databases require NUP licences for all users of those upstream applications.

3. Oracle Java SE Employee Metric Violations

Since January 2023, Oracle Java SE subscriptions are priced on total employee headcount, not on the number of Oracle JDK installations. This means a company with 10,000 employees running Oracle JDK on even 50 machines owes Oracle Java SE subscriptions for 10,000 employees — at $15/employee/month. That is $1.8M per year, regardless of actual deployment. Many enterprises are unaware they are still using Oracle JDK (it is frequently embedded in third-party applications) and have not formally terminated their Oracle Java SE agreements.

4. Options and Packs Not Licenced

Oracle Database includes dozens of optional features — Partitioning, Advanced Compression, Real Application Clusters, Diagnostics Pack, Tuning Pack, and many others — that require separate licence purchases. Oracle's Automatic Workload Repository (AWR) and Active Session History (ASH) data are accessed via the Diagnostics Pack, and simply having Oracle Enterprise Manager deployed on a database often constitutes use of these packs. LMS reviews frequently find enterprises using 5-10 unlicenced options across their Oracle Database estate.

5. Deployment in Non-Authorised Cloud Environments

Oracle's BYOL (Bring Your Own Licence) terms for AWS, Azure, and Google Cloud impose specific infrastructure requirements that differ from on-premise deployments. On AWS, for example, Oracle Database BYOL is only permissible on Dedicated Hosts — bare-metal instances where you have full control of the physical hardware. Deploying Oracle on standard EC2 instances requires full Oracle Cloud licences, not BYOL. Many enterprises that migrated to AWS without specialist guidance are running Oracle in technically unlicenced configurations.

The LMS Scripts: What They Run and What They Collect

Oracle provides two primary script packages for LMS reviews: the Collection Manager and the Database Usage Tracking (DUT) scripts. Understanding what each collects — and what it does not — is essential to preparing your response.

Database Usage Tracking (DUT) Scripts

The DUT scripts run directly against Oracle Database instances and collect: the Oracle version and edition, all database options that have been used (including historical usage via the DBA_FEATURE_USAGE_STATISTICS view), the number of physical CPUs and cores on the host, the number of named users, and network connectivity data showing which applications connect to Oracle. Critically, DBA_FEATURE_USAGE_STATISTICS retains a record of every feature that has ever been enabled on a database, even if the feature is no longer in active use. A database administrator who enabled Advanced Compression for a test in 2019 may have generated a compliance obligation that persists in the data Oracle collects in 2026.

Collection Manager Scripts

The Collection Manager is a broader infrastructure scanner that Oracle requests you run on all servers in your environment — not just Oracle Database servers. It scans for Oracle software installations of any kind, identifies Java versions and distributions, catalogues Oracle middleware deployments (WebLogic, Fusion Middleware, SOA Suite), and documents virtualisation configurations. For enterprises with complex estates, Collection Manager output can run to hundreds of thousands of rows of data.

Your Rights During an Oracle License Review

Oracle's licence agreements include an audit clause that grants Oracle the right to conduct compliance reviews. However, this right is more limited than Oracle's standard outreach letters imply. Understanding the scope of Oracle's contractual audit rights — versus what Oracle asks for as a matter of practice — is fundamental to an effective defence.

Your contractual rights typically include: the right to a reasonable notice period before a review (Oracle cannot demand same-week access), the right to have your legal counsel present throughout the process, the right to negotiate the methodology used to count licences (Oracle's counting methodology is not always the only defensible interpretation), and the right to dispute findings before any obligation is acknowledged in writing.

What Oracle does not have is the right to demand access to systems outside the scope of what your contract covers, the right to share raw collection data with third parties without your consent, or the right to compel specific remediation timelines before findings are formally disputed.

If you have received an LMS letter, your first step should be to acknowledge receipt with a neutral letter that requests additional time to engage appropriate expertise — not to immediately agree to Oracle's proposed timeline or script scope. Most Oracle LMS timelines are negotiable by 30-60 days without penalty.

How to Prepare: 8 Steps Before LMS Arrives

Whether you have already received an LMS letter or you are conducting proactive risk management, these eight steps reduce your compliance exposure and improve your negotiating position significantly.

Step 1: Conduct an Internal Oracle Software Discovery

Before Oracle's scripts run, you need to know what Oracle software you have deployed, where it is, and on what infrastructure. This requires both a technical discovery (using your own tooling, not Oracle's) and a review of your Oracle licence agreements to understand exactly what metrics and use cases your licences cover. Many enterprises discover Oracle installations they had forgotten about — particularly Oracle WebLogic, Oracle Forms, and legacy database instances on servers that were supposed to be decommissioned.

Step 2: Map Your Virtualisation Configurations

Oracle's virtualisation policies are strict and frequently misunderstood. Document every server where Oracle software is deployed, the virtualisation platform in use, and whether that platform qualifies for hard partitioning under Oracle's policies. Oracle recognises only a short list of technologies as hard partitioning: Oracle VM Server, Oracle Solaris Zones (non-global), and IBM LPAR/VIOS (when configured to Oracle's standards). VMware, Hyper-V, and other popular hypervisors are explicitly classified by Oracle as soft partitioning — meaning Oracle requires full host licencing.

Step 3: Audit Oracle Java SE Deployments

Identify every Java runtime in your environment and determine its distribution. Oracle JDK 8 update 202 and earlier (released before January 2019) is free to use commercially under the older BCL licence. Oracle JDK 8 update 211 and later, and all Oracle JDK 11+ versions, require a Java SE subscription under the new commercial terms. Many enterprises are running Oracle JDK versions that trigger subscription requirements without realising it, particularly in application servers, development tools, and packaged applications from third-party ISVs.

Step 4: Review Oracle Database Feature Usage Statistics

Connect to each Oracle Database and query DBA_FEATURE_USAGE_STATISTICS with a focus on features that require additional licences. Pay particular attention to: Partitioning, Advanced Compression, Label Security, Database Vault, Multitenant, Real Application Clusters, Diagnostics Pack, Tuning Pack, and Data Masking. Where features show historical use but are no longer active, document the decommissioning date and prepare evidence that active use has ceased.

Step 5: Review Your Oracle Licence Agreements in Detail

Read your Oracle Customer Licence Agreement (OCLA) and each Software Licence and Services Agreement carefully. Pay attention to the specific metric definitions, the definition of Authorised Use, and any custom terms that were negotiated at signature. Oracle's standard audit clause and the scope of what it covers are defined in these agreements — and sometimes enterprises have more favourable terms than Oracle's standard language would imply, particularly if previous negotiations introduced specific definitions or limitations.

Step 6: Identify and Document Decommissioned Systems

Oracle's scripts will pick up Oracle software on any server they can reach — including servers that are technically active in your infrastructure but have not been in business use for years. Prepare documentation showing when specific systems were taken out of production use. While Oracle will include these in its initial count, having evidence of decommissioning is valuable in the negotiation phase.

Step 7: Engage Independent Oracle Licensing Expertise

This is the step most enterprises delay — and the delay is costly. Engaging an independent software audit defence adviser before Oracle's scripts run gives you the ability to prepare your position before Oracle sees the data. An adviser who has been through hundreds of Oracle LMS reviews knows exactly which counting methodologies Oracle will apply, which are negotiable, and which findings can be challenged on contractual or technical grounds.

Step 8: Prepare a Parallel Compliance Position

Before Oracle presents its findings, develop your own independent compliance position — your count of deployed licences versus your entitlements, using methodologies you are prepared to defend. This parallel position is your negotiating baseline. When Oracle presents a $6M finding and your internal analysis shows $2.5M, you have a defensible counter-position rather than simply accepting or disputing Oracle's number without alternative evidence.

Negotiating the Findings: From First Draft to Settlement

Once Oracle LMS has run its scripts and processed the data, they will schedule a findings presentation. This presentation is the beginning of the negotiation, not the end. Oracle's initial findings presentation includes a compliance gap — typically denominated in licence units and then converted to a list price obligation — that they expect you to acknowledge and remediate.

Several negotiation strategies consistently reduce the final settlement. First, methodological challenges: Oracle's licence counting methodology, particularly around virtualisation and processor cores, is not the only defensible interpretation of the licence agreement language. Where your contract uses terms like "processor" without a specific definition, there is legitimate room to challenge whether Oracle's Core Factor Table counting methodology was contractually specified or merely Oracle's preferred approach.

Second, technical corrections: Oracle's collection scripts, particularly Collection Manager, frequently produce inaccurate data. Servers counted multiple times, instances identified as Oracle Database that are actually other products, Java installations that are runtime-only and covered under third-party application licences — all of these are legitimate corrections that reduce the raw compliance gap before any commercial negotiation begins.

Third, commercial settlement options: Even after technical corrections, there is often a remaining compliance gap that Oracle will expect to remediate. How you remediate this gap matters enormously. Paying list-price back-support fees is the worst outcome. Converting to cloud credits, entering a new EA at below-list pricing, receiving future licence entitlements in lieu of cash, or negotiating a phased remediation plan that coincides with your planned cloud migration are all options that reduce the effective cash cost.

Finally, time is a factor. Oracle's fiscal year-end pressure on LMS teams means that settlements reached before 31 May frequently include more favourable commercial terms than those concluded later in the calendar year.

The 5 Most Expensive Mistakes Enterprises Make

Mistake 1: Responding to LMS Without Independent Expertise

Engaging Oracle's Account Executive and Oracle's LMS team directly — without an independent adviser — gives Oracle complete information asymmetry. Oracle's team does hundreds of these reviews per year. Your team may have done one, or none. The knowledge gap alone costs most enterprises 20-30% of the final settlement amount.

Mistake 2: Running Scripts Without Scope Negotiation

Agreeing to run Oracle's Collection Manager scripts across your full global infrastructure before agreeing on scope means you may expose Oracle to compliance gaps in geographies or business units that were not targeted in Oracle's original outreach. Every server that Oracle's scripts touch is a server that may generate a finding. Scope negotiation before script execution is essential.

Mistake 3: Acknowledging the Initial Finding in Writing

Oracle's findings presentation often includes a form, a letter, or an email follow-up asking you to "acknowledge" the compliance position. Do not acknowledge any finding in writing before your legal and licensing advisers have reviewed it. Written acknowledgement of a compliance position is difficult to walk back in subsequent negotiations.

Mistake 4: Conflating Oracle's Preferred Counting with the Contractual Obligation

Oracle's counting methodologies — particularly around virtualisation, Java SE employee count, and NUP minimum calculations — represent Oracle's preferred interpretation of the licence agreement. They are not automatically correct, and they are frequently negotiable. Treating Oracle's methodology as definitive and building your internal analysis around it means you start from Oracle's position rather than a neutral one.

Mistake 5: Settling Before the Support Renewal

Oracle's LMS reviews are frequently timed to coincide with your Oracle support renewal. If you settle the compliance finding and sign the remediation agreement before your support renewal, Oracle retains full pricing leverage on the support contract. In many cases, linking the settlement and the support renewal negotiation — using the settlement as leverage to reduce support costs — produces a better overall commercial outcome.

How a Gainshare Adviser Changes the Outcome

The standard approach to Oracle LMS defence involves retaining either general legal counsel or a consulting firm on an hourly or fixed-fee basis. The problem with both models is that the adviser is paid regardless of the outcome — which creates no direct alignment between the adviser's incentives and your savings.

Our Oracle negotiation service operates exclusively on a gainshare basis: we receive 25% of the verified savings we generate compared to Oracle's initial finding (or compared to what you would otherwise have paid in an unchallenged settlement). If we cannot reduce the finding, we earn nothing. This model means we are selective about which engagements we take — and it means our advisers are motivated to fight for the maximum possible reduction, not to bill hours.

In a typical Oracle LMS engagement, an enterprise with an initial Oracle finding of $5M would pay our team $250,000-500,000 as a success fee if we reduce the finding to $2-3M — while retaining $1.5-2.75M of cash savings that would otherwise have been paid to Oracle. Compare this to the alternative: accepting the $5M finding, or paying a fixed-fee adviser $200,000 to reduce it by a modest amount with no accountability to the outcome.

The economics of gainshare advisers consistently outperform fixed-fee alternatives for clients, because the adviser only earns a fee when the client saves money — and the adviser's fee is always smaller than the savings generated.