Many customers are familiar with Oracle’s infamous VMware policy which dictates that all physicalESXi hosts where Oracle programs could potentially run via VMware technology (vMotion, DRS, High Availability, etc.) be licensed, regardless of where Oracle is actually running at any point in time.
All too often, customers have learned this policy the hard way – through an audit. But “passing” an audit in the past does not guarantee that you are compliant today, even if your Oracle usage and entitlement has not changed. As VMware technology has improved, Oracle’s licensing position has consequently created more potential compliance exposure for customers. This is because, while older versions of VMware allowed virtual machines to migrate between hosts within a cluster, newer versions of VMware allow for the migration of virtual machines between clusters, data centers, and even vCenter instances. This can greatly increase the number of machines that require licensing. In this way, a customer that has done nothing more than upgrade to a newer ESXi version can create a sizable compliance violation that may be exposed during an audit.