Canada Life optimized the Oracle Database through Oracle licensing assessment, Oracle Database licensing optimization, and the Oracle support optimization.
How to Negotiate an Oracle ULA: No Price List, Just Your Business Case
There is no price list: the ULA fee is a story built from your estate and your growth. Give conservative growth answers, keep the product list narrow, model the breakeven yourself, and negotiate the certification exit before you sign.
Canada Life is one of the largest Canadian insurance and wealth management groups, with roughly twelve thousand employees across Canada, the United Kingdom and Ireland. Its Oracle estate covers Database Enterprise Edition, Real Application Clusters and the Diagnostics Pack.
A group operating across three jurisdictions has a licensing problem most single country businesses never meet. Entities acquire software separately, entitlement sits in different agreements, and nobody holds the consolidated picture.
The assessment rebuilt that picture and optimised the position across the estate.
Twelve thousand employees across three countries, in a sector where regulatory obligations shape the architecture as much as commercial ones do.
Insurance workloads drive Real Application Clusters harder than most. Policy administration and claims systems are availability critical, so the high availability tier is real rather than aspirational, and RAC is licensed per processor on top of the database.
The multi jurisdiction structure also means data residency requirements differ by entity, which shapes where capacity sits and therefore what gets licensed where.
Oracle's position priced the estate at its provisioned capacity, with options carried across the full processor count and support renewed on the accumulated history.
Because entitlement was spread across agreements held by different entities, there was no single consolidated counter position to test it against.
Three strands, run in parallel across the three jurisdictions.
Processor counting first, on the correct basis of physical cores multiplied by the core factor for each processor family. Estates that grew by entity frequently have this inconsistent between sites.
Options second. Which instances genuinely used Real Application Clusters and the Diagnostics Pack, and which had them enabled because a default or a tool switched them on.
Entity scope third. Which agreement covers which legal entity, and whether entitlement bought by one part of the group can be used by another. In a multi jurisdiction insurer that question is worth asking carefully.
For any group operating across jurisdictions, the consolidated entitlement picture is the artefact worth building. Without it you cannot tell whether you are buying something you already own.
The eleven moves, processor counting on the correct core basis, auditing enabled options, support alignment, and the buyer side position at every step of an Oracle renewal.
Used across more than five hundred enterprise clients. Independent. Buyer side.
Oracle framed the Oracle Database as the immediate Oracle uplift at the renewal cycle. Redress reframed the approach around Canada Life's actual Oracle Database utilization. Material commercial saving against the publisher's opening Oracle Database renewal quote.
Independent. Buyer side. The advisory firm enterprise software vendors do not want you to hire.
Oracle Database licensing signals, Oracle support signals, Oracle ULA signals, and the broader Oracle licensing leverage signals across the practice.