How to Use This Assessment

This tool is structured around the same 20 risk vectors Redress Compliance reviews in every Oracle estate engagement. Each item includes an expert note drawn from real audit findings, ULA certifications, and negotiation outcomes. Work through each point methodically. Any item where your answer is "unsure" or "no" represents a live financial or compliance exposure.

For the ADNOC engagement, the estate covered Oracle Database Enterprise Edition, Oracle E-Business Suite, Oracle WebLogic Server, Oracle Java SE, and a portfolio of on-premises middleware running across a VMware-based data centre with over 2,400 physical cores. The majority of the $6M recovery came from just four of the 20 items below.

"Oracle's licensing rules are written to create ambiguity. The ambiguity always resolves in Oracle's favour — unless you bring independent expertise to the table before Oracle's auditors do."
— Morten Andersen, Redress Compliance

Section 1: Database Licensing Fundamentals

Oracle Database Enterprise Edition remains the highest-risk product in most enterprise estates. Processor licensing, core factors, and option/pack activation together account for the majority of Oracle audit findings worldwide. Oil & gas organisations typically run Oracle DB on large x86 clusters — making every calculation here high-stakes.

01 Processor Licence Count vs. Deployed Physical Cores HIGH RISK

Confirm that your Oracle Database processor licence count equals total physical cores multiplied by the applicable core factor from Oracle's Processor Core Factor Table. Intel Xeon and AMD EPYC processors typically carry a 0.5 factor; IBM POWER processors carry 1.0. Verify the exact processor model in each server, apply the correct factor, and round up to the nearest whole number. Compare the result to your current entitlement count.

Expert NoteAt ADNOC, four server clusters were running Oracle DB on hardware that had been upgraded from Intel Xeon E5 (0.5 factor) to Intel Xeon Gold (also 0.5 factor), but the entitlement tracker had not been updated following a hardware refresh, leaving a 32-processor gap between what was deployed and what was licensed. This single item accounted for $1.4M of the engagement's savings — not because more licences were needed, but because the entitlement inventory was inaccurate and overstated, creating unnecessary annual support spend.
02 Database Options & Packs — Active Features Audit HIGH RISK

Oracle automatically installs all options and packs with Database Enterprise Edition. Any feature used — even once, even inadvertently by a DBA running a diagnostic query — is deemed licensed and creates a perpetual obligation. Run Oracle's Feature Usage Statistics script (DBA_FEATURE_USAGE_STATISTICS) across all instances. Map every feature with CURRENTLY_USED = TRUE or DETECTED_USAGES > 0 to a licence entitlement. Common unlicensed features found in energy sector estates include Diagnostic Pack, Tuning Pack, Advanced Compression, Active Data Guard, and Oracle Partitioning.

Expert NoteIn the ADNOC engagement, Diagnostic Pack and Tuning Pack were active across 11 production database instances. Neither was licensed. These two packs alone triggered a $2.1M finding in Oracle's own internal assessment — which Redress Compliance reduced to zero by demonstrating that the usage was accidental, immediately ceased, and that Oracle's own documentation had not made the activation risk adequately clear at the point of installation.
03 Named User Plus Minimums — Per-Processor Calculation MEDIUM RISK

If you licence Oracle Database Enterprise Edition on a Named User Plus (NUP) metric, Oracle requires a minimum of 25 NUPs per processor licence (based on the core factor calculation). Verify that your NUP count meets this floor across every licensed server. This check is frequently overlooked when processor counts change following hardware refreshes or when servers are added to clusters without a corresponding licence review.

Expert NoteNUP minimum violations are almost always inadvertent and result from hardware changes that were not routed through a licence governance process. In oil & gas environments where IT and OT (operational technology) infrastructure merges, it is common to find Oracle DB instances serving SCADA or historian systems on hardware that was added by operational engineering teams with no awareness of the NUP minimum rule.
04 Disaster Recovery & High Availability Licensing HIGH RISK

Oracle's licensing policy requires DR and standby servers running Oracle software to be licensed, unless covered by a specific licensing exception. The Active Data Guard option requires a separate licence. Passive failover standby databases (no active queries, no reporting) may qualify for Oracle's 10-day failover policy — but only if specific conditions are met and documented. Inventory every DR instance and validate which policy applies.

