Fortune 100 Automotive Group Extends Oracle Advisory Partnership to Nine Years

The Partnership That Started With an Audit Letter

Nine years ago, the head of IT procurement at one of the world's largest automotive manufacturers received a letter from Oracle's License Management Services (LMS) team. The message was standard Oracle boilerplate: a "business review" was requested, and Oracle would be sending its audit scripts to assess the client's estate. What followed was the beginning of the longest active advisory engagement in Redress Compliance's portfolio.

The client — a Fortune 100 group with manufacturing operations across four continents, 80,000+ employees, and an Oracle estate spanning Oracle Database Enterprise Edition (600+ processor licenses), Oracle WebLogic middleware, Oracle E-Business Suite, and Java SE deployed across more than 12,000 workstations — had never faced a formal Oracle LMS audit. The internal IT team was deeply capable, but navigating Oracle's compliance machinery is a different discipline entirely. They reached out to our Oracle advisory services team within 48 hours of receiving the audit notice.

What was meant to be a single engagement — audit defence, close it out, move on — became something else entirely. The value delivered in year one led to an extension. That extension led to another. Nine years later, the partnership was formally renewed through 2028. This is the story of how that happened, and what it means for enterprises managing complex Oracle estates over the long term.

Year One — Defending an $8.7M Oracle Compliance Claim

Oracle's LMS team opened with a compliance claim of $8.7M, based primarily on processor licensing gaps in virtualised environments and alleged unlicensed use of Oracle Database options — specifically, the Diagnostics and Tuning Packs, which had been inadvertently enabled through Oracle Enterprise Manager. This is not an unusual scenario. In our experience across 500+ Oracle engagements, unlicensed Database options account for the majority of initial audit claims, because Oracle DBAs routinely enable these features without realising their licensing implications.

Our team ran a parallel technical assessment before Oracle's own LMS scripts produced results. Using our proprietary Oracle audit risk assessment methodology, we identified where the genuine exposure lay, quantified it accurately, and — critically — identified where Oracle's claim was overstated. The virtualisation argument, for example, relied on Oracle asserting that the client needed to license an entire VMware cluster based on its partitioning policy. Our position challenged this on contractual grounds, pointing to the Oracle Master Agreement's definition of "Processor" versus Oracle's own non-contractual Partitioning Policy document.

After four months of structured negotiation, the audit closed at zero additional licence spend. Oracle's $8.7M claim was fully refuted. The Diagnostics Pack exposure was resolved by confirming the options had been disabled and that no production data had been extracted using their functionality. The virtualisation claim was settled through documented evidence of hard partitioning on the affected hosts. To quantify how much that outcome was worth, explore our Oracle Total Cost Optimisation resources — the avoided spend alone more than paid for multiple years of advisory retainer.

The ULA Strategy — Maximising Every Free Deployment

Following the audit defence, the client entered into a three-year Oracle Unlimited License Agreement (ULA) for Oracle Database and related middleware products. ULAs are among the most powerful — and most misunderstood — commercial structures in enterprise software. The core principle is straightforward: Oracle support fees are fixed for the duration of the ULA regardless of how many additional deployments the client makes. That means every new Oracle Database deployment during the ULA term costs nothing in licence fees. The variable is support, and support is already paid.

Our advisory team developed a deployment maximisation strategy. Using the Oracle ULA certification readiness assessment, we identified every candidate workload that could legitimately run on Oracle Database during the ULA window — test and development environments that had been running on older versions, disaster recovery nodes that had been kept unlicensed as a cost measure, new applications under development. Over the three-year ULA term, the client deployed an additional 240 processor-equivalent Oracle Database licences at no additional cost. At prevailing Oracle list prices for Database Enterprise Edition, that represented approximately $3.1M in licence value captured for free.

This is the advice that separates informed ULA management from passive contract management. Many enterprises under-utilise their ULA window because no one is tracking deployment opportunities against the certification date. Our team ran quarterly reviews throughout the ULA term, cross-referencing infrastructure projects with remaining deployment capacity. By the time the ULA was certified, the client's Oracle estate was fully rationalised and accurately documented — which also meant the certification count came in lower than Oracle had projected, reducing future support costs.

