Oracle ULA Exit Yields $4M Annual Savings for U.S. Manufacturing Company

Client Profile and Context

The client is a publicly traded U.S. manufacturing company with approximately 5,000 employees and annual revenues of approximately $2 billion. The company operates manufacturing facilities across multiple U.S. states and had signed a three-year Oracle ULA covering Oracle Database Enterprise Edition, Oracle Middleware, and several Oracle technology stack components used across its production, ERP, and supply chain systems.

The ULA had been signed during a period of anticipated Oracle-driven growth. Three years later, the deployment trajectory had fallen significantly short of original projections. An application rationalisation programme and a partial shift of back-office workloads to SaaS had reduced Oracle's role in the estate. The company was paying Oracle support based on the ULA's original licence value — a baseline that no longer reflected actual usage — and Oracle's annual support increases of 8% per year were compounding that problem every year.

The Challenge: Oracle's Renewal Pressure Campaign

With eighteen months remaining on the ULA term, Oracle's account team began an intensive renewal campaign. The proposal on the table was a four-year renewal at a significantly higher total contract value, with an expanded product scope that included Oracle Cloud Infrastructure commitment. Oracle's messaging emphasised the complexity and risk of the certification process, suggesting that the company's virtualised VMware environment would create counting disputes that could leave it exposed after exit.

The company's procurement team recognised the pressure tactics but lacked independent data to push back with confidence. Their CMDB was acknowledged to be incomplete, their internal Oracle expertise was limited, and no structured ULA preparation programme had been initiated. When they engaged Redress Compliance, the ULA had fourteen months to run.

The Approach: Deployment Maximisation Followed by Clean Exit

Redress Compliance's engagement opened with a full scope assessment — reviewing the ULA contract in detail, establishing which products were covered, which entities were in scope, and what the certification window and requirements were. The assessment identified three critical issues: the CMDB was missing deployments across two manufacturing facilities; the virtualisation counting methodology being applied internally was incorrect and would have resulted in significant undercounting at certification; and a pipeline of Oracle Database deployments on new manufacturing execution system servers had been informally deferred pending the ULA renewal decision.

The strategic recommendation was a structured exit, executed in three phases:

Phase 1: Deployment Sprint (Months 14–8 Before Expiry)

The deployment sprint activated the deferred Oracle Database deployments on the new manufacturing execution servers. Because the ULA support fees were fixed regardless of deployment volume — additional deployments during the ULA term are free in licence terms — each processor licence deployed during this phase became a perpetual entitlement at zero incremental cost. The sprint added 48 processor licences to the certification baseline, licences that would have cost approximately $3.2 million at Oracle list price if purchased post-exit.

The Redress team also worked with the company's IT infrastructure group to correctly apply Oracle's processor core factor table across the VMware environment. The corrected methodology added a further 22 processor licences to the count that the company's internal team had not identified. Every additional licence certified was one fewer licence the company would need to buy in future years.

Phase 2: Audit and Certification Documentation (Months 8–2 Before Expiry)

A comprehensive deployment audit was completed across all in-scope environments — production, development, test, and disaster recovery — at all facilities. The audit methodology combined automated network discovery scanning, manual review of CMDB records, and direct interviews with application and database owners. It identified 14 Oracle installations that were not in the CMDB and confirmed the absence of any compliance gaps that Oracle could use as audit leverage.

The certification letter was drafted nine months before expiry and reviewed by legal counsel. The letter declared the final count of 312 processor licences across the ULA-covered products. Supporting documentation was prepared for every deployment, including hardware specifications, CPU model numbers, Oracle core factor calculations, and environment classification.

Phase 3: Oracle LMS Engagement and Post-Certification Support Transition

Oracle's Licence Management Services team requested a review meeting within three weeks of the certification letter submission. The LMS team raised two queries: a question about the VMware deployment count methodology, and a request to run Oracle's Collection Scripts across the estate. Redress Compliance prepared detailed written responses to both, supported by the documentation package prepared during Phase 2. The VMware counting dispute was resolved in the company's favour on the basis of the documented partition configuration. The company declined to run Oracle's Collection Scripts, as it was not contractually required to do so.

Oracle formally accepted the certification within six weeks of submission. The company then transitioned its non-production Oracle Database workloads and stable production instances to a third-party support provider, reducing annual support costs by approximately 50% on those workloads.

Financial Outcomes

The combined effect of the deployment maximisation, clean certification, and post-exit support transition produced the following financial outcomes:

• Renewal avoided: Oracle's proposed renewal would have cost approximately $18 million over four years in combined licence and support. The company instead exited with perpetual licences at no additional licence cost.
• Perpetual licences secured: 312 processor licences across Oracle Database Enterprise Edition and Middleware were certified as perpetual entitlements — a position Oracle's LMS team did not challenge, because the documentation was complete.
• Annual support reduction: By transitioning 60% of the Oracle estate to third-party support post-certification, the company reduced its annual Oracle support bill from approximately $8 million to approximately $4 million — a $4 million annual saving that compounds with every year Oracle's standard support fees would otherwise have increased at 8% per year.
• Three-year cumulative saving: Over three years, the $4 million annual reduction represents $12 million in total savings compared to the renewal path, net of advisory fees.

Key Lessons from This Engagement

This case study illustrates several principles that apply broadly to Oracle ULA exits in manufacturing and similarly capital-intensive environments:

The deployment sprint is not optional — it is the primary value driver. The 70 processor licences added through the sprint and corrected counting methodology were worth $4.7 million at Oracle list price. This is value that was available to the company during the ULA term and would have been permanently lost without a structured exit programme.

VMware virtualisation disputes are Oracle's most common certification challenge in manufacturing environments. Manufacturing estates typically run Oracle Database on VMware — a configuration Oracle deliberately keeps ambiguous in its licensing policy. Documenting the partition configuration before the certification letter is submitted removes Oracle's leverage entirely.

Oracle's Collection Scripts are a commercial tool, not a compliance requirement. Running Oracle's LMS Collection Scripts provides Oracle with data about your estate that goes significantly beyond what your certification letter commits to. You can prepare a complete and defensible certification letter using your own discovery tools, without running Oracle's scripts.

Third-party support is the most impactful post-exit cost lever for stable Oracle workloads. Once you hold perpetual licences, you can move eligible workloads to third-party support providers. The typical saving is 40–50% of Oracle's annual support rate, though the decision requires careful assessment of your Oracle dependency, upgrade plans, and contractual terms.

For more information on Oracle ULA advisory for manufacturing organisations, visit the Redress Compliance Oracle services page or explore our Oracle knowledge hub.