Client Profile
The client is a professional services group headquartered in Frankfurt, providing management advisory, technology implementation, and regulatory consulting services to corporate clients across the financial services, automotive, and manufacturing sectors. The organisation employs approximately 8,500 staff across offices in Germany, the Netherlands, France, Switzerland, Poland, and the United Kingdom. Its Oracle estate was originally deployed to support a centralised ERP platform and business intelligence function, with Oracle Database Enterprise Edition serving as the data layer for a core SAP landscape that the group had migrated to over the preceding five years.
The Oracle Unlimited License Agreement had been entered during the initial deployment phase, when the organisation's Oracle Database usage was growing rapidly alongside the SAP implementation. At the time of engagement with Redress Compliance, the ULA was in its final year and Oracle Database deployment had largely stabilised. The organisation had no plans to expand its Oracle footprint and was actively evaluating cloud-native analytics platforms that would reduce its Oracle Database dependency for new workloads over the following two years.
The Challenge
Oracle's account team had been engaged with the organisation's technology procurement function for more than twelve months, presenting a ULA renewal as the safest and most cost-effective path forward. The renewal proposal was structured around an Oracle estimate of 220 processor licences across the estate, producing an annual support obligation at renewal of approximately €3.2M per year — effectively an €800,000 increase over the current year's support cost, compounded by an additional ULA licence fee of approximately €2.5M for the new term.
The organisation's technology leadership had two concerns with Oracle's position. First, the 220-processor estimate had been produced by Oracle's own assessment team without access to the full configuration details of the group's virtualised server environment, and the IT team believed it overstated the actual deployment count. Second, the organisation's strategic direction was away from Oracle, and committing to a new three-year unlimited licence would lock in a level of Oracle dependency that the technology roadmap was designed to reduce.
A further complication was the group's EMEA-wide footprint. Oracle's estimate appeared to include processor licences for Oracle Database instances running in the Netherlands and Poland offices, where local IT teams had deployed Oracle for development and testing purposes under what they believed were development-only licences — not production deployment entitlements. The correct categorisation of these instances was a significant factor in the processor count and had not been independently resolved.
The Approach
Redress Compliance conducted a six-country deployment survey over a seven-week period, working with local IT leads in each jurisdiction to capture Oracle Database configurations, virtualisation settings, and usage profiles. The survey covered 28 server environments across the EMEA footprint and produced a comprehensive processor count with full documentation for each deployment.
Key findings from the survey included three significant areas of divergence from Oracle's estimate. First, the Netherlands and Poland development instances were correctly categorised as development and testing deployments that did not qualify as production processor licences under the ULA product schedule — removing 24 processors from the certifiable count. Second, a production Oracle Database cluster in the Frankfurt primary data centre was running on VMware with CPU affinity settings that constituted legitimate hard partitioning under Oracle's published policy, allowing the organisation to count only the assigned virtual CPUs rather than all physical cores in the cluster — removing a further 22 processors. Third, an Oracle Data Guard standby configuration in the Swiss office had been counted by Oracle as a separate licensed deployment, but met the conditions for Oracle's Data Guard active standby licence exclusion, removing an additional 6 processors from the count.
The certified processor count submitted to Oracle was 172 processors — 48 fewer than Oracle's estimate of 220, a reduction of approximately 22%. Redress prepared the certification letter and the full supporting technical documentation package, addressing each area of divergence with specific contractual and configuration-level evidence. The certification was submitted to Oracle's GLAS team with a simultaneous termination notice for the ULA, formally initiating the exit process.
The Outcome
Oracle accepted the certification at 172 processors after a two-week review period, during which the GLAS team requested clarification on the Dutch and Polish development instance categorisation. The supporting documentation from Redress addressed the query fully and Oracle proceeded without further challenge. The ULA exit was completed cleanly, with perpetual Oracle Database Enterprise Edition licences granted for the certified 172-processor count.
The post-certification annual Oracle support obligation was €1.4M — a reduction of €1.8M against Oracle's renewal proposal rate of €3.2M per year. Added to the avoided ULA renewal licence fee of €2.5M, the total saving against Oracle's proposed renewal was €4.5M over the equivalent three-year period. The organisation also gained what its CTO described as "genuine compliance clarity for the first time since we entered the ULA" — a defined, documented perpetual licence position that removed the ambiguity inherent in the unlimited licence structure.
Key Takeaways
- Development and testing deployments are frequently miscounted. Oracle's pre-certification assessments often include development and testing instances as production processor licences. Where the ULA product schedule excludes non-production environments, each miscounted instance represents a meaningful reduction in the certifiable count.
- Multi-country Oracle estates require local engagement. Configuration details that affect the processor count — hard partitioning settings, development licence status, Data Guard exclusions — are held by local IT teams and are rarely visible in centralised summaries. A physically present audit consistently produces better results than a remote assessment.
- Data Guard standby licences are frequently over-counted. Oracle's active standby exclusion is a standard feature of Oracle Database licensing that is routinely missed in pre-certification assessments. Identifying and applying it correctly is one of the most reliable sources of legitimate count reduction.
- A clean exit from an Oracle ULA is almost always possible. The perception that Oracle ULAs are too complex to certify and exit without Oracle's involvement is a commercial narrative. Independent certification with proper documentation consistently produces accepted certifications.
- Exiting a ULA changes the negotiating dynamic with Oracle permanently. An organisation with a defined perpetual licence base negotiates Oracle cloud services, incremental licences, and support arrangements from a position of defined entitlement rather than open-ended obligation.
Oracle ULA approaching expiry? Independent certification advisory starts here.
Redress Compliance conducts independent pre-certification deployment audits for EMEA Oracle estates of all sizes.