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 engineering, manufacturing, and field operations, NOV maintained a significant Oracle footprint including Oracle Database Enterprise Edition, WebLogic Server, and various middleware products — all covered under an Oracle Unlimited License Agreement (ULA).
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 terms (an increasingly expensive proposition), or exit the ULA through proper certification — a process that, if executed correctly, would convert NOV’s unlimited usage rights into a defined number of perpetual licences at no additional cost.
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 and unequivocal: NOV needed to renew the ULA at a projected cost of over $22 million. Oracle’s sales representatives warned that if NOV chose not to renew, an audit would likely identify a comparable amount in compliance exposure — effectively positioning the renewal as the “easier” path versus facing an audit that Oracle implied would be both costly and disruptive.
Oracle further suggested 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. The implication was that NOV had Java compliance exposure that could only be resolved by purchasing Java subscriptions through the renewal.
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 required licensing, regardless of whether Oracle was deployed on that host or whether the virtual machines were running. This “soft partitioning” interpretation inflated NOV’s required licence count by approximately 3–4× versus actual deployed usage.
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 new Java SE subscriptions. Oracle’s pricing was presented as non-negotiable, with the implicit threat that declining would trigger an audit producing similar or greater financial exposure.
Java SE Exposure
NOV had Oracle Java SE installations across its environment that were outside the ULA scope. Oracle identified this as a separate compliance issue, suggesting it could only be resolved by adding Java subscriptions to the renewal. The total Java exposure was unclear because NOV had not yet conducted an independent assessment of which Java installations required Oracle licensing and which could be migrated to OpenJDK or other alternatives.
NOV’s Risk: 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 that Oracle could exploit in a subsequent audit. The certification process required meticulous documentation of actual Oracle deployments, accurate licence counts, and contractual compliance with the ULA’s certification requirements.
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. Our engagement followed a structured four-phase methodology designed to build an unassailable factual foundation before any negotiation with Oracle.
Complete Oracle Deployment Inventory
We 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. For each deployment, we documented: the Oracle product and version, the physical and virtual host configuration, the number of processors and cores, the applicable Oracle licensing metric (Processor or NUP), and the virtualisation technology in use. This inventory — based on actual deployment data from Oracle’s own tooling (LMS scripts) and NOV’s infrastructure management systems — became the factual foundation for the entire engagement.
Usage Analysis and Oracle Claim Challenge
We compared our 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 was deployed — Oracle’s standard “soft partitioning” interpretation. Our analysis demonstrated that NOV’s actual Oracle usage was significantly lower than Oracle’s claim. We identified specific technical and contractual arguments to challenge Oracle’s capacity-based calculations, including documented evidence that certain hosts were dedicated to non-Oracle workloads and that NOV’s virtualisation architecture limited Oracle’s actual resource access. We reduced the licence requirement by approximately 60–70% versus Oracle’s inflated numbers.
Java SE Assessment and Remediation
We conducted a separate assessment of NOV’s Oracle Java SE usage. The findings revealed that the majority of NOV’s Java installations fell into categories that did not require Oracle licensing: (a) installations of Java versions prior to the subscription requirement, (b) Java installations used solely for internal development and testing purposes, (c) Java installations that could be replaced with OpenJDK without functional impact, and (d) Java bundled within third-party applications where the third party held the licensing obligation. After identifying and categorising every Java installation, we developed a remediation plan that migrated non-essential Oracle Java to OpenJDK and retained Oracle Java subscriptions only for the small number of systems where Oracle Java was genuinely required. This reduced the Java compliance exposure from Oracle’s suggested hundreds of thousands of dollars to a minimal subscription covering fewer than 50 employees.
ULA Certification and Oracle Negotiation
With accurate deployment data and a defensible licensing position, we prepared NOV’s ULA certification documentation. This included: a complete inventory of all Oracle deployments covered by the ULA, the number of perpetual licences NOV was entitled to certify (based on actual usage, not Oracle’s inflated figures), evidence that the certification met all contractual requirements specified in the ULA, and optimisation actions taken during the final months of the ULA to ensure NOV’s certified licence count accurately reflected its ongoing needs. We then represented NOV in all communications with Oracle. When Oracle challenged specific elements of the certification, we responded with contract references and technical evidence. Oracle’s audit threat — which had been the primary pressure mechanism — lost its power once we demonstrated that NOV’s licensing position was fully documented and defensible.
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.
| Metric | Oracle’s Position | Redress Outcome | Impact |
|---|---|---|---|
| ULA Renewal Cost | $22M+ (3-year renewal) | $0 — ULA certified, no renewal | $22M saved |
| Oracle Database Licences | Required purchasing additional licences beyond ULA scope | All required licences certified as perpetual entitlements within ULA | Full coverage at zero cost |
| WebLogic Server | Included in $22M renewal | Perpetual licences certified within ULA | No additional cost |
| Java SE Exposure | Hundreds of thousands in new subscriptions | Fewer than 50 subscriptions required after OpenJDK migration | 90%+ reduction in Java cost |
| Audit Risk | Oracle threatened audit with “similar” $22M exposure | Fully documented, defensible licensing position eliminates audit risk | Zero audit exposure |
| Strategic Flexibility | Locked into another 3-year Oracle ULA | Free to adjust Oracle strategy — cloud migration, third-party support, or optimisation | Full strategic freedom |
“Not renewing our Oracle ULA felt risky — Oracle had us convinced we’d owe tens of millions if we tried. Redress Compliance navigated us through each step and turned what could have been a $22 million nightmare into a victory. They meticulously calculated our Oracle usage and showed us how to optimise it. When Oracle pushed back, Redress stood firm with facts and contract terms. Ultimately, we didn’t pay Oracle a dollar more. We certified out of the ULA, retained the necessary licences, and avoided a significant renewal. Redress’s independent expertise and unwavering support saved us $22 million and gave us confidence we’ll never be bullied into overpaying Oracle again.”
Key Lessons — What NOV’s Experience Teaches Every Oracle Customer
Oracle’s Renewal Numbers Are a Starting Position
Oracle’s $22M demand was based on inflated usage calculations that assumed peak virtual capacity rather than actual deployment. An independent assessment reduced the actual licensing requirement by 60–70%. Never accept Oracle’s renewal quote without conducting your own bottom-up assessment of actual Oracle usage. The gap between Oracle’s claim and reality is almost always substantial.
ULA Certification Is a Viable Exit Strategy
Oracle positions ULA renewal as the safe, easy path and certification as risky. In reality, certification — when executed with proper preparation and independent expertise — converts unlimited usage rights into perpetual licences at zero additional cost. The key is meticulous documentation, accurate licence counts, and contractual compliance. Oracle cannot refuse a properly prepared certification that meets the ULA’s contractual requirements.
Java SE Exposure Is Manageable
Oracle increasingly uses Java SE compliance as additional leverage in renewal negotiations. In most enterprises, a rigorous Java assessment reveals that the majority of Java installations either do not require Oracle licensing or can be migrated to OpenJDK. The Java exposure that Oracle presents as a multi-hundred-thousand-dollar problem is typically reducible to a minimal subscription covering a small number of genuinely Oracle-dependent systems.
“The pattern we see in Oracle ULA renewals is consistent: Oracle calculates the maximum possible licensing requirement, presents it as the minimum, and positions the renewal as the only alternative to a costly audit. In every ULA engagement we have conducted, the actual licensing requirement has been 40–75% lower than Oracle’s initial claim. The difference is not a negotiation discount — it is the gap between Oracle’s inflated calculation methodology and the customer’s actual, documented deployment reality.”