Virtualization and licensing: the trap that makes you pay for CPUs you do not use
You virtualized to spend less and, without meaning to, multiplied your licensing bill.
Virtualization should save you money. With Oracle, misconfigured, it does the opposite. Oracle tends to hold that if a database can move across an entire cluster, you have to license every core in the cluster, even if the database only uses one. That is the trap, and also the way out.
01 Oracle counts cores by where the database "could" run
On flexible virtualization platforms, Oracle argues you must license every host the virtual machine could migrate to. Not where it runs: where it could run.
02 A large cluster multiplies the bill
If you have a 6-host cluster and your database lives on one, Oracle may demand licenses for all 6. The bill sextuples over an infrastructure decision.
up to 6x the expected license
03 Isolating the workload is the defense
Setting up dedicated clusters, strict affinity or Oracle-recognized hard partitioning limits how many cores you have to license.
04 Documentation saves you or sinks you
In an audit, your configuration has to prove the database cannot migrate freely. Without evidence, the auditor wins the argument.
// A typical case
Imagine a cluster of 4 hosts with 8 cores each, running an Oracle database on just one. Without isolation, Oracle demands licensing for all 32 cores: 16 processors x USD $47,500 = USD $760,000. With a dedicated single-host cluster, you license 4 processors: USD $190,000. That is a difference of more than half a million dollars based on how the virtualization is put together.
Illustrative example with typical market figures, not a specific client.
// next step
Reviewing your virtualization architecture before an audit avoids bills of this size. At dba.mx we run that scan at a fixed price with a firm cap, so you know where you are exposed.