Client Profile
The client is a global management consulting and professional services firm operating in more than 40 countries, serving clients across financial services, energy, life sciences, and the public sector. The organisation employs approximately 65,000 staff globally and manages a substantial enterprise technology estate that supports its consulting delivery platforms, knowledge management systems, internal finance and HR operations, and a client-facing analytics capability. Oracle Database and Oracle E-Business Suite are core components of the organisation's back-office infrastructure, with Oracle deployments distributed across primary data centres in the United States, United Kingdom, and Singapore, and additional satellite environments supporting regional operations.
The firm had entered its most recent Oracle Unlimited License Agreement three years prior, covering Oracle Database Enterprise Edition, Oracle Real Application Clusters, Oracle Partitioning, Oracle Advanced Security, and Oracle Multitenant. The ULA had been structured during a period of rapid headcount growth and significant investment in Oracle-powered analytics infrastructure. At the time of the engagement with Redress Compliance, the firm's Oracle usage had stabilised and its strategic direction had shifted towards cloud-native platforms that reduced, rather than expanded, its dependence on Oracle Database for new workloads.
The Challenge
In the twelve months before the ULA expiry date, Oracle's account team approached the firm's technology procurement function with a renewal proposal. Oracle characterised the certification and exit option as commercially and technically risky, citing the complexity of the firm's multi-site Oracle estate, the prevalence of Oracle Database Options deployed across the environment, and the assertion that independent certification of a ULA of this scale would require an internal investment of time and resource that would outweigh the savings from exiting the agreement. Oracle's renewal proposal was priced at $7M per year in a new ULA with a three-year term commitment — an additional $21M in total commitment over the new term.
The technology leadership team was sceptical. The firm's actual Oracle usage had grown substantially during the ULA term — from approximately 120 to over 320 processor licences across the estate — but it had done so in a planned and documented way as part of the analytics expansion programme. The CTO's view was that the organisation had maximised its ULA and now had a well-defined perpetual licence base that, if correctly certified, would eliminate the need for another open-ended unlimited commitment.
The procurement function engaged Redress Compliance eight months before expiry to conduct an independent assessment of the certification feasibility, the correct processor count, and the commercial case for exit versus renewal.
The Approach
Redress Compliance began with a full technical deployment survey of the firm's Oracle estate across its three primary data centre locations and seven satellite environments. The survey mapped all Oracle Database installations, identified the Oracle options and packs deployed on each server, and produced a processor count based on Oracle's published counting rules, applied conservatively and with full technical documentation for each server's configuration.
The survey identified 328 processor licences across the estate — a count the Redress team considered technically complete and defensible. Oracle's own pre-certification estimate had placed the count at 386 processors, inflated primarily by two factors: first, the inclusion of three Oracle Database instances running in a disaster recovery environment that the ULA agreement excluded from the licensed scope; and second, the counting of Oracle Advanced Security and Oracle Multitenant on a subset of servers where those options were installed but had never been configured or activated.
Redress worked with the firm's legal team to review the ULA product schedule and confirm the contractual scope. The disaster recovery exclusion was clearly documented in the ULA contract, reducing the qualifying count by 28 processors. The options analysis required Oracle's own product documentation to confirm that installed-but-unconfigured options are not licensable under Oracle's standard licence terms, reducing the count by a further 30 processors. The final certified position was 328 processor licences — 58 fewer than Oracle's estimate.
In parallel, Redress prepared the certification letter, the supporting technical documentation package, and a commercial analysis demonstrating the long-term cost difference between the certified exit position and Oracle's proposed renewal. The analysis showed that at Oracle's 22% annual support rate, certifying 328 processors at the correct Oracle price list value would produce an annual support obligation of approximately $5.8M — compared to Oracle's renewal proposal of $7M, a difference of $1.2M per year or $3.6M over the equivalent three-year term. The ULA renewal fee itself added another $7M in incremental licence cost, making the total three-year differential $10.6M in favour of certification and exit.
The Outcome
The certification letter was submitted to Oracle at the agreed date. Oracle's GLAS team requested clarification on two technical points — the disaster recovery scope exclusion and the options counting methodology — both of which the Redress documentation package addressed directly and completely. Oracle accepted the certification within six weeks of submission, without proceeding to an independent verification process or raising compliance concerns.
The firm's post-certification annual Oracle support obligation was $4.2M — a reduction of $2.8M compared to Oracle's renewal proposal rate and a saving of $7M in avoided licence renewal fees. The organisation now holds perpetual Oracle Database Enterprise Edition licences at a defined and documented count, carries no unlimited commitment to Oracle, and has complete clarity on its compliance position for the first time in six years.
Key Takeaways
- Oracle's "too complex to certify" argument is a commercial position, not a technical assessment. Virtually any Oracle ULA can be certified and exited with the right technical methodology. The argument is designed to prevent organisations from engaging independent advisors who would demonstrate that certification is feasible.
- Oracle typically overstates the certification count by 10–20%. Disaster recovery exclusions, unconfigured options, and incorrect cluster scope are the most common sources of overcount. Each requires specific contractual and technical analysis to challenge successfully.
- The certification letter is a legal document. What you certify becomes your permanent licence position. Errors — whether understating or overstating the count — have long-term consequences. Expert review before submission is non-negotiable.
- Eight to twelve months before expiry is the right engagement window. The technical audit, contractual analysis, and certification documentation take time. Organisations that engage in the final ninety days consistently produce weaker certification positions under time pressure.
- A clean certification creates commercial leverage. A documented, accepted perpetual licence position is a negotiating asset in future Oracle discussions — for cloud services, incremental licences, and support arrangements alike.
Oracle pushing you to renew your ULA rather than certify out?
Redress Compliance provides independent certification advisory — without Oracle's commercial incentives.