Circles Telco Singapore: $4M Oracle Compliance Exposure Eliminated

Executive Summary

Circles is a digital-native telecommunications provider based in Singapore, serving millions of mobile subscribers across Southeast Asia. Its IT environment runs on a virtualised VMware infrastructure with Oracle Database Enterprise Edition for core data management, Oracle WebLogic Server for middleware, and Oracle Java SE deployed across internal applications and endpoints.

When Oracle's License Management Services (LMS) initiated a compliance inquiry, Circles faced a potential $4M+ exposure driven by three converging risks: Oracle's aggressive interpretation of VMware "soft partitioning" rules, WebLogic licence compliance questions across clustered environments, and Java SE licensing obligations triggered by Oracle's revised commercial Java policy. Oracle's sales team was simultaneously pressing Circles to resolve the situation by purchasing a $6M+ Unlimited License Agreement (ULA).

By engaging Redress Compliance for an independent licensing assessment and Oracle audit defence, Circles eliminated the entire $4M exposure through entitlement corrections, technical reconfigurations, and factual rebuttals. No unplanned licence purchases were required, and the Oracle audit was withdrawn. This case study is part of the Oracle Pricing and Negotiation Guide — see also ADNOC: $6M Saved and NOV Inc: $22M Saved.

Key takeaway: Oracle's LMS audit claimed $4M in compliance gaps. Independent analysis reduced the genuine exposure to $120K — a 97% reduction. The difference was Oracle's aggressive interpretation of virtualisation rules, overcounting of WebLogic deployments, and blanket Java licensing demands. Every claim was factually challengeable with proper data and contract analysis.

The Challenge: Three Converging Oracle Compliance Risks

Circles' Oracle licensing situation was typical of fast-growing technology companies in the APAC region: IT infrastructure had scaled rapidly to support subscriber growth, while licensing governance hadn't kept pace. Three distinct compliance risks converged simultaneously when Oracle LMS initiated its formal inquiry.

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

Circles ran Oracle Database Enterprise Edition on a VMware vSphere infrastructure. 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 required licensing. This meant Oracle was asserting that Circles needed to licence all 12 servers — approximately 192 cores and 96 Oracle Processor licences — 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 (approximately 24 licences at $1.14M) and licensing 12 servers (approximately 96 licences at $4.56M) was $3.42M. Oracle LMS presented a gap of approximately $2.4M after accounting for existing entitlements. For the detailed methodology behind Oracle's virtualisation licensing claims, see our guide on Oracle advisory services.

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 approximately $800K in additional Processor licences — an assertion that included development and test environments in a Processor licence calculation that was factually incorrect.

Circles' WebLogic deployments included production environments licensed correctly under existing entitlements, development and test instances that Oracle had incorrectly included in the Processor licence count, and disaster recovery environments that qualified for reduced-rate Disaster Recovery licensing rather than full Processor licensing. Oracle's count was wrong on every category.

3. Java SE — Blanket Subscription Demand

Java SE was deployed across Circles' internal applications and developer workstations. Oracle's revised commercial Java policy had triggered a compliance inquiry, and LMS asserted that Circles required an enterprise-wide Java SE subscription covering its entire employee base — a demand worth approximately $800K annually.

In reality, Oracle's commercial Java SE licensing applies to specific production use cases — not every Java installation on every device. A proper classification of Circles' Java estate identified a targeted subset of installations genuinely requiring a commercial licence, reducing the actual requirement from $800K to approximately $120K. The remainder could be addressed through OpenJDK migration or fell into categories that did not require a commercial licence under Oracle's own policies. Our Java Knowledge Hub explains this classification methodology in detail.

How Redress Compliance Responded

Redress Compliance engaged across all three compliance areas simultaneously, working to establish Circles' true licensing position before Oracle could formalise its audit findings or apply additional commercial pressure.

VMware Infrastructure Analysis

Redress Compliance conducted a technical analysis of Circles' VMware environment, documenting the specific hosts running Oracle workloads, the configuration of Oracle Database virtual machines, and the network segmentation between Oracle and non-Oracle workloads. Rather than accepting Oracle's cluster-wide licensing position, Redress applied Oracle's own technical policies to demonstrate that the factual circumstances of Circles' deployment did not require cluster-wide licensing under several interpretations that Oracle's LMS team had failed to consider.

The documentation package prepared for Oracle included infrastructure diagrams, VM configuration exports, Oracle process mapping, and a legal analysis of Oracle's published licensing policies demonstrating that Oracle's position overstated the actual requirement. Oracle withdrew its database licensing claim in full following review of this documentation.

WebLogic Environment Classification

Redress Compliance mapped every WebLogic instance in Circles' environment against Oracle's environment classification criteria. Development and test instances were reclassified appropriately, disaster recovery environments were documented under applicable licensing policies, and production deployments were verified against existing entitlement documentation. The outcome: Circles' existing WebLogic entitlements were sufficient to cover all production deployments, and the incorrectly classified environments were addressed at no additional cost.

Java SE Scope Assessment

The Java assessment classified every Java installation by version, usage context, and applicable licensing requirement. The targeted subset genuinely requiring a commercial Oracle Java SE subscription — approximately $120K annually — was confirmed and addressed. The remainder of Oracle's $800K claim was eliminated through proper classification and an OpenJDK migration programme covering development workstations and non-production systems.

Key Takeaways for Technology Companies in APAC

Oracle's VMware soft partitioning policy is its most effective audit amplifier. The policy allows Oracle to multiply licensing claims by a factor of three to five or more on virtualised infrastructure. Challenging this position requires technical evidence — infrastructure documentation, Oracle process mapping, and a legal analysis of Oracle's own published policies. Redress Compliance has challenged this position successfully across multiple engagements.

Never accept Oracle's environment classification. Oracle's LMS team routinely includes development, test, and disaster recovery environments in Processor licence calculations. Proper classification of these environments — documented with Oracle policy references — eliminates a significant portion of any claimed WebLogic or Database shortfall.

Java SE requires targeted assessment, not enterprise-wide subscription. Oracle's blanket Java licensing demands are calibrated to generate maximum revenue. A proper classification of actual commercial Java use consistently reveals that the genuine requirement is 10 to 30% of Oracle's stated claim. Our Oracle Audit Response Playbook provides the full methodology.