Expert NoteThe ADNOC estate included two active-passive Data Guard configurations and one active-active RAC deployment used for high availability. The active-active RAC configuration required Real Application Clusters licences on all nodes — a fact not reflected in the entitlement register. This is the most commonly missed item in energy sector Oracle audits, where DR architecture decisions are made by infrastructure teams without licensing input.

Section 2: Virtualisation & Infrastructure Risk

Oracle's virtualisation policy is the single most contentious area in Oracle licensing. Oracle does not recognise VMware, Microsoft Hyper-V, or most other hypervisors as "hard partitioning" — meaning that if Oracle software can run on any host in a cluster, Oracle's position is that all hosts must be fully licensed. This creates enormous leverage for Oracle auditors in VMware-heavy data centres.

05 VMware Cluster-Wide Licensing Exposure HIGH RISK

If Oracle DB VMs are hosted on a VMware vSphere cluster, Oracle's position requires all physical hosts in that cluster to be fully licensed — not just the hosts the Oracle VM currently runs on. Identify every VMware cluster hosting Oracle workloads, count the total physical cores across all hosts in each cluster, apply the core factor, and compare against current entitlements. If you have not done this calculation, assume you are under-licensed.

Expert NoteThis was the largest single exposure area in the ADNOC engagement. Oracle DBs were running in VMs spread across a 14-host VMware cluster. The client had licensed only the hosts the Oracle VMs were pinned to (4 hosts). Oracle's position would have required all 14 hosts to be licensed — a difference of 10 hosts × 36 cores × 0.5 = 180 additional processor licences at approximately $47,500 list price each. Redress Compliance resolved this by renegotiating to an alternative infrastructure topology, eliminating the cluster-wide exposure entirely without purchasing additional licences.
06 VM Mobility, Snapshots, and Live Migration Policies HIGH RISK

Any Oracle VM that has the ability to migrate — via vMotion, DRS, or automated load-balancing — to an unlicensed host creates an immediate compliance exposure. Even historical snapshots of Oracle VMs can be counted by Oracle's audit scripts. Disable automated DRS migration for Oracle VMs, document VM affinity rules, and audit any snapshot history for Oracle instances.

Expert NoteOracle's LMS (License Management Services) audit scripts capture VM migration logs. A single unplanned vMotion event — triggered by a failing host during routine maintenance — can be used by Oracle to assert licensing obligations across the destination host and its cluster. This is not theoretical: Redress Compliance has seen Oracle cite a three-minute vMotion event as justification for $4M in additional licence demand in a financial services audit.
07 Oracle VM & Hard Partitioning Alternatives MEDIUM RISK

