How Redress Compliance helped a $2 billion U.S. manufacturer exit an Oracle ULA, transition to third-party support, save $4 million annually ($12M over 3 years), and resolve $52 million in potential licence gaps before Oracle could act.
A mid-size U.S. manufacturing company serving the automotive and aerospace industries, with approximately 5,000 employees and $2 billion in annual revenue, had entered a 3-year Oracle ULA to support rapidly expanding IT needs after a period of growth and acquisitions.
With Partitioning and Advanced Security options across multiple plants
Core ERP for finance and supply chain management
Factory management and supply chain integration tools
All Oracle workloads ran on-premises across multiple U.S. manufacturing plants and data centres, with some virtualisation in use. As the ULA neared expiration, the company faced the pivotal decision to renew or certify out.
Growth slowed in the latter half of the ULA term. The company hadn’t deployed as many Oracle instances as projected — a classic shelfware situation where the hefty ULA investment wasn’t yielding full value.
Oracle’s annual support fees (~22% of original licence value) exceeded $1 million per year. With actual usage below expectations, this felt disproportionately high and consumed a significant portion of the IT budget.
Oracle account representatives were pushing the company to renew, emphasising it would “protect” them from compliance issues — implicitly suggesting exiting could expose them to an audit. Classic Oracle fear-based renewal tactics.
Concern about Oracle Database instances in test environments and a legacy JD Edwards ERP system recently brought under Oracle support. These had to be carefully verified as covered by the ULA or separately licensed.
The CIO was exploring third-party support to cut costs. This required exiting the ULA with all licences in hand — Oracle doesn’t permit third-party support under an active ULA. The only path to cheaper support was exit.
Redress performed a full inventory covering every Oracle Database instance (production, development, testing) and JD Edwards ERP modules. The audit revealed several non-production databases running options (such as Partitioning) that could be turned off or consolidated, and confirmed the JD Edwards system was fully covered under the ULA’s product list.
Given under-utilisation, Redress recommended proactively expanding Oracle deployments in a controlled manner before ULA expiration. Key business applications were identified where additional Oracle Database instances could improve performance or redundancy. By scaling up these deployments (within genuine business need), the company increased the count of processor licences it would ultimately certify — maximising the “unlimited” value rather than leaving licences on the table.
Usage maximisation before certification is one of the most effective ULA strategies. Every additional deployment during the unlimited period converts to a perpetual licence at exit, dramatically increasing the return on your ULA investment.
Redress addressed potential compliance gaps: for test databases running extra options, they guided IT staff to either disable unneeded features or include them in the final certification count. Every deployment was cross-checked against ULA inclusions so nothing fell through the cracks — eliminating the risk of surprises during Oracle’s certification review.
For compliance tactics during certification, see Oracle ULA Certification: Oracle Will Try to Stop You.
Redress advised against renewal and outlined a clear exit strategy: certify all entitled usage, then transition to a third-party support provider immediately after ULA conclusion. A detailed timeline ensured seamless support transition without any lapse in coverage. Redress helped prepare formal notifications to Oracle, preempting last-minute renewal pitches.
Redress negotiated with Oracle to secure assurances regarding certification — including confirmation that legacy JD Edwards licences would be counted as perpetual licences at exit. Oracle, seeing a well-prepared customer, raised no objections to the certification approach.
For exit planning frameworks, see Oracle ULA Exit Strategy: When and How to Walk Away.
By moving to third-party support, the firm saved approximately $4 million annually — the difference between Oracle’s maintenance fees and the third-party provider’s fees. Over three years: $12 million in savings reinvested into IT and operational improvements.
Through the late-term deployment boost, the client certified hundreds of Oracle licences valued at roughly $120 million in list terms. These are now perpetual assets, usable indefinitely without additional licence purchases.
Identified and resolved $52 million worth of potential licence gaps (list-price value of software deployed outside entitlements) before Oracle could levy penalties. Proactive remediation protected against what could have been a significant financial hit.
No longer tied to Oracle’s renewal cycle. Support costs slashed 50–60% via third-party provider. Factory systems continue running seamlessly. If Oracle offers new products, the company evaluates on merit, not obligation.
The switch to third-party support was seamless — users noticed no difference in service levels, but the IT department noticed a transformative difference in the budget.
“Redress Compliance enabled us to turn a difficult situation into a big win. Their expertise in Oracle licensing is second to none — they showed us how to fully utilise our ULA and then guided us out of it without a hitch. Thanks to Redress, we slashed our Oracle support costs and ended a cycle of overspending. They truly acted as our advocate, not beholden to Oracle or any vendor, which gave us confidence every step of the way.”
— IT Director, U.S. Manufacturing Company
Third-party support providers (like Rimini Street or Spinnaker Support) offer Oracle maintenance — bug fixes, tax/legal updates, and technical support — at 50–60% less than Oracle’s fees. The trade-off is you don’t get Oracle patches or upgrades. For organisations on stable Oracle versions that don’t plan to upgrade, this is often a highly cost-effective option. In this case, the manufacturer saved $4M annually by making the switch. See our Oracle Third-Party Support Advisory Service.
No. An active Oracle ULA includes Oracle support as part of the agreement. You must exit (certify out of) the ULA first, which converts your usage to perpetual licences. Only then can you cancel Oracle support and transition to a third-party provider. This is why ULA exit planning and third-party support strategy should be coordinated together.
During the unlimited period, you can deploy Oracle products freely. Usage maximisation means strategically expanding deployments (within genuine business need) before certification to lock in more perpetual licences at exit. This increases the return on your ULA investment. In this case, Redress identified business applications where additional Database instances could improve performance or redundancy, resulting in hundreds of additional certified licences valued at $120M in list terms.
Test and development instances must be accounted for in the certification count or properly decommissioned. Common issues include non-production databases running licensed options (like Partitioning or Advanced Compression) that were enabled for testing but never disabled. Redress recommends a comprehensive audit of all environments — production, dev, test, staging, DR — to identify these before certification. Options include disabling the features, consolidating instances, or including them in the final licence count.
Yes — when the documentation is precise and comprehensive, Oracle typically accepts certification without challenge. Oracle’s pushback usually targets poorly prepared certifications where gaps or ambiguities exist. In this case, Redress’s meticulous audit, compliance remediation, and documentation meant Oracle raised no objections. The certification was accepted smoothly, with Oracle confirming perpetual licences for all declared usage. See our Oracle ULA Certification guide.
We’ll help you assess your usage, explore third-party support options, and develop a roadmap to savings. Don’t renew blindly — let Redress Compliance show you how to optimise your Oracle licensing and liberate your IT budget.
This case study is part of our Oracle ULA Guide pillar. Explore related case studies and guides: