Problem
Oracle VMs needed clearer infrastructure boundaries so licensing scope did not extend unnecessarily across general-purpose VMware ESXi hosts.
Reduced Oracle Licensing Costs on VMware Clusters
Oracle workloads running across broad VMware clusters can increase licensing exposure when placement is not tightly controlled. I reduced that exposure by segregating ESXi hosts dedicated to Oracle VMs into a separate cluster and applying host affinity rules so Oracle workloads stayed on approved capacity.
Action
Segregated Oracle-capable ESXi hosts into a dedicated VMware cluster and added host affinity rules to keep Oracle VMs on the intended hosts.
Impact
Reduced Oracle licensing cost exposure, improved audit readiness, and gave infrastructure teams clearer control over where Oracle workloads could run.
- Separated Oracle VMs from general-purpose VMware clusters
- Controlled placement with ESXi host affinity rules
- Reduced unnecessary licensing scope and cost exposure
- Improved governance for virtualized database workloads