The Challenge
A tier-2 insurance group operating across four European markets ran Oracle E-Business Suite 12.2 as its core Finance, HR, and Procurement platform. Annual Oracle Premier Support cost: $5.1M — covering EBS, Oracle Database EE, and Oracle WebLogic. The company had operated on EBS 12.2 for seven years with deep functional customisations and no strategic plans to migrate to Oracle Fusion Cloud. Their core regulatory environment — Solvency II, IFRS 17 — was stable, and their audit history with Oracle was clean.
The last Oracle-issued patch the company had applied was 18 months prior — a patch required to fix a regression Oracle itself had introduced in a previous update, not a security fix relevant to the company's specific infrastructure. Oracle's renewal team had twice positioned potential Oracle Diagnostics Pack usage as a compliance concern — implying that without Premier Support, the company could not access Oracle's assistance in a compliance review. This was misleading on two counts. First, Oracle audit assistance is not a feature of Premier Support — Oracle's LMS audit process operates independently of whether you have active support. Second, the company's compliance posture was clean and its Database instances were not running Diagnostics Pack or Tuning Pack without licence.
When the third annual support renewal arrived at 22% of net licence value — Oracle's standard annual rate — the insurance group's CFO authorised an independent review of whether Premier Support was still justified.
Our Approach
-
Contract and Entitlement Review
The first step in any third-party support migration is to confirm that Oracle licences are perpetual and that no contractual clause ties licence validity to active Premier Support. We reviewed the insurance group's Oracle Master Agreement, Order Forms, and Support Schedule across all three CSI numbers. All Oracle licences were perpetual. No contractual term linked licence validity to support status. The support contracts were term-based with annual renewal — there was no long-term support commitment, and cancellation required standard notice under the Support Schedule terms.
-
Audit Risk Assessment
Oracle audits examine what products are installed, what features are being used, and how licences are counted — not whether Premier Support is active. Third-party support does not affect audit risk. What affects audit risk is the licence position and deployment configuration. We confirmed the insurance group's Oracle licence position was clean: EBS, Database EE, and WebLogic were correctly licensed with no feature usage gaps. Their audit exposure was low by any metric. With a clean licence position documented, the residual risk of third-party support migration was minimal.
-
Third-Party Support Provider Evaluation
We evaluated three third-party Oracle support providers against criteria specific to insurance sector requirements: response SLA (24/7 P1 coverage), regulatory compliance support capability (Solvency II, IFRS 17 reporting integrity), patch currency for Oracle EBS 12.2, and commercial terms over a three-year engagement. The evaluation process included SLA simulation — we presented each provider with a representative set of the insurance group's historical support tickets to assess response quality. Final provider selection was based on technical capability and commercial terms independently negotiated.
-
Oracle Support Cancellation
Oracle's support cancellation process is governed by the Support Schedule terms and requires formal written notice with a specific cancellation effective date. Oracle's renewal team made two further contact attempts after the cancellation notice was submitted — one with a revised pricing offer (a 15% discount on Premier Support) and one with a veiled reference to the company's "compliance situation." We managed both contacts on behalf of the client. The Premier Support contract terminated on the contracted date. No concession was made.
-
Licence Position Documentation
Post-transition, we produced a comprehensive Oracle licence position document covering all products across all three CSI numbers: entitlement quantities, deployment configurations, Core Factor Table calculations for Processor metric products, and DBA_FEATURE_USAGE_STATISTICS analysis confirming no unlicensed Database Options usage. This document is the insurance group's primary audit defence asset — it demonstrates, without Oracle's involvement, that the organisation's licence position is clean, known, and defensible.
The Results
Key Takeaways
- Third-party Oracle support does not affect Oracle audit risk — audits examine licence position, not support status
- Oracle Premier Support is only necessary if you're actively consuming patches that improve your risk posture
- Oracle's renewal teams routinely misrepresent what third-party support means for licence compliance — get independent advice
- Perpetual Oracle licences remain valid regardless of support status — verify the contractual position before any transition
- Third-party support providers are commercially negotiable — published rates are a starting point, not a final offer
"Oracle's renewal team told us three times that switching to third-party support would expose us in a compliance review. None of it was accurate. We saved $1.1M in the first year and our compliance position is better documented now than when we were paying Oracle full support."— CFO, Tier-2 Insurance Group