Oracle ULA Advisory Helps Brazilian Energy Firm Cut Costs and Ensure Compliance

Client Background

The client is a major integrated energy corporation headquartered in Brazil, with operations spanning upstream exploration, downstream refining, and power generation across South America. With a workforce exceeding 18,000 employees and revenues in the multi-billion dollar range, the company had built its enterprise systems around Oracle technology over two decades — Oracle Database Enterprise Edition, Oracle Fusion Middleware, Oracle E-Business Suite, and an array of Oracle database options including Real Application Clusters (RAC) and Advanced Security.

Six years prior to engaging Redress Compliance, the company had signed an Oracle Unlimited License Agreement covering Oracle Database Enterprise Edition and a defined set of database options. The ULA was structured on a three-year initial term with a three-year renewal, creating a six-year window during which the company could deploy covered products without per-unit licence fees. Annual support under the ULA was fixed at the time of signing — a significant advantage that the company had not fully appreciated.

As the final certification date approached, the company had two choices: certify the number of deployments actually in use at that date and walk away with those licences as perpetual entitlements, or renew the ULA for another term and pay Oracle another lump-sum fee plus escalating annual support. Oracle's account team was pushing hard for renewal, citing compliance risks, cloud migration plans, and the complexity of the certification process.

The Challenge: Approaching Certification Unprepared

When Redress Compliance was engaged eighteen months before the certification date, the internal situation was more precarious than the company's leadership realised. The Oracle estate had grown organically, with deployments spread across on-premises data centres in São Paulo and Rio de Janeiro, a secondary disaster recovery site in Brasília, and a small but growing presence on Oracle Cloud Infrastructure (OCI). Internal IT teams had limited visibility into the full deployment picture, and the company's software asset management (SAM) tooling had not been updated to reflect recent infrastructure changes.

Several critical problems were identified in the first phase of the engagement:

• Under-deployment relative to ULA potential: The company was using fewer licences than it was paying support on, meaning it was not extracting maximum value from the ULA structure.
• Uncontrolled deployment growth without documentation: New Oracle Database deployments had been spun up for analytics and reporting projects without proper tracking, creating compliance uncertainty at certification.
• Support cost trajectory without a ULA: Oracle's standard annual support increases run at 8% per year. If the company allowed the ULA to expire without certifying, it would be exposed to per-unit licencing at current prices plus 8% annual support escalation on any future Oracle contract.
• Cloud deployment ambiguity: The existing ULA contract predated Oracle's cloud deployment policies. The certification provisions did not explicitly address OCI deployments, creating a risk that post-certification licences would be limited to on-premises use.
• Oracle renewal pressure: Oracle's account team had presented renewal proposals at numbers 30% higher than the original ULA fee, framing renewal as the only route to continued compliance. This framing was incorrect — the company had every right to certify and exit.

The ULA Mechanics Oracle Does Not Emphasise

A critical and often misunderstood feature of Oracle Unlimited License Agreements is the relationship between support fees and deployment volume. During an active ULA term, the annual support fee is fixed at the amount agreed at contract signing. It does not increase as you deploy more Oracle products. This means that every additional deployment during the ULA period is free from a licensing perspective — the support cost does not change.

This structure creates a powerful incentive: any deployment that does not happen before the certification date is a deployment the company will need to licence separately afterwards, at full current Oracle prices, with 8% annual support increases applied each year thereafter. The mathematics of this are stark. A single Oracle Database Enterprise Edition licence with RAC can cost $150,000 to $200,000 at Oracle list price, with annual support of 22% — approximately $33,000 to $44,000 per year — escalating at 8% annually. Under the ULA, the marginal cost of that same deployment is zero.

Oracle does not proactively explain this to customers approaching certification. Its account team's commercial interest is in renewal, not in helping customers extract maximum value from the existing agreement. This information asymmetry is one of the primary reasons companies benefit from independent advisory at the ULA certification stage.

The Advisory Approach: Maximise, Document, Certify

Redress Compliance structured the engagement in three phases over eighteen months, designed to extract maximum value from the remaining ULA term while ensuring a legally sound and defensible certification.

Phase 1: Estate Discovery and Gap Analysis (Months 1–3)

The first phase involved a comprehensive discovery of the entire Oracle estate. Using Oracle's own LMS collection scripts alongside independent SAM tooling, the team created a complete inventory of every Oracle Database deployment, including virtual machine environments, RAC clusters, standby databases, and cloud instances. The discovery revealed a significantly larger estate than the company's internal records showed — including production databases used by operational technology systems in refinery management that had never been registered with the central IT department.

The gap analysis compared the discovered estate against the ULA contract terms, identifying which products and versions were covered, which were outside the ULA scope, and crucially, which deployment opportunities within the ULA coverage had not yet been utilised. The analysis identified significant under-deployment in Oracle Multitenant, Oracle Advanced Security with Transparent Data Encryption (TDE), and Oracle Label Security — all of which were included in the ULA but had not been deployed at scale.

Phase 2: Strategic Deployment Programme (Months 3–14)

