Global Manufacturer: $4.2M Saved Through Strategic Oracle ULA Certification

The Challenge

A global manufacturing group — 18 subsidiaries, operations across eight countries — entered the final 90 days of a 4-year Oracle Unlimited License Agreement covering Oracle Database Enterprise Edition, RAC, Partitioning, and GoldenGate. The ULA had been signed at a time when the group was undergoing rapid M&A activity and needed the flexibility to deploy without counting licences. Four years later, the deployment picture had changed dramatically — and Oracle's account team had a detailed view of exactly how incomplete the certification documentation was.

Oracle's position was straightforward: the group's deployment records were insufficient to support a clean ULA certification. Without a certified deployment count that Oracle's LMS team would accept, the group faced two options in Oracle's framing: renew the ULA at Oracle's proposed rate (approximately $6.8M over three years) or face a post-ULA true-up for all uncounted deployments. Oracle's proposed renewal carried pricing that was 40% above the group's estimated actual licence requirement — Oracle had deliberately priced in a compliance premium based on the deployment documentation gap.

The group engaged us 11 weeks before the ULA expiry date. This is a common engagement pattern for Oracle ULAs: the certification problem is understood internally for months, but the complexity and Oracle's pressure tactics delay external engagement until the timeline is genuinely compressed. Eleven weeks is workable — but it requires immediate, structured action.

Our Approach

1. Rapid Deployment Discovery Across All 18 Entities

   We deployed a structured Oracle deployment discovery process across all 18 subsidiaries simultaneously. This used a combination of Oracle's OCSM (Oracle Customer Success Manager) approved scripts and third-party discovery tooling to enumerate every Oracle Database instance, RAC node, Partitioning usage, and GoldenGate deployment in scope. Six of the 18 subsidiaries had no Oracle Database deployments — they were running on SQL Server and PostgreSQL estates. These entities were excluded from the ULA certification scope entirely.

2. Maximising Certifiable Deployment Count

   The ULA certification mechanism works in the customer's favour when the deployment count is maximised — every processor licence certified "freezes" that entitlement in perpetuity. We identified five scenarios where Oracle Database instances had been stood up in development and test environments that fell within the ULA scope but had not been included in the internal deployment register. Including these environments increased the certified deployment count by 23%, which significantly improved the group's post-ULA licence position relative to what Oracle's account team had assumed.

3. ULA Certification Meeting Preparation

   Oracle's LMS team conducts ULA certification meetings with a detailed agenda and challenges every deployment entry in the certification register. We prepared the group's documentation package to address every predictable Oracle challenge: Core Factor Table calculations for each processor, hardware refresh records for servers deployed within the ULA term, virtual machine configurations, and the contractual basis for each subsidiary's inclusion in the ULA scope. This preparation eliminated the ambiguity Oracle typically exploits to delay or challenge certification.

4. Certification Negotiation and Post-ULA Terms

   The ULA certification meeting with Oracle's LMS team took place over two sessions. Oracle challenged 14 deployment entries; we had pre-prepared evidence for 13 of them. The 14th — a development cluster in the group's Singapore subsidiary — was removed from the certification register by agreement, at no material cost to the overall licence position. Oracle issued the certification letter within 10 days. Post-ULA licence purchases for products deployed beyond the certified count were negotiated at 40% below Oracle's opening offer, using fiscal quarter timing and benchmark data from comparable Oracle Database deals.

The Results

The group exited the Oracle ULA on schedule, with a clean LMS-issued certification letter and a post-ULA perpetual licence position that accurately reflected their actual Oracle Database deployment. The $4.2M saving was realised against Oracle's renewal offer — the group paid $2.6M for post-ULA top-up licences versus Oracle's proposed $6.8M renewal. Our 40+ Oracle ULA certifications without a single failure remained intact.