Licensing glossary
What is hard and soft partitioning in Oracle?
Hard partitioning limits the processors Oracle counts, in a way Oracle accepts. Soft partitioning, such as VMware vSphere, does not, so every core the VM could reach is counted.
How it works
Oracle's Partitioning Policy separates the two. On a soft-partitioned platform Oracle treats the programs as installed and/or running on every processor the VM could be moved to, so every core in the cluster counts, and Oracle has asserted the vCenter or shared-storage boundary in disputes.
Soft: VMware vSphere, Microsoft Hyper-V, and KVM, Nutanix AHV, Proxmox or XenServer without pinning. Hard, when configured as Oracle prescribes: Oracle VM Server and Oracle Linux KVM with hard-pinned vCPUs, capped IBM LPARs, capped Solaris Zones and Fujitsu PPARs. The list is Oracle's, and it changes.
Worked example
One Enterprise Edition VM, three platforms:
- 12-host vSphere cluster, two-socket 32-core Xeon hosts
- 768 cores × 0.5 = 384 licenses
- Dedicated two-host vSphere cluster
- 64 cores × 0.5 = 32 licenses
- Oracle Linux KVM, four pinned cores
- 2 licenses
Every option the database uses is counted on the same boundary.
What to watch
- Joining an isolated Oracle cluster to a larger one, or enabling cross-cluster vMotion. Either multiplies the position without installing anything.
- Pinning done your own way. It has to follow Oracle's documentation, with the tools Oracle names, and be auditable after the fact.
- Shared vCenter and storage. To be safe against the wider readings, keep the Oracle cluster apart from both.
- Cluster changes without change control. Membership of Oracle hosts should not move for convenience.