01 — The Client: NOV Inc.
NOV Inc. is a major US-based energy technology company providing equipment and technology for the global oil and gas industry. With operations spanning multiple continents and a complex IT infrastructure supporting global manufacturing, field services, and engineering operations, NOV had been operating under an Oracle Unlimited License Agreement (ULA) covering Oracle Database Enterprise Edition and Oracle WebLogic Server.
The ULA had served NOV well during a period of rapid growth, allowing unlimited deployment of covered Oracle products without per-licence constraints. But as the ULA approached expiration, NOV faced a critical decision: renew at Oracle's proposed cost, certify the ULA and exit to perpetual licences, or face an uncertain position if Oracle initiated a compliance review after expiration.
02 — The Challenge: Oracle's $22M Pressure Campaign
As the ULA expiration approached, Oracle's sales team launched an aggressive renewal campaign. Their position was clear: NOV needed to renew the ULA at a projected cost of over $22 million. Oracle further warned that if NOV chose to exit the ULA, an audit would find a similar amount owed in perpetual licences — creating a coercive framing designed to discourage independent evaluation.
Oracle's Claim: Full Virtual Capacity
Oracle calculated NOV's licensing requirements based on the peak capacity of NOV's virtualised environments — not actual usage. Under Oracle's interpretation, every processor in every VMware host running Oracle software required licensing, regardless of actual Oracle VM density or workload allocation. This peak-capacity methodology produced a dramatically inflated licence count that bore little relationship to NOV's genuine Oracle deployment footprint.
Oracle's Demand: $22M+ Renewal
Based on the inflated usage numbers, Oracle proposed a ULA renewal exceeding $22 million, representing a significant increase over the original ULA cost. The renewal included Oracle Database Enterprise Edition, WebLogic Server, and — separately — Oracle Java SE subscriptions that Oracle insisted would be required after the ULA expired.
Java SE Exposure
Oracle identified Java SE installations across NOV's environment that were outside the ULA scope as a separate Java compliance exposure. Oracle suggested this could only be resolved by adding Java SE subscriptions to the renewal package — a product not covered by the existing ULA — which would have increased the total cost even further. Hundreds of thousands of dollars in new annual Java SE subscriptions were cited.
Risk of Improper Certification
If NOV chose to exit the ULA without proper preparation, an incorrect certification could result in fewer perpetual licences than actually needed, creating an immediate compliance gap. Oracle would be entitled to invoice for those licences at full list price with back support, potentially matching the renewal cost Oracle was proposing — and without the commercial terms that a renewal negotiation might achieve.
Approaching an Oracle ULA expiration with renewal pressure?
03 — Our Approach: The Redress Compliance Engagement
NOV engaged Redress Compliance to provide an independent assessment of their Oracle licensing position, develop a ULA exit strategy, and represent NOV's interests in all Oracle communications. The 14-week engagement covered four workstreams running in parallel.
Complete Oracle Deployment Inventory
Redress conducted a comprehensive inventory of every Oracle Database and WebLogic Server deployment across NOV's global infrastructure. This included production, development, test, staging, and disaster recovery environments across all geographies. Every instance was documented by version, edition, deployment type, and hardware configuration — creating the complete picture required for an accurate certification count.
Usage Analysis and Oracle Claim Challenge
Redress compared the deployment inventory against Oracle's usage claims. The critical finding: Oracle had calculated NOV's licensing requirements based on the full physical capacity of VMware hosts where Oracle software was installed — not the actual Oracle VM footprint. This peak-capacity methodology produced a count roughly 3 to 4 times higher than NOV's genuine Oracle deployment. Redress documented the technical and contractual basis for challenging Oracle's methodology, preparing a counter-analysis that Oracle's compliance team could not credibly dismiss.
Java SE Assessment and Remediation
Redress conducted a separate assessment of NOV's Oracle Java SE compliance. The findings revealed that the majority of NOV's Java installations fell into categories that did not require Oracle licensing: internal tooling running on OpenJDK-compatible distributions, developer environments, and applications with no dependency on Oracle-specific Java APIs. A targeted migration to OpenJDK was completed, reducing the genuine Oracle Java SE obligation from hundreds of thousands of dollars annually to fewer than 50 subscriptions covering specific production dependencies.
ULA Certification and Oracle Negotiation
With accurate deployment data and a defensible licensing position, Redress prepared NOV's ULA certification documentation. This included a complete inventory of all Oracle deployments covered by the ULA, technical evidence demonstrating the deployment count for each covered product, documentation of the virtualisation methodology applied and its contractual basis, and a formal certification submission meeting Oracle's requirements. Redress led all negotiations with Oracle on the certification count, responding to Oracle's challenges with evidence-based counter-positions.
04 — The Outcome: $22M Saved, Full Compliance Achieved
NOV Inc. successfully exited its Oracle ULA without renewing and without paying Oracle any additional fees. The outcome was transformative for NOV's Oracle licensing position and its broader IT strategy.
| Area | Oracle's Proposed Outcome | Achieved Outcome |
|---|---|---|
| ULA Renewal Cost | $22M+ (3-year renewal) | $0 — ULA certified, no renewal |
| Oracle Database Licences | Required purchasing additional licences beyond ULA scope | All required licences certified as perpetual entitlements within ULA |
| Java SE Subscriptions | Hundreds of thousands in new annual subscriptions | Fewer than 50 subscriptions required after OpenJDK migration (90%+ reduction) |
| Audit Risk | Oracle threatened audit with “similar” $22M exposure | Fully documented, defensible licensing position eliminates audit risk |
| Strategic Flexibility | Locked into another 3-year Oracle ULA | Free to adjust Oracle strategy — cloud migration, third-party support, or optimisation |
05 — Key Lessons: What NOV's Experience Teaches Every Oracle Customer
Oracle's Renewal Numbers Are a Starting Position
Oracle's ULA renewal proposals are built on methodology choices that systematically overstate the genuine licensing requirement. Peak-capacity virtualisation claims, Employee Metric Java SE calculations, and assumptions about deployment scope are all contestable. Every Oracle customer approaching a ULA expiration should obtain an independent assessment before treating Oracle's figures as a basis for negotiation. The gap between Oracle's opening position and the independently verified requirement is typically 40 to 75% — and in NOV's case, it was effectively 100%.
ULA Certification Is a Viable Exit Strategy
Oracle's messaging around ULA expiration is designed to create fear about the certification process. In reality, a properly prepared certification — with complete deployment documentation, a defensible virtualisation methodology, and independent expertise — is a straightforward exit path that converts ULA deployments into perpetual licence entitlements at no additional cost. The key is preparation: certification requires the same evidence base that would be needed to defend against an Oracle audit.
Java SE Exposure Is Manageable
Oracle's Java SE pricing model creates apparent exposure that is dramatically reduced through systematic remediation. The majority of enterprise Java installations — typically 70 to 90% — can be migrated to OpenJDK distributions with limited disruption, eliminating Oracle commercial licensing requirements entirely. The remaining dependencies on Oracle-specific Java features are invariably a small fraction of the estate and can be managed through targeted subscriptions at a fraction of Oracle's initial demand.