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.
Part of the Oracle ULA series. This case study is part of our comprehensive Oracle ULA Guide. For the full pillar overview including certification strategies, renewal tactics, and exit planning, start there. See also: Oracle ULA Exit Strategy · Oracle ULA Certification Guide.
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.
| Oracle Product | Role in the Estate |
|---|---|
| Oracle Database EE | With Partitioning and Advanced Security options across multiple plants |
| Oracle JD Edwards | Core ERP for finance and supply chain management |
| Oracle Middleware | 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.
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. This maximised the "unlimited" value rather than leaving licences on the table.
Key insight: usage maximisation. 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. This eliminated the risk of surprises during Oracle's certification review.
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.
Related guides. For compliance tactics during certification, see Oracle ULA Certification: Oracle Will Try to Stop You. For exit planning frameworks, see Oracle ULA Exit Strategy: When and How to Walk Away.
Seamless transition. 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, including bug fixes, tax/legal updates, and technical support, at 50 to 60% less than Oracle's fees. The trade-off is you do not get Oracle patches or upgrades. For organisations on stable Oracle versions that do not 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.