How Redress Compliance helped a southern European bank reduce an €8 million Oracle audit claim to just €300,000. A 96% reduction. By identifying critical errors in Oracle's findings and executing a targeted negotiation strategy that settled the matter in four months.
Oracle audited a southern European bank running Oracle Database in a complex infrastructure environment. The bank initially attempted to navigate the audit process independently. A common but frequently costly mistake when facing Oracle's License Management Services (LMS) scripts and audit methodology.
After Oracle issued an audit report worth €8 million, the bank's leadership recognised the severity of the situation and enlisted Redress Compliance to help minimise the impact and negotiate the best possible outcome. The licence compliance issues identified by Oracle ranged from virtual environment licensing disputes to unlicensed database options usage. Two of the most common and most frequently inflated findings in Oracle audits.
Oracle's LMS team is not an impartial assessor. Their audit reports are designed to maximise revenue for Oracle, not to accurately reflect your compliance position. In our experience, the majority of Oracle audit reports contain errors, incorrect assumptions, or inflated calculations. Particularly around virtualisation rules and database options. An independent expert review almost always identifies material reductions.
The bank faced an €8 million non-compliance claim from Oracle's LMS team. A potentially devastating financial hit for any organisation, particularly one that believed it was broadly compliant with its Oracle licence agreements.
| Challenge | Detail |
|---|---|
| €8M Audit Claim | Oracle's LMS team issued an audit report asserting €8 million in non-compliance, covering multiple Oracle Database products, options, and infrastructure configurations across the bank's environment. |
| Virtual Environment Disputes | Oracle applied its restrictive soft partitioning policy to the bank's virtualised infrastructure, potentially requiring the bank to licence all physical cores across entire clusters. Far exceeding actual Oracle usage. |
| Unlicensed Database Options | The audit flagged usage of Oracle Database options and management packs (such as Diagnostics Pack, Tuning Pack, or Partitioning) that may have been inadvertently enabled but not actively used. A common Oracle audit tactic. |
| No Independent Expertise | The bank had attempted to handle the audit independently, without the specialised Oracle licensing knowledge needed to challenge Oracle's findings, identify errors, or develop a counter-strategy. |
Oracle's position on virtual environments is one of the most contentious areas in enterprise software licensing. Oracle does not recognise VMware, Hyper-V, or other soft partitioning technologies as valid licence-limiting mechanisms. They may claim you need to licence every physical core in a cluster where Oracle software could theoretically run. This single issue frequently inflates audit claims by millions.
Redress Compliance was engaged after the audit report had already been issued. A late-stage intervention, but one where our experience in deconstructing Oracle audit findings delivers the greatest impact.
Redress conducted a comprehensive, line-by-line review of Oracle's audit report. Examining every finding, every calculation, and every assumption. We cross-referenced Oracle's claims against the bank's actual licence entitlements, ordering documents, and contractual terms to build an accurate picture of the true compliance position.
Redress identified significant errors and incorrect assumptions on Oracle's part. These included misapplied virtualisation rules, inflated processor core counts, database options flagged as in use that were merely installed but never actively utilised, and licensing calculations that did not reflect the bank's actual contractual entitlements. Each error was documented with evidence to support the bank's counter-position.
Redress developed a structured negotiation strategy designed to challenge Oracle's findings systematically and enable the bank to pay as little as possible. The strategy addressed each audit finding individually, prioritised the highest-value errors for challenge, and established a target settlement range based on the bank's actual compliance exposure versus Oracle's inflated claims.
Redress guided the bank through a focused negotiation process with Oracle's LMS team. Presenting the documented errors. Challenging Oracle's methodology. And applying commercial pressure to reach a fair settlement. The negotiation was resolved within four months of the original audit report.
Oracle's LMS reports frequently contain inflatable findings. Areas where Oracle makes assumptions in their favour that do not reflect the customer's contractual reality. The most common errors include counting all physical cores in a virtualised cluster when Oracle only runs on a subset, flagging database options as in use based on cumulative feature-usage views (which record any past activation, even momentary or accidental), misapplying processor core factors, and not accounting for existing licence entitlements that offset deployments.
The audit was settled at €300,000. A €7.7 million reduction from Oracle's initial €8 million claim. This outcome was achieved by systematically dismantling Oracle's audit findings through expert analysis, identifying multiple material errors in Oracle's calculations and assumptions, and executing a disciplined negotiation strategy that kept the bank in control of the process throughout.
| Metric | Oracle's Claim | Actual Position |
|---|---|---|
| Total Non-Compliance Claim | €8,000,000 | €300,000 |
| Virtual Environment Findings | Inflated: all physical cores counted | Errors identified, scope corrected |
| Database Options Findings | Multiple options flagged as in use | Installed but not actively used: challenged |
| Savings Achieved | €7,700,000 (96% reduction) |
The settlement not only delivered immediate financial savings of €7.7 million but also established a stronger compliance posture for the bank going forward. With clearer documentation of its licensing position and improved processes for managing Oracle deployments in virtualised environments.
"The strategic insights and deep expertise of Redress Compliance have been instrumental in our Oracle audit process. Their comprehensive approach and unwavering support were key in navigating the complexities of the audit. They identified errors and wrong assumptions on behalf of Oracle and provided a negotiation strategy that resulted in a significant cost reduction. Their contribution has been pivotal in our IT strategy and has saved us millions." — Director of IT, Southern European Bank
Oracle's LMS reports are not objective compliance assessments. They are commercial documents designed to maximise Oracle's settlement. In this case, 96% of Oracle's claim was eliminated through expert review. Always engage independent analysis before responding.
Oracle's soft partitioning policy is one of the most contested areas in enterprise licensing. Oracle will attempt to licence every physical core in a cluster where an Oracle VM could theoretically run. Challenge these findings with architectural evidence and contractual analysis.
Oracle's audit scripts record cumulative feature-usage data. A database option that was briefly or accidentally enabled years ago will still appear as in use. This is one of the most common inflated findings in Oracle audits and should always be challenged with evidence of actual usage patterns.
This bank initially handled the audit independently and faced an €8M claim. After engaging Redress, the claim was reduced to €300K. The complexity of Oracle's licensing rules, particularly around virtualisation, processor metrics, and database licensing models, requires specialist expertise to defend effectively.
Oracle's audit teams operate on internal timelines and revenue targets. A well-prepared defence that slows the process and forces Oracle to justify every finding puts the customer in a stronger position. This engagement was settled in four months. Fast, but on the bank's terms.
Extremely common. In our experience across hundreds of Oracle audit engagements, the majority of Oracle LMS reports contain material errors, incorrect assumptions, or inflated calculations. Reductions of 50 to 90 percent or more are achievable when findings are challenged with independent expertise. Oracle's LMS team is incentivised to maximise the claim, not to reflect the customer's actual compliance position.
The most frequent errors include counting all physical cores in a virtualised cluster when Oracle only runs on a subset, flagging database options as in use based on cumulative feature-usage views that record any past activation including momentary or accidental, misapplying processor core factors for specific hardware, and not accounting for existing licence entitlements that offset deployments.
No. While earlier engagement is always better, post-report intervention is where independent advisors often deliver the greatest financial impact. The audit report is not a final bill. It is a negotiation starting point. An experienced advisor can identify errors, build a counter-position, and negotiate a significantly lower settlement. This case study demonstrates exactly this scenario. The bank engaged Redress after the report was issued and achieved a 96% reduction.
Oracle's licensing policy does not recognise soft partitioning technologies such as VMware, Hyper-V, or KVM as valid licence-limiting mechanisms. Oracle's position is that you must licence all physical cores in a cluster where Oracle software could theoretically run, even if Oracle only actively runs on a small subset of those cores. This policy interpretation can inflate a finding from tens of thousands to millions. It is the single largest driver of inflated Oracle audit claims.
Redress operates on a fixed-fee basis. No hourly rates, no percentage of savings. The fixed fee is agreed upfront based on the scope and complexity of the engagement. In this case, the advisory fee was a small fraction of the €7.7 million in savings delivered. Contact us for a confidential discussion of your situation and a fixed-fee proposal.
Resolution timelines vary depending on complexity, but most engagements are resolved within 3 to 6 months from the point of our engagement. This case was settled in 4 months from the original audit report. The key factors affecting timeline are the number of findings, the quality of the customer's existing documentation, and Oracle's willingness to engage constructively once errors are identified.
Oracle LMS audit reports are designed to maximise Oracle revenue, not to reflect your true compliance position. Our team of former Oracle auditors consistently identifies material errors, inflated calculations, and incorrect assumptions.