Editorial photograph of a global energy company control room representing enterprise Oracle estate modernization
Case Study · Oracle · ULA Certification

Oracle ULA certification. 12 million saved.

A global energy engineering group ran the ULA certification and the third party support move in one workstream. The result landed 12 million euros below the projected three year envelope on the Oracle Database and middleware estate.

Read the Framework Case Studies
EUR 12MThree year saving
a leading industry analyst firmRecognized
Industry Recognized
500+ Enterprise Clients
$2B+ Under Advisory
11 Vendor Practices
100% Buyer Side Independent

A global energy engineering group ran two parallel decisions on its Oracle estate in 2023 and 2024. Certify out of a five year Oracle Unlimited License Agreement. Move the post certification support footprint to a third party support provider on a subset of the estate. The combined work landed 12 million euros below the projected three year envelope.

This case study reads as a buyer side narrative. Use it with the ULA decision framework, the third party support comparison, the certification 90 day checklist, and the Oracle practice overview.

Key Takeaways

What this case study delivers in 90 seconds

  • 12 million euros saved over three years. Versus the projected ULA renewal envelope.
  • ULA certification scope locked early. 90 day pre certification scoping ran before the conversation with Oracle.
  • Third party support on legacy footprint. Database 11g and 12c on stable workloads.
  • Mainstream support retained on production 19c. The strategic database estate stayed with Oracle.
  • Cloud at Customer evaluated and deferred. Not yet the right fit for this estate.
  • Contractual residuals secured. Cap escalators, audit cooling off period, support reinstatement clause.
  • The work ran 11 months. Pre certification, certification, post certification reorganization.

Engagement context

The client is a global energy engineering group with a 30 plus country operating model. The Oracle estate carries Database Enterprise Edition on Real Application Clusters, several Oracle Database Options, and a WebLogic Server middleware layer. The estate sits across on premises data centers and three hyperscalers under BYOL.

Scope of work

  • Pre certification scoping. 90 day inventory and certification deployment scope.
  • Certification facilitation. Working with Oracle LMS through the formal process.
  • Third party support transition. Legacy database estate to Rimini Street.
  • Cloud at Customer evaluation. Deferred after total cost of ownership review.
  • Residual contract negotiation. Cap escalators and audit cooling off clauses.

The starting position

The client entered the engagement 14 months before the ULA expiry date. The Oracle account team had opened the renewal conversation. The projected renewal envelope sat at 8 million euros annually, equivalent to 24 million euros over three years for a similar five year structure.

The Oracle estate at engagement start

LayerProductVersionApproximate Processor count
Production strategicOracle Database Enterprise Edition19c on Linux240 Processors
Production legacyOracle Database Enterprise Edition11g and 12c180 Processors
Production optionsRAC, Partitioning, Active Data GuardVariousTied to above counts
MiddlewareWebLogic Server12c and 14c96 Processors
Cloud BYOLDatabase EE on AWS and Azure19c72 Processors equivalent

Decision frame

The engagement opened with three decisions on the table. Renew the ULA at the projected envelope. Certify out and absorb the count under existing support. Certify out and move a subset to third party support to bend the cost curve down.

The three options scored

OptionThree year cost projectionRisk profileStrategic posture
Renew the ULA24 to 28 million eurosAudit safe, no operational changeLocked in to Oracle for five more years
Certify out under Oracle support18 to 20 million eurosCounting risk on certification scopeOperational continuity, fixed support cost
Certify out plus third party support on legacy10 to 13 million eurosReinstatement risk on legacy productsCost discipline, strategic estate stays with Oracle

Certification scope work

The certification scope work ran 90 days before the formal Oracle Software Investment Guide certification process. The inventory captured every Database and WebLogic deployment by environment. The footprint was reconciled against the ULA product schedule.

The four pre certification steps

  1. Full deployment inventory. Every database instance, every host, every option.
  2. Reconciliation to ULA schedule. In scope, out of scope, dual use products tagged.
  3. Cloud BYOL count. AWS and Azure deployments counted under ACE rules.
  4. Engineering window. 60 day operational deployment window pre certification.

