A wise db admin once told me Oracle's current licensing strategy is set up in such a way to be cumbersome towards any other virtualization platform other than it's own.
Apologies about the bias in the title, its not biases if your visualization centric - it is if your a weblogic (oracle) fanboy
Lets start with the facts:
Every Oracle customer shares a common challenge how to avoid over- or under-licensing.
In a recent survey, 53 percent of enterprises indicated that a portion of software license spend is associated with applications that are overused and therefore out of compliance.1 At the same time, a large percentage of organizations also overspend – owning Oracle licenses that are not used or not deployed for maximum benefit.
Now knowing that we are faced with the tedious implication of licensing the actual application, to maximize their 'compliance' we have to manage and almost require an entire team dedicated to licensing.
Any Oracle licensing strategy is a complex calculation based on current and projected usage. It’s not enough to count database server CPUs, the number of users, or even installations. While these metrics are important, especially for processor-core based agreements, Oracle requires detailed accounts of what is being used – which includes editions, versions, and any options and management packs. The burden is on the organization to keep licenses aligned with actual usage.
Actual usage can often vary dramatically from the projections used when entering into an Oracle contract – particularly for growing companies. Oracle provides assistance in making usage calculations, including scripts for tracking software usage. However, the onus is on the company to maintain license compliance, and many organizations simply do not have the processes or infrastructure in place to meet the reporting requirements of Oracle contracts – so they are at high-risk of expensive over-utilization adjustments in the event of an Oracle license assessment or audit.
While usage tracking is central to managing audit risk, tracking can also address under-utilization – finding Oracle licenses that could be redeployed for maximum usage. This frequently happens when organizations buy and install large quantities of Oracle database Options, but never actually deploy these Options. The process to determine Option utilization is much more complex than simply confirming installations. The process requires detailed analysis of each individual database Option through SQL queries and applying the appropriate business rules.
Knowing this is good and all, but how do you apply it?