1. Count all physical cores.
2. Multiply total physical cores by Core Factor. Round up if needed.

1. Identify physical servers that support Oracle workloads. This may be either a standalone physical host that VMs with Oracle may be limited to, or clusters of physical hosts within which VMs may VMotion, or VCenters where such VMs may VMotion across clusters/hosts.
2. Based on the above, determine if host-level, cluster-level, or VCenter level licensing will be applied.
3. For the appropriate level, identify total physical hosts across which the VMs with Oracle programs reside. Count all physical cores across all CPUs on the hosts.
4. Multiply total physical cores by Core Factor. Round up if needed.

Note: The above methodology ignores Oracle’s policy on licensing in virtual environments (Server Partitioning (oracle.com)) and instead relies on contractual definitions only.

1. Identify virtual and physical servers that support Oracle workloads and the VM-to-CPU mapping or pinning between the VMs and cores on the physical hosts. Depending on the type of virtualization, count cores on physical hosts based on directions in the following documents:
   – Linux KVM: Hard Partitioning with Oracle Linux KVM
   – OVM x86: Hard Partitioning with Oracle VM Server for x86
   – OVM SPARC: Hard Partitioning with Oracle VM Server for SPARC
   The documentation above also provides instructions on how VMs can be pinned to specific cores to reduce or limit the license requirement.
2. Based on the above, identify physical cores running Oracle programs.
3. Multiply total physical cores by Core Factor. Round up if needed.

1. Identify all LPARs with Oracle programs.
2. Analyze LPARs current and maximum allowed cores. This is typically done using the lparstat command and inspecting the mode to see if it’s capped or uncapped.
3. For capped LPARs, count the capped core count. For uncapped LPARs, count the maximum cores the LPAR may access. Also ensure that the total core count for each Oracle product does not exceed the maximum core pool size.
4. Based on the above, identify physical cores running Oracle programs.
5. Multiply total physical cores by Core Factor. Round up if needed.

1. For OCI Compute and DBCS, count the number of OCPUs in the respective VMs or, in the case of bare metal, the total number OCPUs in the system.
2. For OCI VMware Cloud Solution (OVCS), count total OCPUs for the configured hosts in the VMware SDDC.
3. Multiply total physical cores by Core Factor. Round up if needed. The Core Factor for OCI is defined in the Processor Core Factor table referenced above.

1. For compute services (EC2, etc.), count the number of vCPUs in the VMs or in the physical host, in the case of bare metal systems.
2. For VMware Cloud Solutions across the different cloud vendors, one of two approaches can be taken depending on your interpretation of the Oracle contract, and whether you decide to apply Oracle’s licensing policy in third-party clouds:
   – If you apply Oracle’s policy document: Count total vCPUs in the VMware clusters and (if the systems are hyper-threaded), count 1 Processor license for each vCPU. Round up if needed.
   – If you ignore Oracle’s policy document: Count total physical cores in the VMware clusters and apply the appropriate Core Factor for the CPU type. Round up if needed.