Oracle recognises only a narrow set of technologies as "hard partitioning" — including Oracle VM Server, Oracle Solaris Zones (non-capped excluded), and IBM LPAR with dedicated CPUs. If your infrastructure roadmap includes a move away from VMware (particularly given Broadcom's 2024 pricing changes), evaluate whether migrating Oracle workloads to Oracle VM or bare metal would eliminate the cluster-wide licensing risk and reduce long-term licence exposure.

Expert NoteThe Broadcom acquisition of VMware in 2023–2024 triggered many enterprises to reconsider their hypervisor strategy. For Oracle workloads specifically, this creates an opportunity: migrating to bare metal or Oracle Cloud Infrastructure (OCI) can eliminate the soft-partitioning ambiguity entirely. At ADNOC, a phased workload migration to dedicated bare-metal servers for the highest-risk Oracle DB instances was part of the remediation plan.
Get the full Oracle Licensing Audit Defence Kit
Includes LMS script decoder, processor licence calculator, and ULA certification guide. Gated download.
Download Free

Section 3: Java SE Licensing

Oracle's January 2023 switch to an employee-based Java SE Universal Subscription model turned a previously manageable cost into a potentially enormous liability for large enterprises. An oil & gas major with 60,000 employees can face an annual Oracle Java bill exceeding $3M — even if only a fraction of employees use Java-based applications.

08 Oracle JDK Installation Inventory — All Environments HIGH RISK

Run a full discovery of Oracle JDK installations across production, development, test, staging, and containerised environments. The Oracle Java Universal Subscription is calculated on total employee headcount — not on the number of JDK installs — but discovery is still necessary to understand which systems are using Oracle-branded JDK versus an OpenJDK build. Any Oracle JDK version receiving updates after September 2024 (when the NFTC free period ended) requires a paid subscription.

Expert NoteIn large oil & gas operations, Oracle JDK is frequently embedded in industrial control system (ICS) vendor software, historian platforms, and GIS applications that were deployed without IT's knowledge. These embedded deployments are just as licensable as any directly installed JDK. Redress Compliance routinely finds 30–60% more Oracle JDK instances than the client's IT asset management tool reports — because ITAM tools do not scan OT network segments.
09 OpenJDK Migration Readiness MEDIUM RISK

Assess which Oracle JDK deployments can be replaced with a supported OpenJDK distribution (Adoptium, Amazon Corretto, Microsoft Build of OpenJDK, Azul Zulu). For applications not requiring Oracle-specific patches, OpenJDK migration eliminates the Java subscription cost entirely. Prioritise migration of JDK 8, 11, and 17 instances — the most common versions still running Oracle-branded binaries in enterprise estates.

Expert NoteOpenJDK migration is the single most impactful action most organisations can take to reduce their Oracle cost exposure in 2026. It is technically straightforward for standalone applications but requires careful testing for Oracle Fusion Middleware, Oracle Forms, and Oracle E-Business Suite deployments, where Oracle-bundled JDK versions may be required under support terms.
10 Java in Containers & CI/CD Pipelines MEDIUM RISK

Docker images and Kubernetes workloads that embed Oracle JDK are licensable under the Universal Subscription model. Audit your container registry for base images containing Oracle Java. CI/CD pipelines that pull Oracle JDK as a build tool are also in scope. This is a rapidly growing exposure area as energy sector organisations accelerate DevOps adoption for operational analytics and AI workloads.

Expert NoteOracle's audit methodology for containerised Java is still evolving, but the contractual position is clear: if your organisation's employees use Oracle JDK in any form, you need a Universal Subscription covering all employees. Container counts do not cap the obligation — only employee headcount determines the cost. The implication is that even a single container image using Oracle JDK creates a full enterprise-wide subscription requirement.

Section 4: ULA & Agreement Management

Oracle Unlimited License Agreements (ULAs) are common in large energy sector organisations due to the scale of Oracle deployments. A ULA provides unlimited use of specified products for a fixed term (typically three years), after which the organisation must either renew or "certify" — locking in a specific licence count. Certification is where most value is lost or recovered.

11 ULA Coverage Scope — Products & Metrics Confirmed HIGH RISK

Obtain every Oracle ordering document associated with your current or most recent ULA. Verify exactly which products are included, on which metric (processor or NUP), and whether any geographic or entity restrictions apply. ULAs frequently exclude options, packs, cloud services, and recently acquired Oracle products — usage of excluded items creates a compliance liability even during the ULA term.

Expert NoteIn the ADNOC engagement, the client's ULA covered Oracle Database Enterprise Edition and Oracle WebLogic Suite. It did not cover Oracle Analytics Server, which had been deployed 18 months into the ULA term by a BI team with no knowledge of the licence restriction. Redress Compliance renegotiated this item retroactively as part of the ULA renewal discussion, avoiding a $780K back-licence demand.
12 ULA Certification Readiness — Non-Production Environments HIGH RISK

If your ULA is approaching its end date (within 18 months), begin your certification count immediately. Include all environments — production, development, test, QA, and disaster recovery. Under-counting during certification leaves you under-licensed post-ULA; over-counting leaves you paying unnecessary annual support on phantom licences. Both errors are costly. The certification count you agree with Oracle is permanent — it cannot be revised downward after submission.

Expert NoteThe most common ULA certification mistake is treating non-production environments as exempt. Oracle's standard position is that all instances running ULA-covered products must be counted, regardless of purpose. Redress Compliance recommends starting the certification process 12 months before ULA expiry to allow time for environment rationalisation — decommissioning unused instances before they are counted and locked into the perpetual licence cost base.
13 ULA Renewal vs. Certification Decision Analysis MEDIUM RISK

At ULA expiry, you face a binary choice: certify (exit the ULA with a fixed perpetual count) or renew (enter another ULA term). Oracle's sales team will almost always recommend renewal — because it preserves Oracle's revenue and avoids locking in a low licence count. Run a quantitative analysis comparing the net present value of certifying at current deployment levels versus the cost of a renewal term, factoring in cloud migration plans and anticipated workload changes.

Expert NoteFor organisations with stable or declining Oracle footprints — which increasingly describes large energy companies migrating to cloud or SaaS alternatives — certification is almost always the better financial decision. Certifying locks in a perpetual licence count that costs nothing additional to maintain (other than annual support), while renewal commits the organisation to another three years of ULA fees regardless of actual usage growth.

Section 5: Support, Cloud & Middleware

Oracle's annual support model — typically 22% of the net licence fee — represents the largest recurring Oracle cost for most enterprises. Third-party support alternatives, cloud migration paths, and middleware rationalisation together offer the most accessible cost reduction levers available without renegotiating the core product licence structure.

14 Annual Support Cost Review — 22% Model Challenge MEDIUM RISK

Oracle standard support is priced at 22% of net licence value annually, and Oracle's support contracts typically include an annual uplift of 4–8%. Review which Oracle products you are actively using Oracle support for — including submitting SRs, downloading patches, or accessing My Oracle Support (MOS). Products that are stable, at end-of-development, or earmarked for decommission within three years are candidates for third-party support or support termination.

Expert NoteThe ADNOC estate included Oracle E-Business Suite R12 at a support cost of approximately $1.1M per year. With the client having no plans to upgrade, and the system being in maintenance mode, a move to a third-party support provider (offering equivalent cover at ~50% of Oracle's price) represented an annual saving of $550K. This saving alone exceeded the cost of the entire Redress Compliance engagement.
15 Third-Party Support Viability Assessment LOW RISK

Evaluate whether Oracle EBS, Oracle Database, or Oracle Middleware products in your estate qualify for third-party support through providers such as Rimini Street, Spinnaker Support, or US Cloud. Third-party support is legally permitted, typically saves 50% vs Oracle's support fees, and does not affect your perpetual licence entitlements. The key constraint is that third-party support providers cannot deliver Oracle patches — so assess whether your security patching strategy can operate without access to new Oracle CPUs.

Expert NoteThird-party support is appropriate for stable, non-upgrading Oracle systems. It is not appropriate for Oracle products still in active development cycles, systems requiring frequent Oracle patches for regulatory compliance, or products where Oracle's support is a contractual requirement (e.g., within a ULA or cloud subscription). Evaluate each product independently — a hybrid approach, with Oracle support retained only where necessary, is often the optimal outcome.
16 Oracle Middleware — WebLogic, Forms, Reports Rationalisation MEDIUM RISK

Oracle WebLogic Server, Oracle Forms, and Oracle Reports are frequently over-licensed in large enterprise estates. Verify that WebLogic Server processor licence counts match deployed cores, and that you are not paying for WebLogic Suite (which includes several components you may not be using) where the standalone WebLogic Server licence would suffice. Oracle Forms and Reports deployments are often candidates for decommission in favour of modern web application frameworks.

Expert NoteIn oil & gas environments, Oracle Forms applications connected to EBS are sometimes still in production that were deployed in the early 2000s. The Forms and Reports licence cost, combined with WebLogic support fees, can exceed $200K per year for a legacy deployment that serves a few hundred users. A migration to Oracle APEX (free with Oracle Database) or a modern SaaS equivalent typically pays back in under 24 months.
17 Cloud Migration Licensing — BYOL vs. PAYG Analysis MEDIUM RISK

If Oracle workloads are being migrated to AWS, Azure, Google Cloud, or Oracle Cloud Infrastructure (OCI), validate the licensing model before migration. BYOL (Bring Your Own Licence) on third-party clouds requires the same processor licence count as on-premises, based on the cloud provider's vCPU-to-core mapping. On OCI specifically, Oracle offers more favourable BYOL terms. Incorrect cloud licensing assumptions can create a larger compliance exposure than the on-premises environment being replaced.

Expert NoteA common trap: enterprises migrate Oracle DB to AWS EC2, assume their existing processor licences cover the deployment, and find during an audit that their vCPU count maps to more processor licences than their on-premises entitlement. On AWS, each physical core underlying an instance is licensable — and with hyperthreading, this means two vCPUs = one physical core = 0.5 processor licences (for Intel). Always confirm the physical core count from your cloud provider before migration.
18 Indirect Access / Technology Risk — Third-Party Application Connectivity HIGH RISK

Oracle's indirect access policy holds that any data accessed in an Oracle database by a non-Oracle application is potentially licensable — based on the total number of users or devices that could access that data. This applies to ERP integrations, data warehouse pipelines, API gateways, and industry-specific systems (such as SCADA historians, GIS platforms, or supply chain tools) that read from or write to Oracle databases. Identify all third-party applications that touch Oracle data and assess their licence position under Oracle's current indirect access policy.

Expert NoteIndirect access is Oracle's most aggressive audit lever in complex enterprise environments. In oil & gas, where ERP, GIS, historian, scheduling, and maintenance management systems are all frequently integrated, the indirect access exposure can exceed the direct Oracle licence cost. Redress Compliance has seen Oracle demand $8–15M in additional licences based on indirect access claims in integrated energy sector estates. The key defence is maintaining clear contract language restricting Oracle's indirect access assertions — ideally negotiated upfront rather than at audit.
19 Oracle Audit Readiness — LMS Script Review HIGH RISK

Oracle's License Management Services (LMS) team uses a suite of scripts to scan Oracle environments during audits. Obtain and run Oracle's published Collection Scripts against your estate before any audit is triggered. Review the output for unexpected findings, feature activations, or deployment counts that differ from your licence register. Oracle will use the script output as the primary basis for any compliance gap assessment — you should know what it says before they do.

Expert NoteOracle's LMS scripts capture far more than just product installations — they record feature usage history, diagnostic pack access, VM configuration details, and user counts. Running these scripts in a controlled environment before an audit allows you to address findings on your timeline rather than Oracle's. Redress Compliance has helped clients reduce initial Oracle audit demands by 60–80% simply by resolving preventable issues identified during pre-audit script review.
20 Renewal Strategy — Upcoming Support & Agreement Dates MEDIUM RISK

Map all upcoming Oracle support renewal dates, ULA expiry dates, and cloud subscription renewal windows on a forward-looking calendar. Oracle's sales team is most receptive to pricing and scope negotiations in the 90–180 days before renewal. Any negotiation attempted after a renewal order is placed has significantly less leverage. Ensure that renewal conversations are initiated with independent advisory support — Oracle's sales team is expert at structuring deals that appear attractive while locking in long-term cost commitments that disadvantage the buyer.

Expert NoteAt ADNOC, three Oracle support contracts had been silently auto-renewing at list price for five years. No negotiation had taken place. By consolidating these into a single renewal discussion and leveraging the overall scope of the Oracle relationship — database, middleware, EBS, and Java — Redress Compliance negotiated a 34% reduction in blended support rates, delivering $620K in annual savings going forward. The leverage available at renewal is almost always greater than clients expect, provided they are prepared and independent.

What the ADNOC Engagement Proved

The $6M savings achieved in this engagement did not come from a single dramatic finding. They came from the cumulative effect of working through assessments like this one, methodically, with the depth of knowledge that only comes from having been on Oracle's side of the table. The four highest-value items — database options exposure, VMware cluster-wide licensing, ULA scope violation, and support renegotiation — each required a combination of technical expertise, contract interpretation, and negotiation skill that is difficult to replicate without specialist support.

The 20 points in this checklist represent the minimum viable assessment for any large Oracle estate. For ADNOC-scale environments, the full Redress Compliance methodology extends to over 60 assessment points covering specific technology configurations, contract language analysis, and benchmarking against industry peer data. If any item on this checklist has surfaced a question you cannot answer with confidence, that gap is worth addressing before Oracle addresses it for you.

Ready to run this assessment on your Oracle estate?
Redress Compliance offers a complimentary 45-minute scoping call to assess your highest-priority risk areas. No obligation.
Book a Call