Oracle DB license usage data - incorrect

[suvro]

Hi Team,

In the license usage report,

For a specific country it is showing that it is using 16# processor licenses.But this is incorrect, it should be #8. Can you help us out, why as the result (or the calculation of Sam Pro) is incorrect, not trustworthy, because 

• Äccording to Oracle:
4.4 Virtualized servers
Oracle does not recognize virtualization technology and it is not permitted as a means to determine or limit the number of software licenses required for any given server or cluster of servers within your environment. This means that if virtualization technology (like VMware) is used where Oracle software is installed and/or running, all the physical cores within the vCenter need to be counted and licensed. So it is important to note that one Oracle install within the wrong vCenter can have great financial consequences!

When there is a combination between on prem with VMware> whole vCenter needs to be licensed: vcenter cores*processor core factor table .

Oracle's licensing policies for VMware environments require that all physical processors in a cluster be licensed if any Oracle software is running on a virtual machine (VM) within that cluster.
Therefore we are not counting with the vCPUS assigned to vms.
In our case there are 16 cores (2 esx hosts with 8-8 ) with core factor 0.5’’

So it should be 8.

Can someone throw some more light on this one. 

Thanks a lot in advance.

Regards,

Suvro

[Jacques Wiehahn]

Hi Suvro,

This often comes down to how the VMware reconciliation properties are configured in SAM Pro. By default, ServiceNow can either:

• Calculate license consumption per host (which can double-count processors/cores), or

• Roll it up at the vCenter level, which usually aligns better with Oracle’s policy of licensing all physical processors in the cluster.

I’d suggest you check the Software Asset → Properties , especially:

• “Select the level of aggregation for reconciling licenses …” → set this to vCenter(s).

• “Use host affinity … at the vCenter’s aggregation level” → this decides whether the counts remain on each host (Yes) or are aggregated to the vCenter (No).

  

If these aren’t set correctly, SAM Pro can overstate usage (e.g. showing 16 instead of 8). Adjusting these properties and rerunning reconciliation should help bring the results in line with Oracle’s licensing logic.

Best Regards,

Jacques

[suvro]

Hi Jacques,

Currently we have the following values in properties:

It is ESX Cluster instead of Vcenter. Changing it to vCenter will resolve the issue? Please suggest

[Jacques Wiehahn]

Hi Suvro,

Based on your statement:

"Oracle's licensing policies for VMware environments require that all physical processors in a cluster be licensed if any Oracle software is running on a virtual machine (VM) within that cluster. Therefore we are not counting the vCPUs assigned to VMs."

This indicates you’re likely applying the correct level of aggregation. You also mentioned:

"In our case there are 16 cores (2 ESX hosts with 8 each) with core factor 0.5."

Could you confirm whether the core factor of 0.5 aligns with the Processor field value of the ESX servers? If the Processor value is empty, you’ll need to populate it.

Example:

Step:
Navigate to Software Asset > Administration > Refresh Processor Definitions. In my experience, running this refresh populates missing Processor values.

Once the Processor values for your ESX servers are populated, please check the cmdb_processor_definition table. Look for the processor name in the “Processor name condition” field . This will indicate both the Microsoft and Oracle core factor values.

Example:

Thanks,

Jacques

[suvro]

Hi Jacques,

Processor is populated in the ESX server records below is the screenshot. These 2 ESX servers are in a cluster

In cmdb_processor_definition table these are the 2 records. 

 In samp_processor_factor_map

Let me know if you need more details

Thanks,

Chandra Suvro Bose