Containing Oracle's 8% Annual Support Escalation

Oracle's support fee structure is one of the most quietly damaging mechanisms in enterprise software. Oracle charges 22% of net licence value per year for Premier Support, and those fees increase by 8% per year by default. Over a decade, that compounding effect turns a manageable annual support bill into something considerably larger — at 8% annually, support costs effectively double every nine years.

For our client, the rationalisation work done at ULA certification provided an immediate lever: the support base was reset against the certified licence count rather than the original purchase price of all Oracle products ever bought. This alone reduced annual support spend by approximately $820,000 per year. Beyond the immediate reset, we renegotiated a contractual cap on annual support increases at 4% for the following three years — a provision Oracle does not advertise but will accept under the right commercial conditions. The combination of rationalised base and capped escalation saved the client an estimated $2.4M over three years compared to the default trajectory.

For organisations on Extended Support — which adds an additional 10% premium on top of the standard 8% annual increase — the maths are even more compelling. Our Oracle support cost optimisation assessment provides a full projection of your support trajectory and identifies the levers available at renewal. The third-party support option, explored in years five and six of this engagement, can deliver 47–65% savings on legacy products, as the client discovered first-hand.

Java SE Audit Defence — A $12.6M Claim Resolved at $2.1M

Oracle's shift to an employee-based Java SE subscription model in January 2023 created an immediate compliance crisis for large enterprises. The client had 12,000+ workstations running Oracle JDK — some on versions that pre-dated the subscription requirement, some on newer builds that Oracle claimed triggered a subscription obligation. Oracle's LMS team contacted the client in year seven of the partnership with a compliance claim of $12.6M per year under the employee subscription model, calculated at $10.50 per employee per month across all 80,000 employees.

This calculation was aggressive on multiple dimensions. The employee definition Oracle applies to its Java SE Universal Subscription includes not just direct employees but all contractors, outsourcers, and consultants who "support internal business operations" — a scope that Oracle interprets broadly and clients should challenge systematically. Our team used the Java audit risk assessment to establish the actual eligible population, identify which JDK versions were genuinely in scope, and document the evidence base for a materially lower obligation.

After six months of negotiation, the subscription was agreed at $2.1M per year — a reduction of $10.5M per year from Oracle's opening position. The settlement included a contractual cap on annual subscription increases at 5% per year for the term, a migration pathway to OpenJDK for non-production environments, and a right to audit Oracle's own determination methodology. For the full technical and commercial framework behind this defence, our Oracle Java audit defence white paper covers the exact negotiation scripts used across 40+ live Java audits. The broader picture of our Oracle advisory work — including audit defence and support optimisation — is detailed in our case studies library.

Why the Partnership Was Extended — And What It Tells You

In early 2026, the client's CIO asked a straightforward question during the annual partnership review: what had Redress delivered, in aggregate, over nine years? The answer, compiled across all engagements, was just over $14M in avoided costs, hard savings, and commercial improvements — against a total advisory investment that represented less than 8% of that figure. The partnership was extended through 2028 without negotiation.

The lesson here is structural rather than transactional. Oracle's commercial model is designed to grow your spend over time — through support escalation, audit enforcement, and product bundling. The only effective counterweight is sustained, independent expertise that understands Oracle's playbook as well as Oracle does. A single advisory engagement solves a single problem. A long-term advisory partnership changes the commercial dynamic: Oracle knows you have expert representation, and that knowledge shapes every subsequent negotiation before it even starts.

For enterprises managing complex Oracle estates, we recommend beginning with a baseline assessment of your current position — before the next audit notice arrives. You can book a confidential call with our Oracle advisory team to discuss your specific estate, or explore the Oracle Knowledge Hub for the full library of licensing, audit, and negotiation resources that underpin our advisory work. Redress Compliance maintains zero commercial relationships with Oracle or any software vendor — our only incentive is your outcome.

Written by Fredrik Filipsson, Co-Founder, Redress Compliance. 20+ years in enterprise software licensing and commercial negotiation.