Case Study: Oracle Licensing Assessment — Circles Telco in Singapore — $4M Saved

Circles' Oracle licensing situation was typical of fast-growing technology companies in the APAC region: the IT infrastructure had scaled rapidly to support subscriber growth, while licensing governance hadn't kept pace. Three distinct compliance risks converged simultaneously, creating a complex and high-stakes situation.

1. Oracle Database on VMware — The "Soft Partitioning" Dispute:

Circles ran Oracle Database Enterprise Edition on a VMware vSphere infrastructure — a common architecture for telecom companies that need elastic compute capacity. The Oracle estate included approximately 12 physical servers in a VMware cluster, with Oracle Database instances deployed on specific virtual machines.

Oracle's LMS team applied their standard soft partitioning policy: because VMware is not on Oracle's "hard partitioning" approved list, Oracle claimed that all physical processors in the entire VMware cluster — not just those hosting Oracle VMs — required licensing. This meant Oracle was asserting that Circles needed to licence all 12 servers (approximately 192 processor cores, equating to 96 Oracle Processor licences at the standard 0.5 core factor) rather than the 3 servers actually running Oracle workloads.

At list price, Oracle Database Enterprise Edition Processor licences cost approximately $47,500 each. The difference between licensing 3 servers (~24 Processor licences = $1.14M) and licensing 12 servers (~96 Processor licences = $4.56M) was $3.42M — though Oracle LMS presented a "gap" figure of approximately $2.4M after accounting for Circles' existing entitlements.

This is one of the most common and financially significant Oracle audit disputes. Oracle's policy document states that virtualised environments using "soft partitioning" technologies (VMware, Hyper-V, KVM, Solaris Zones, etc.) require licensing of the entire physical host. However, Oracle's own contractual terms and the legal enforceability of their partitioning policy are more nuanced than Oracle LMS typically presents.

2. WebLogic Middleware — Overcounted Deployments:

Oracle WebLogic Server was deployed as the middleware layer supporting Circles' customer-facing portals and internal service orchestration. Oracle LMS identified WebLogic instances across multiple servers and claimed that additional Processor licences were required — approximately $800K in additional licensing.

The core dispute: Oracle's scan tools detected WebLogic components installed on servers where they were not actively running — a common occurrence when standard OS images include middleware binaries that are never configured or used. Oracle counted these as "deployments" requiring licences, even though the WebLogic software was never started or invoked.

3. Java SE — The New Licensing Minefield:

Oracle's revised Java SE licensing model — shifting from free distribution to a commercial subscription based on employee headcount — had significant implications for Circles. Oracle's LMS inquiry identified Java SE installations across hundreds of endpoints and servers, and Oracle's sales team proposed an enterprise-wide Java subscription covering all employees at approximately $15 per employee per month.

For Circles, with thousands of employees, this translated to approximately $800K in annual Java licensing costs — for software that had previously been free. Oracle framed this as a mandatory compliance requirement, implying that any commercial use of Java SE required the enterprise subscription.

Circles engaged Redress Compliance to conduct a comprehensive, independent Oracle licensing assessment — a systematic review of every Oracle product deployment mapped against contractual entitlements. This assessment formed the factual foundation for challenging Oracle's claims.

1. Oracle Database Assessment:

The team deployed independent data collection (not Oracle's LMS scripts) to map every Oracle Database instance across Circles' infrastructure. For each instance, they documented: the physical host, VMware cluster assignment, CPU/core configuration, Oracle Database edition and version, activated options and packs (via DBA_FEATURE_USAGE_STATISTICS), and the specific VMware configuration (vMotion scope, affinity rules, DRS groups).

The critical finding: Circles had implemented VMware DRS affinity rules that restricted Oracle VM workloads to a defined subset of 3 physical hosts within the larger 12-host cluster. While Oracle's partitioning policy document doesn't recognise VMware as "hard partitioning," the contractual question is whether the customer's actual deployment requires licensing beyond the hosts where Oracle runs. The advisory team prepared a detailed technical report demonstrating that Oracle Database workloads were physically constrained to 3 hosts and could not — under the configured VMware policies — migrate to the other 9 hosts.

Additionally, the team identified that several Oracle Database options detected by LMS (Diagnostics Pack, Tuning Pack) had been automatically enabled during installation but never actively used. Oracle's licence model requires licensing for "use," and Oracle's own documentation acknowledges that certain features can be enabled by default without constituting licensable use if they are not accessed. The team generated DBA_FEATURE_USAGE_STATISTICS reports showing zero usage for these options over the past 12 months, building a defence against Oracle's claim that they required additional licences.

2. WebLogic Middleware Assessment:

The team conducted a process-level audit of every server where Oracle LMS had detected WebLogic. For each server, they verified whether WebLogic processes were actually running (not just installed), whether WebLogic was configured and serving active applications, and whether the server's function required WebLogic or whether the binaries were remnants of previous configurations or default installations.

The findings were striking: of the 14 servers where Oracle claimed WebLogic required licensing, only 6 had active WebLogic instances serving production or development workloads. The remaining 8 had WebLogic binaries present on disk but no running processes, no configured domains, and no application deployments. These were either leftover installations from prior projects or default middleware components included in OS provisioning templates.

For the 6 active servers, the team verified that Circles' existing WebLogic Processor entitlements covered the deployment. Oracle LMS had overcounted by including the dormant servers, inflating the gap by approximately $800K.

3. Java SE Assessment:

The Java assessment required a different approach — granular cataloguing of every Java installation across Circles' enterprise environment. The team used endpoint management tools to inventory Java versions, installation paths, and usage patterns across servers, desktops, and endpoint devices.

Key findings:

By categorising every installation, the team determined that only ~180 server instances genuinely required Oracle's commercial Java subscription. Rather than the enterprise-wide headcount-based subscription Oracle proposed (~$800K/year), Circles could licence Java on a targeted, server-specific basis at approximately $120K/year — an 85% reduction.

The largest single exposure — $2.4M — stemmed from Oracle's VMware soft partitioning assertion. Defending against this required both technical evidence and contractual analysis.

1. Oracle's Policy vs Contractual Reality:

Oracle's "Partitioning Policy" is a unilateral document published by Oracle — it is not part of the customer's licence agreement. Oracle's actual licensing contracts (the Oracle Master Agreement and associated ordering documents) typically define licensing requirements based on the "Processor" metric, which counts the cores of "the server where the Oracle programs are installed and/or running." The critical legal question is whether "the server" means the physical host running the Oracle VM or the entire VMware cluster.

Oracle's position is that VMware counts as "soft partitioning" and therefore the entire cluster must be licensed. However, this interpretation relies on the Partitioning Policy — an external document that may not be incorporated into the customer's specific contract. The advisory team reviewed Circles' Oracle Master Agreement and ordering documents and confirmed that the Partitioning Policy was not referenced or incorporated in any signed agreement. This meant Oracle's licensing obligation was defined by the contract language ("installed and/or running"), not by their unilateral policy document.

2. Technical Defence — DRS Affinity Rules:

Even applying Oracle's Partitioning Policy at face value, the team documented that Circles' VMware environment was configured with DRS (Distributed Resource Scheduler) affinity rules that physically restricted Oracle VMs to 3 designated hosts. The vMotion scope was limited such that Oracle VMs could only move between these 3 hosts — not across the broader 12-host cluster. This meant:

Under Oracle's own policy framework, only the hosts where Oracle is "installed and/or running" require licensing. With affinity rules preventing migration to other hosts, the licensing scope was limited to the 3 Oracle-designated hosts — exactly what Circles had licensed.

The team prepared a comprehensive technical report documenting the VMware configuration, including screenshots of DRS rules, vCenter configuration exports, and historical vMotion logs showing that no Oracle VM had ever migrated to a non-Oracle host. This report was submitted to Oracle LMS as part of the formal audit response.

3. Financial Impact of the Defence:

Circles' existing Oracle Database Processor entitlements (26 licences) actually exceeded the 24 required under the corrected scope — meaning not only was the $2.4M claim eliminated, but Circles had a small surplus of entitlements.

With the independent assessment complete, the engagement shifted to active audit defence — managing Oracle's LMS process, countering their claims with data, and deflecting the sales team's commercial pressure.

1. Managing the Oracle LMS Process:

Oracle's LMS audits follow a structured process: initial inquiry → data collection → analysis → preliminary findings → negotiation → resolution. The advisory team managed each stage on Circles' behalf, ensuring that: only contractually required data was provided (Oracle LMS often requests more data than the audit clause entitles them to), all data submissions were reviewed before delivery to Oracle to prevent inadvertent disclosure of information that could be misinterpreted, and every Oracle finding was met with a documented, fact-based response within agreed timelines.

A critical principle: never ignore an Oracle audit, but never accept their findings uncritically. Oracle LMS presents preliminary findings as authoritative assessments of licensing gaps. In reality, these findings are starting positions — calculated using Oracle's most aggressive interpretations — designed to create urgency and drive commercial outcomes.

2. Separating Audit from Sales:

One of Oracle's most effective tactics is conflating the audit and sales processes. Circles experienced this directly: while LMS was conducting the compliance review, Oracle's sales team simultaneously approached Circles' CIO with a proposal for a $6M+ Unlimited License Agreement (ULA), positioned as the "simple solution" to resolve all compliance concerns.

The advisory team helped Circles formally separate the two processes. Circles communicated to Oracle that the audit would be resolved through the LMS compliance channel based on facts, and any commercial discussions about new purchases would be conducted separately, on Circles' timeline, through procurement. This prevented Oracle from using audit fear as a sales lever — a tactic that frequently leads organisations to overspend by 3–10× their actual compliance exposure.

3. Formal Response and Claim Reduction:

The advisory team prepared a comprehensive response document addressing each Oracle LMS finding:

The formal response was submitted with over 40 pages of supporting documentation. Oracle LMS reviewed the evidence over a 6-week period and progressively withdrew their claims. The final resolution: zero compliance gap for Oracle Database and WebLogic, and a targeted Java subscription of $120K/year for genuinely required installations. The Oracle audit was formally closed.

4. Deflecting the ULA Proposal:

With the audit resolved, Oracle's sales team lost their primary leverage for the $6M ULA proposal. The advisory team helped Circles formally decline the ULA and instead negotiate a targeted Java subscription at competitive rates — achieving a 40% discount off Oracle's initial Java subscription pricing through benchmark data and competitive alternatives (Azul, Amazon Corretto, Eclipse Adoptium). The final Java subscription cost: $120K/year — versus the $800K Oracle initially demanded.

The engagement delivered comprehensive results across all three risk areas, eliminating $3.88M of the $4M exposure Oracle had identified — a 97% reduction in claimed compliance gaps.

Beyond Cost Avoidance — Strategic Benefits:

The engagement delivered benefits beyond the immediate $4M in cost avoidance. Circles gained confidence in its Oracle compliance position, backed by detailed documentation that can be produced if Oracle initiates future inquiries. The IT team now has a clear understanding of Oracle's licensing rules for databases, middleware, and Java — significantly reducing the risk of inadvertent non-compliance as the environment evolves.

Perhaps most importantly, Oracle's sales pressure subsided once accurate licensing data was presented. The IT team gained breathing room to plan infrastructure expansion on their own terms, without the constant threat of an unresolved audit distorting procurement decisions. Circles' CIO noted that the engagement fundamentally changed the power dynamic with Oracle — from a position of fear and uncertainty to one of informed confidence.

Client Testimonial — CIO, Circles: "Redress Compliance delivered exactly what we needed — an independent Oracle licensing review that saved us $4 million. Their expertise in Oracle audit defence and precise knowledge of Oracle's policies gave us confidence. We avoided a potentially devastating compliance bill and can now expand without fear of surprise Oracle costs. Working with Redress was like having Oracle insiders on our side, looking out for our interests."

Circles' experience highlights several transferable lessons applicable to any enterprise running Oracle on virtualised infrastructure.

1. Oracle's Partitioning Policy Is Not Necessarily Your Contract:

Oracle's Partitioning Policy is published on Oracle's website. It is not automatically part of your licence agreement. Your licensing obligations are defined by the signed contract — typically the Oracle Master Agreement (OMA) or Oracle License and Services Agreement (OLSA) and associated ordering documents. If the Partitioning Policy is not referenced or incorporated in your signed agreements, Oracle's claims based on it rest on weaker contractual ground. Always review your specific contract language before accepting Oracle's interpretation.

2. VMware DRS Affinity Rules Are Your Best Defence:

If you run Oracle on VMware, implementing and documenting DRS host affinity rules is the single most effective technical measure. By restricting Oracle VMs to designated hosts and preventing vMotion to non-Oracle hosts, you limit the licensing scope to those specific hosts. This defence works both under Oracle's Partitioning Policy (by demonstrating that Oracle is not "installed and/or running" on non-Oracle hosts) and under the contract's processor metric definition.

3. Oracle's Scan Tools Overcount — Always Verify Independently:

Oracle LMS uses automated tools (including the now-deprecated LMS Collection Tool and the newer Oracle LMS SaaS) that detect Oracle software binaries on disk. These tools do not distinguish between installed-and-running software and installed-but-dormant binaries. In Circles' case, 8 of 14 WebLogic "deployments" were dormant. This overcounting pattern is consistent across Oracle audits and routinely inflates compliance claims by 30–60%.

4. Separate the Audit from the Sales Process — Always:

Oracle routinely uses active audits as sales leverage, positioning commercial purchases (ULAs, cloud subscriptions) as "solutions" to compliance problems. This conflation serves Oracle's interests, not yours. Formally separate the two processes: resolve the audit through LMS based on facts, and conduct any commercial discussions through procurement on your own timeline. An organisation under audit pressure that buys a ULA typically overspends by 3–10× their actual compliance exposure.

5. Java Licensing Is Not All-or-Nothing:

Oracle's revised Java policy doesn't require every enterprise to purchase an enterprise-wide subscription. Many Java installations can remain under free terms (older versions, OpenJDK alternatives, redistributable JREs bundled with third-party applications). A targeted, installation-specific approach to Java licensing can reduce costs by 70–90% compared to Oracle's headline enterprise subscription proposal.

Redress Compliance provides end-to-end Oracle licensing assessment and audit defence services, following the same structured approach demonstrated in the Circles engagement.

1. Independent Oracle Licensing Assessment:

We conduct a comprehensive audit of your Oracle estate using our own independent tools and methodologies — not Oracle's. We map every Oracle Database, middleware, and Java deployment against your contractual entitlements, identifying genuine compliance gaps (and confirming areas of compliance) before Oracle's LMS team engages. The assessment typically takes 6–10 weeks and delivers a detailed findings report with quantified exposure and remediation options.

2. Oracle Audit Defence:

When Oracle LMS initiates an audit, we manage the entire process on your behalf: controlling data submissions, reviewing and challenging Oracle's findings, preparing formal responses with supporting evidence, and separating the audit from any sales pressure. Our Oracle Audit Defence Service has supported over 80 enterprise audits with an average claim reduction of 72%.

3. VMware and Virtualisation Defence:

We have specific expertise in Oracle's virtualisation licensing disputes — the highest-value area of audit exposure for most enterprises. Our team documents VMware configurations, analyses contract language, and prepares technical defence reports that consistently challenge Oracle's cluster-wide licensing claims.

4. Java Licensing Assessment and Remediation:

Our Java licensing practice helps enterprises navigate Oracle's evolving Java SE commercial model. We inventory all Java installations, categorise by licensing requirement, recommend migration paths (OpenJDK, Corretto, Adoptium), and negotiate targeted Java subscriptions at benchmark-validated pricing. Typical outcomes: 70–90% reduction compared to Oracle's enterprise subscription proposals.

Key point: Redress Compliance has no commercial relationships with Oracle or any software vendor. Our advice is 100% independent — we recommend the approach that delivers the best outcome for your organisation, whether that means resolving an audit, restructuring a contract, or migrating away from Oracle products entirely.

Circles' experience is representative of a consistent pattern across Oracle licensing assessments. In every engagement, the independent assessment identifies significant discrepancies between Oracle's claimed exposure and the actual compliance position. Here is a summary of comparable outcomes across industries and geographies.

The pattern is consistent: Oracle LMS assessments routinely overstate compliance exposure by 50–97%. The discrepancy stems from aggressive policy interpretations (particularly around virtualisation), automated tool overcounting (installed vs running software), and blanket licensing demands (especially for Java). Independent assessment consistently reduces these claims to a fraction of Oracle's initial number.

The lesson for any enterprise receiving an Oracle LMS inquiry: do not accept the initial findings. Engage independent expertise to validate every claim before making any commercial commitments. The investment in an independent assessment — typically a fraction of Oracle's claimed exposure — delivers returns measured in millions.

Whether you're currently facing an Oracle audit or want to proactively reduce your risk, here is a practical action plan based on the strategies that delivered results for Circles and dozens of similar engagements.

Key point: Oracle's audit claims are starting positions, not final verdicts. Circles faced $4M in claimed exposure; independent analysis reduced it to $120K. The pattern repeats across industries and geographies. The difference between an undefended and properly defended Oracle audit is measured in millions — invest in the assessment, not in Oracle's compliance narrative.