Client Profile
The client is a global professional services firm operating across management consulting, technology implementation, and outsourcing services in 28 countries. The organisation employs approximately 22,000 staff and maintains a substantial Oracle estate that supports finance, HR, project management, and client delivery platforms. Oracle E-Business Suite serves as the backbone of the firm's financial management infrastructure, with Oracle Database Enterprise Edition underpinning EBS and a range of custom applications developed during a decade of Oracle-first architecture. Oracle Middleware components, including Oracle WebLogic and Oracle Identity Manager, provide integration and security services across the client's hybrid IT environment.
The firm had successfully certified out of a three-year Oracle Unlimited License Agreement twelve months prior to engaging Redress Compliance. The ULA certification had been managed with appropriate rigour, and the certified licence position accurately reflected the firm's Oracle deployments. However, the post-certification estate was large: the ULA had permitted significant Oracle expansion during its term, and the certified perpetual licence position carried a total annual support obligation of $5.8M. With Oracle's 8% annual uplift applied each year, the five-year projected Oracle support spend exceeded $34M — a figure the firm's technology leadership judged unsustainable in the context of a broader cost reduction initiative.
The Challenge
The fundamental challenge of post-ULA support management is that organisations typically certify the maximum defensible licence count to protect themselves against future Oracle audit risk — and then pay support on every licence in the certified position, regardless of whether every product is actively used. The ULA certification creates a large, static perpetual position; but the organisation's actual operating dependency on that position evolves, with products retired, workloads migrated, and applications decommissioned in the years following certification.
In this firm's case, the certified estate included Oracle licences for four major product lines that had been deployed during the ULA term for projects that were now complete. These products — Oracle Identity Manager, Oracle Business Intelligence Enterprise Edition, Oracle Data Integrator, and an Oracle WebLogic deployment supporting a decommissioned client portal — were no longer in active use but were carrying annual support costs totalling $2.4M. Because the licences were perpetual, Oracle's standard position is that support is required to maintain the licence entitlement; but the firm had no operational requirement for these products going forward and no intention of returning to them.
The remaining $3.4M in annual support covered active Oracle products, but the product mix included a set of older Oracle E-Business Suite modules and Oracle Database instances on a stable, mature technology stack where the firm had not applied a security patch or requested Oracle support intervention in over two years. For these stable, predictable workloads, Oracle's premium support pricing was difficult to justify commercially.
The Approach
Redress Compliance structured the engagement around two separate workstreams that operated in parallel. The first addressed the unused licence position. The second addressed the support cost of the active but low-utilisation Oracle estate.
For the unused licences, Redress advised on the contractual and commercial mechanism for terminating Oracle support on perpetual licences for products the firm no longer required. Oracle's standard terms permit customers to terminate support on perpetual licences, subject to a reinstatement penalty if support is later re-established. For products the firm had no strategic intention to re-activate, termination was the commercially rational decision. Redress validated that each of the four product lines met the criteria for clean termination — no active deployments, no pending projects, and no strategic roadmap dependency — and prepared the contractual notice documentation for Oracle. Oracle's support team accepted the terminations for three of the four products without challenge. For Oracle Identity Manager, Oracle's team proposed a reduced-cost "sustaining engineering" support tier that the firm accepted at a cost of $280,000 annually rather than the prior $620,000 — preserving access to Oracle's security update archive while eliminating active support costs.
For the active but low-utilisation Oracle estate, Redress evaluated third-party support providers for the Oracle E-Business Suite modules and Oracle Database instances identified as stable. Following a structured evaluation of Rimini Street and Spinnaker Support, the firm transitioned eight Oracle product lines — covering EBS modules and Oracle Database instances on two legacy application environments — to third-party support. The third-party support arrangement provided equivalent functional support at 50% of Oracle's price, producing an annual saving of $1.6M on the affected product lines.
The Outcome
The combined effect of the licence terminations and the third-party support migration produced a total annual Oracle cost reduction of $4M: $2.4M from the termination and restructuring of unused licence support, and $1.6M from third-party support for stable legacy products. The firm's remaining annual Oracle support obligation — covering strategic Oracle Database, active EBS modules, and Oracle Middleware in active production — was reduced to $1.8M per year, a reduction of 69% from the $5.8M post-certification baseline.
The third-party support transition was completed over a twelve-month period, with a structured transition plan that preserved service continuity for all affected product lines. No production incidents attributable to the support transition occurred during the migration period. The restructured Oracle cost position was incorporated into the firm's five-year technology cost model, where it contributed to an overall IT cost reduction target of 20% across the firm's enterprise software estate.
Key Takeaways
- ULA certification creates a large perpetual estate that requires active management. Organisations that certify the maximum defensible count and then pay support passively are funding Oracle for products they no longer use. A post-certification review is a necessary follow-on to the certification process.
- Unused perpetual licences can be terminated — but the process requires expertise. Oracle's default position is that perpetual licences require ongoing support. Navigating the termination process without triggering reinstatement penalties or creating future compliance exposure requires careful contractual management.
- Third-party support is commercially viable for stable, non-strategic Oracle products. For Oracle E-Business Suite, legacy Database, and Oracle Middleware environments that are mature and infrequently patched, third-party support at 50% of Oracle's price is a risk-managed cost reduction strategy, not a compliance risk.
- The post-ULA support bill compounds annually. Oracle's 8% annual uplift means that every $1M of avoidable support cost left unaddressed becomes $1.47M in five years. The financial case for post-certification review strengthens with time.
- Oracle's "sustaining engineering" tier is often overlooked. For products that cannot be terminated cleanly but are no longer actively developed, Oracle's reduced-cost sustaining tier provides access to existing patches and fixes at significantly reduced cost and is worth evaluating before a full termination discussion.
Paying Oracle support on products you no longer use?
Redress Compliance reviews post-ULA Oracle estates and identifies sustainable cost reduction strategies that Oracle's team won't suggest.