With a clear picture of the under-deployment gap, a strategic deployment programme was designed and executed. The programme prioritised deployments that would deliver genuine operational value while maximising the perpetual licence count at certification. Key workstreams included:

• Database option activation: Oracle Advanced Security TDE was deployed across all production databases storing sensitive personal and financial data — a project that had been deferred due to cost concerns but was now effectively free to implement under the ULA.
• Multitenant consolidation: Several standalone Oracle Database instances used by departmental applications were consolidated into a Multitenant Container Database architecture, improving resource utilisation while increasing the certified licence count.
• Secondary site coverage: The disaster recovery site in Brasília was fully documented and added to the Oracle deployment inventory, ensuring that all DR database instances would be captured at certification.
• Analytics platform expansion: A new Oracle Database environment for operational analytics and reporting was deployed and brought into production before the certification date, converting planned future expenditure into ULA-covered deployment.

Phase 3: Certification Preparation and Execution (Months 14–18)

The certification preparation phase involved creating a complete, defensible record of every Oracle deployment to be included in the certification declaration. This included processor counts (using Oracle's processor factor table to convert physical cores to licence units), Named User Plus calculations where applicable, and documentation of the hardware configurations underlying each deployment.

Oracle's standard certification process requires the customer to submit a deployment list to Oracle License Management Services (LMS), after which Oracle has the right to request additional information or conduct its own verification. Preparing for this verification requires the same rigour as preparing for an Oracle audit — every deployment must be supported by configuration records, scripts, and inventory data that Oracle cannot credibly challenge.

The certification declaration was submitted to Oracle on the contractually specified date. Oracle requested additional documentation on three deployment categories — the OCI instances, the RAC cluster configurations, and the consolidated Multitenant environment. Each query was answered with supporting documentation within the agreed timeframe. Oracle accepted the certification without issuing a compliance claim or requesting a renewal meeting.

Results and Commercial Outcomes

The certification delivered quantified financial outcomes across multiple dimensions:

• Perpetual licence value secured: The certified deployment count represented Oracle list price value of approximately $47 million in Oracle Database Enterprise Edition licences with associated options — all converted to perpetual entitlements owned outright by the company.
• Annual support cost reduction: Post-certification, the company was no longer paying ULA support fees on the full ULA contract value. Instead, support was payable only on the certified licence count at the rates agreed at certification. Combined with the strategic decision to reduce support coverage on some legacy environments by transitioning to third-party support, annual Oracle support costs fell by $3.2 million compared to the ULA support fee.
• Oracle renewal fee avoided: Oracle's proposed renewal fee was in the range of $14 million to $18 million for a further three-year term. The company avoided this expenditure entirely by certifying and exiting the ULA.
• Future cost escalation protection: The certified licences are perpetual. Oracle's 8% annual support increases apply to the agreed support rates at certification — not to a new, inflated contract value. The company has full flexibility to reduce support costs further or negotiate support terms independently in future cycles.

Key Lessons for Oracle ULA Holders

This engagement illustrates several principles that apply broadly to any organisation holding an Oracle ULA or PULA approaching its certification date:

Start the deployment review at least 18 months before certification. The deployment opportunities within an Oracle ULA cannot be identified and executed in the final weeks before the deadline. Significant deployments — database consolidation, option activation, DR coverage — require planning, procurement, and implementation lead times that demand early engagement.

The ULA support fee does not increase with deployment. This is the single most commercially important feature of an Oracle ULA and the one most frequently overlooked by customers. Every deployment before the certification date is free. Every deployment after is a new licence purchase at current Oracle prices with 8% annual support increases applied from the outset.

Oracle's renewal pitch is a sales conversation, not a compliance conversation. When Oracle's account team warns about the complexity or risk of certification, it is acting in Oracle's commercial interest, not the customer's. Independent advisors with direct experience of the LMS certification process can assess the actual risk and prepare the documentation that makes certification straightforward.

Cloud deployments require specific contractual attention. Not all ULA contracts explicitly cover cloud deployments in the certification. Older agreements written before cloud infrastructure became standard often contain ambiguous language. Resolving this ambiguity — either through contract interpretation, negotiated amendment, or strategic deployment decisions — requires specialist contract expertise.

Oracle has no Enterprise Agreement equivalent. Some customers attempt to negotiate with Oracle using EA-style frameworks from their Microsoft or SAP experience. Oracle does not offer Enterprise Agreements. The relevant commercial structures are the ULA, the PULA (Perpetual Unlimited License Agreement), Oracle Cloud Services (OCS), and standard Customer Support Identifier (CSI) contracts. Understanding which structure applies and how its terms operate is essential before entering any Oracle commercial discussion.

About Redress Compliance

Redress Compliance is an independent enterprise software licensing advisory firm. We represent buyers only — never software vendors. Our Oracle practice covers ULA and PULA certification, audit defence, licence optimisation, renewal negotiation, and cloud licensing strategy. Both co-founders, Fredrik Filipsson and Morten Andersen, bring over 20 years of enterprise software licensing experience, including direct experience with Oracle's licensing and compliance processes. We have guided more than 60 Oracle ULA and PULA certification engagements across energy, manufacturing, financial services, and the public sector.