How an Oracle audit can cost millions (and how to protect yourself)
Oracle has the right to audit you, and it knows exactly where people tend to slip up.
Most Oracle contracts include the right to audit your usage. When the audit comes, they do not review what you bought: they review what you used. That is where the expensive surprises show up, almost always from options switched on by accident or virtualization that was misunderstood.
01 Options turn themselves on
Partitioning, Advanced Compression or Diagnostics Pack can end up active by default or with a single click. Each one is an extra per-core license that Oracle will bill you for retroactively.
02 Virtualization is the auditor's favorite ground
Oracle often argues you must license every core in the virtualization cluster, not just where the database runs. That is where a small bill turns into a huge one.
03 The cost is not just the license: it is the back interest of time
If you have been using something unlicensed for three years, they bill you for three years of support too. The hole gets deeper the longer it goes undetected.
up to 100% of list price in penalties
04 Protecting yourself means auditing yourself first
An honest internal inventory, done before Oracle arrives, gives you time to turn off options, rebalance workloads and negotiate from a position of strength.
// A typical case
Imagine a company with 10 licensed cores that, without realizing it, had Partitioning active in production. In an audit, that is 10 additional cores at USD $11,500 per core for the option, plus three years of accumulated support. The tab runs around USD $190,000 for something nobody chose to use on purpose.
Illustrative example with typical market figures, not a specific client.
// next step
The best defense is a self-assessment before anyone audits you. At dba.mx we run that compliance scan at a fixed price, so you know where you stand before someone else finds out for you.