How Redress Compliance helped a $5 billion Brazilian oil and gas multinational exit a 60%-utilised Oracle ULA, save $4 million, achieve zero audit penalties, and reduce currency exposure.
This case study is part of our comprehensive Oracle ULA Guide. See also: American Financial Institution | Scandinavian Public Entity | $4M Annual Support Reduction | German Services Company | Global Automotive Manufacturer
A Brazilian multinational in the oil and gas sector, with operations across exploration, refining, and distribution, employing around 8,000 people and generating over $5 billion in annual revenue, sought Redress Compliance's expertise to manage its Oracle licensing.
| Oracle Product | Deployment Context |
|---|---|
| Oracle Database | High-end UNIX servers for seismic data analysis and ERP systems. |
| Oracle JD Edwards | Core ERP for finance and supply chain management. |
| Oracle Middleware | Data integration tools across exploration and distribution operations. |
To streamline licence management during an infrastructure overhaul, the firm had entered a 3-year Oracle Unlimited License Agreement (ULA) covering Database and JD Edwards modules. As the ULA approached expiration, volatile oil prices made cost control a top priority.
Oracle support is one of the largest recurring software costs for any enterprise and one of the most overlooked for optimisation. Most organisations pay the annual renewal automatically without ever questioning whether they are paying for value they actually receive. This client had the strategic vision to challenge that assumption. The results speak for themselves: $4M saved.
| Challenge | Detail | Risk |
|---|---|---|
| Budget Constraints | An oil-price downturn drove company-wide budget cuts. IT was mandated to reduce costs by at least 15%. Oracle's ULA renewal quote would consume a large portion of the IT budget, conflicting with these targets. | Failure to reduce Oracle spend would force cuts in other strategic IT initiatives, undermining digital transformation goals. |
| Underutilised ULA | Usage growth had not matched expectations. A major upstream production expansion was delayed, meaning the "unlimited" allotment was only approximately 60% utilised. | Renewing at the same cost meant paying for 40% shelfware. Every dollar spent on unused licences was a dollar diverted from productive investment. |
| Audit and Compliance Fears | A complex environment with remote oilfield sites syncing data to central databases raised concerns. Some deployments at remote locations or in test environments might not perfectly align with ULA terms. | Oracle audits in the region had a reputation for being strict. Non-compliant deployments discovered at certification could derail the exit strategy entirely. |
| Open-Source Migration Plans | The company was planning a gradual shift to PostgreSQL for certain systems. The question: renew the ULA for continuity during transition, or exit now? | Renewing would lock Oracle costs in place during a transition period where the firm was actively moving away from Oracle products. The licensing strategy needed to align with the multi-year technical roadmap. |
| Currency and Local Compliance | Operating in Brazil with a volatile Real, USD-denominated Oracle deals could spike unexpectedly. Local procurement rules added complexity. | A large USD-denominated multi-year renewal created significant foreign exchange risk in an already volatile operating environment. |
Compliance concerns at remote oilfield sites had to be resolved before ULA certification. Databases installed at contractor sites, temporary project locations, or remote facilities may fall outside ULA terms if they are not properly attributed to the ULA entity. The compliance cleanup was a prerequisite for a clean exit. See Oracle ULA Certification: Oracle Will Try to Stop You.
| Step | Activity | Outcome |
|---|---|---|
| 1. ULA Utilisation Analysis | Thorough analysis of Oracle ULA utilisation by reviewing deployment records and growth trends across all sites including remote oilfield locations. | Established that the ULA was only approximately 60% utilised. Provided a factual basis to argue that renewing at current rates meant continuing to pay for a large cushion of unused licences. |
| 2. Cost-Benefit Scenarios | Prepared clear scenarios comparing renewal versus exit. Exiting and purchasing a fixed number of licences (covering 60% usage plus buffer) projected immediate savings aligned with the cost-reduction mandate. | Analysis presented directly to the CFO demonstrated that renewal would be fiscally inefficient. The exit scenario delivered $4M in immediate savings versus Oracle's $5M renewal quote. |
| 3. Simulated Audit and Compliance Cleanup | Conducted a simulated audit examining deployments at remote oilfield sites and checking coverage under ULA terms. Found instances where databases were installed outside main environments at contractor-run sites. | Advised shutting down non-compliant installations or formally bringing them under the company's ownership before ULA expiration. Compliance posture tightened to ensure zero findings at certification. |
| 4. Negotiation with Oracle Brazil | Led negotiations with Oracle's Brazilian account team. Presented utilisation data and two options: a drastically reduced renewal or a straightforward exit with a small purchase. Oracle pushed back with audit-risk arguments. | Countered Oracle's pressure with facts. Oracle offered a shorter 1-year extension at a lower fee. Client, with Redress guidance, decided to exit immediately on their own terms rather than accept a delay tactic. |
| 5. Certification and Support Transition | Developed a meticulous certification plan, compiled all required data, and rehearsed the process internally. Negotiated post-ULA support pricing for JD Edwards and Database licences. | Ensured support costs would not spike after losing the ULA discount. Prevented any "support surprise" after exiting. Clean certification confirmed by Oracle with perpetual licences for declared usage. |
| 6. Tech Roadmap Alignment | Given plans to transition to PostgreSQL, timed licence purchases to avoid overspending on technologies slated for phase-out. Purchased licences only for databases remaining long-term. | Avoided locking capital into Oracle products scheduled for migration within 12-18 months. Licensing strategy aligned with the multi-year technical roadmap for the first time. |
For the complete decision framework on when to exit versus renew an Oracle ULA, see Oracle ULA Exit Strategy: When and How to Walk Away. For Oracle's renewal pressure tactics, see Oracle ULA Renewal: Timing, Tactics and What Oracle Will Not Tell You.
| Metric | Result | Detail |
|---|---|---|
| $4M savings realised | Avoided the $5M renewal. Purchased approximately $1M in licences for uncovered areas. | JD Edwards user licences for expanding distribution operations. Achieved immediate IT spend reduction contributing substantially to the 15% budget-cut target. |
| Zero audit penalties | Proactive compliance cleanup resolved fringe cases at remote oilfield sites. | Certification went through smoothly with Oracle confirming perpetual licences for declared usage. No audit initiated post-exit. |
| 20% lower support costs | Optimised licence holdings mean annual support is approximately 20% lower than under the ULA. | Little to no shelfware. Support costs aligned with actual needs for the first time. |
| Currency risk reduced | Avoided a large USD-denominated renewal, reducing exposure to Real/USD volatility. | Licences and support handled under local currency arrangements, making budgeting easier in Brazil's inflation environment. |
| Strategic freedom | Well-defined Oracle licence inventory and freedom to proceed with PostgreSQL migration. | No contractual weight of an unlimited deal constraining future technology decisions. CFO and executive team viewed the outcome as a benchmark for future vendor negotiations. |
The $4M savings headline is significant, but the real value is the strategic freedom this firm now has. They are no longer locked into Oracle's renewal cycle. They are not paying for 40% shelfware. And they have a clean compliance baseline that protects them from audit risk as they execute their PostgreSQL migration. That is a fundamentally different relationship with their software costs.
"Redress Compliance delivered exactly what we hoped for and more. We were staring at a costly renewal that did not make sense for us. Redress's team came in, did a deep analysis, and confirmed our suspicions. We were set to overpay if we renewed. They then expertly navigated the exit process for us. The result: no audit, no issues, just pure savings. In an industry as volatile as ours, every dollar counts, and Redress helped free up a lot of them. It was also reassuring to have an advisor who understood Oracle but was firmly on our side, with no agenda other than our success."
CIO, Brazilian Energy Firm
| Lesson | What This Case Demonstrates |
|---|---|
| Measure ULA utilisation before renewal decisions | The ULA was only 60% utilised. Without independent measurement, the client would have renewed at full price paying for 40% shelfware. Utilisation data is the single most powerful negotiation tool in any ULA decision. See Decoding Oracle ULA Pricing. |
| Exit can be more valuable than renewal | Oracle positions renewal as the safe default. In this case, exiting and purchasing right-sized licences saved $4M immediately and reduced ongoing support costs by 20%. The "safe" option was actually the expensive one. |
| Compliance cleanup is a prerequisite, not an afterthought | Remote oilfield deployments created compliance risk that could have derailed the exit. The simulated audit identified and resolved these issues before certification. Clean compliance is the foundation for a successful exit. |
| Reject Oracle's short-term extension tactic | Oracle offered a 1-year extension to delay the exit and maintain the relationship. The client recognised this for what it was: a delay tactic that would have added cost without changing the underlying economics. Sometimes the best response to a counter-offer is to proceed with your original plan. |
| Align licensing with technology roadmap | With PostgreSQL migration planned, purchasing licences only for long-term Oracle systems avoided capital waste on products slated for retirement within 12-18 months. Licensing decisions should serve the technology strategy, not the other way around. |
| Currency exposure is a real cost | For companies operating in volatile-currency countries, a large USD-denominated multi-year ULA renewal creates significant foreign exchange risk. Exiting and moving to right-sized, locally managed arrangements reduced this exposure materially. |
An underutilised ULA means you are paying a premium for capacity you never deployed. At certification, you only lock in the licences you actually used, so the "unlimited" headroom you paid for is lost. The key decision is whether the cost of renewal is justified by future deployment plans, or whether exiting and purchasing a right-sized licence set is more economical. For most organisations with flat or declining Oracle growth, exiting is the better financial outcome.
Oracle typically quotes ULA renewals in USD. For companies operating in volatile-currency countries like Brazil, a large USD-denominated multi-year commitment creates significant foreign exchange risk. Exiting the ULA and moving to a right-sized licence portfolio, potentially with local-currency support arrangements, can reduce this exposure. In this case, avoiding the $5M USD renewal substantially improved budget predictability in a volatile Real environment.
Yes, and it is often the optimal strategy. Renewing a ULA locks you into Oracle costs during the transition period. Exiting lets you purchase licences only for systems that will remain on Oracle long-term, avoiding spend on databases slated for PostgreSQL or other alternatives within 12-18 months. In this case, Redress aligned the certification with the client's migration roadmap, purchasing only the licences needed for systems staying on Oracle.
Remote deployments are a common compliance risk area. Databases installed at contractor sites, temporary project locations, or remote facilities may fall outside ULA terms if they are not properly attributed to the ULA entity. A simulated audit before certification is essential to identify these edge cases. Options include shutting them down, migrating them to covered environments, or formally bringing them under your organisation's ownership. See our guide on Oracle ULA Certification.
Yes. This is a common tactic. When Oracle senses a client is ready to exit, they may offer a shorter 1-2 year extension at a reduced fee to maintain the relationship and defer the exit decision. While this can buy time, it often delays the inevitable and adds cost. In this case, Oracle offered a 1-year extension but the client, advised by Redress, determined even that was unnecessary and exited immediately, realising the full $4M in savings upfront. See Oracle ULA Renewal: Timing, Tactics and What Oracle Will Not Tell You.
We help organisations evaluate whether to exit or renew their Oracle ULA with independent utilisation analysis, compliance preparation, and negotiation support. Fixed-fee. Vendor-neutral.
Oracle ULA Advisory ServiceIndependent ULA utilisation analysis, compliance preparation, certification support, and negotiation. Fixed-fee engagements.