The cloud BYOL count is part of certification

Many ULA buyers miss this. The cloud BYOL deployments under the ULA Authorized Cloud Environment provisions count at the certification date if the ULA scope extends to cloud. Confirm cloud counting in writing before the formal certification opens.

Third party support move

The third party support move covered the legacy database estate on Database 11g and 12c. The strategic estate on 19c with Real Application Clusters and Active Data Guard stayed with Oracle mainstream support. The split kept Oracle as the support partner on the strategic core while moving the legacy estate to Rimini Street.

The third party support split

  • Strategic estate on 19c. Oracle Premier Support continued.
  • Legacy estate on 11g and 12c. Rimini Street support, fixed annual fee 50 percent below Oracle list.
  • Middleware estate. Split between Oracle Premier and Rimini Street by criticality.
  • Cloud BYOL deployments. Stayed with Oracle support to preserve the ACE coverage.

Contractual outcome

The post certification contract carried specific residual protections. The buyer team negotiated a 3 percent cap on annual support uplift, a 12 month audit cooling off period, and a written support reinstatement clause for the legacy estate at unwound terms.

The five residual clauses

  • 3 percent annual support cap. Locked for 36 months.
  • 12 month audit cooling off period. No formal audit inside the year after certification.
  • Support reinstatement clause. Legacy estate can return to Oracle at unwound terms.
  • Cloud BYOL extension. ACE coverage extended for the three year horizon.
  • Discount inheritance clause. Future Oracle orders inherit the negotiated discount band.

Financial outcome

The combined work delivered a three year financial outcome of 12 million euros below the projected ULA renewal envelope. The number is documented on a like for like basis against the original Oracle proposal. The savings split between the support cost reduction on the legacy estate and the avoided ULA renewal premium.

Three year financial outcome

ComponentOriginal projectionRealized costSaving
Oracle ULA renewalEUR 24MEUR 0 (certified out)EUR 24M avoided
Oracle Premier Support strategicEUR 0 in projectionEUR 7.2MNet new commitment
Rimini Street legacy supportEUR 0 in projectionEUR 3.6MNet new commitment
Net cost three yearsEUR 24MEUR 12.1M (cleared, rounded)EUR 12M net saving

Lessons for other buyers

Three lessons translate directly to other Oracle ULA holders considering certification. The lessons are operational, not theoretical. Each appeared on this engagement and on many other ULA exits.

The three lessons

  • Pre certification scoping is the leverage. The 90 day inventory window pays back across the term.
  • Third party support split protects the strategic estate. The legacy estate moves, the core stays.
  • Residual clauses outlast the headline. The audit cooling off and the reinstatement clause carry more weight than the cap.

What to do next

The seven step checklist below moves an Oracle ULA holder from a renewal conversation to a defensible certification and post certification position. Open it 14 to 18 months before the ULA expiry date.

  1. Pull the deployment inventory. Every Database, WebLogic, options, environment.
  2. Read the ULA product schedule. In scope, out of scope, cloud BYOL provisions.
  3. Score the three options. Renew, certify out under Oracle support, certify out plus third party support.
  4. Build the cloud BYOL count. ACE counting on every cloud deployment.
  5. Run the 90 day pre certification scoping. Before the formal certification opens with Oracle.
  6. Negotiate the residual clauses. Cap, cooling off, reinstatement, discount inheritance.
  7. Document the support split in writing. Strategic estate Oracle, legacy estate third party, cloud BYOL on Oracle.

Frequently asked questions

How long does an Oracle ULA certification take in practice?

The formal Oracle Software Investment Guide certification process runs 60 to 90 days. A well run engagement adds 90 days of pre certification scoping before the formal process opens. The total work window from scoping start to post certification contract close runs 9 to 12 months in most cases.

What is the risk of third party support on Oracle Database?

The main risks are loss of access to Oracle security patches on the unsupported version path, loss of access to My Oracle Support, and the reinstatement cost if the buyer wants to return to Oracle mainstream support. The reinstatement clause in the residual contract bounds the third risk if negotiated correctly.

Can the strategic estate stay on Oracle support while the legacy moves to third party?

Yes. The buyer can split the support footprint on Oracle Database. The strategic estate on the current supported version stays with Oracle Premier Support. The legacy estate on older versions moves to a third party. The split is the most common shape on large Oracle estates considering third party support.

Does Oracle audit more aggressively after a ULA certification?

Audit posture varies by region and account. A 12 month audit cooling off period clause is a reasonable buyer side negotiation outcome. The clause is not standard in the Oracle Master Agreement template. The clause must be added at contract refresh or at the post certification residual negotiation.

How are cloud BYOL deployments treated in the ULA certification?

If the ULA scope extends to cloud BYOL under the Authorized Cloud Environment provisions, the cloud deployments count at the certification date. Confirm the counting in writing before the formal certification opens. The cloud counting is the most common source of certification disputes on multicloud Oracle estates.

Was Oracle Cloud at Customer evaluated on this engagement?

Yes. The Cloud at Customer option was evaluated and deferred. The three year total cost of ownership did not show a clear advantage versus the certify out plus third party support split. The Cloud at Customer evaluation may be revisited at the next renewal cycle when the strategic estate moves further toward 23ai.

How Redress engages on Oracle ULA decisions

Redress runs the Oracle ULA decision work as an 11 to 14 month engagement. The work covers pre certification scoping, certification facilitation, post certification residual negotiation, and the support split where third party support is part of the answer. The engagement always sits on the buyer side.

Read the related Vendor Shield, the Renewal Program, the Benchmark Program, the Software Spend Assessment, the Benchmarking framework, the about us page, the management team page, the locations page, and the contact page.

Score your Oracle ULA exit options against the buyer side benchmark in under five minutes.
Open the Database Calculator →
White Paper · Oracle

Download the Oracle ULA Decision Framework.

A buyer side framework for the Oracle Unlimited License Agreement decision. Certification math, post certification support split, third party support comparison, and residual clause checklist.

Used across five hundred plus enterprise software engagements. Independent. Buyer side. Built for Oracle Database, Java, and applications customers approaching a ULA expiry.

Oracle ULA Decision Framework

Open the white paper in your browser. Corporate email only.

Open the Paper →
EUR 12M
Saved over three years
11 months
Engagement length
90 days
Pre certification scoping
500+
Enterprise clients
100%
Buyer side

We ran the pre certification scoping before opening the formal process with Oracle. The deployment inventory took 60 working days. The certification itself ran 75 days. The post certification residual negotiation took another 90. The combined work compressed by 20 percent versus the standard playbook and the financial outcome improved by 1.4 million euros against the original target.

Group VP IT Procurement
Global energy engineering group
More Reading

More from this practice.

Case Studies →
Oracle ULA Decision Framework
Oracle · Landing
Oracle ULA Decision Framework
Run the ULA decision.
16 min read
Oracle Third Party Support 2026
Oracle · Article
Oracle Third Party Support 2026
Rimini Street and the alternatives.
18 min read
ULA Certification 90 Day Checklist
Oracle · Article
ULA Certification 90 Day Checklist
The certification checklist.
12 min read
Oracle License Types Explained
Oracle · Article
Oracle License Types Explained
Every Oracle metric decoded.
14 min read
Oracle Multicloud Licensing
Oracle · Article
Oracle Multicloud Licensing
BYOL to AWS, Azure, GCP, OCI.
16 min read
Editorial photograph of enterprise contract negotiation strategy

Your Oracle ULA exit is your envelope.

We have run 500+ engagements across 11 publishers. Every engagement starts with one conversation.

Oracle licensing intelligence, monthly.

ULA certification signals, third party support movement, post certification residual clauses, and the wider Oracle commercial signals across every renewal cycle.