The management of Oracle license terms is a much more complex process than most businesses may think. These include very specific guidelines regarding the calculation of processor numbers, virtualization, cloud computing usage, and more, which could make a big difference in terms of cost and compliance.
Being unaware of all these nuances, companies can find themselves in situations where there are gaps in the licensing policy or unexpected costs associated with Oracle software usage or even fines after the audit.
Infrastructure changes, moving to the cloud, or just upgrading your systems may involve licensing issues that the average IT or purchasing department is not aware of.
Most enterprise software licensing is relatively straightforward to model. A per-user licence means the cost scales with the number of users. A per-server licence means the cost scales with the number of servers. The licence metric is defined, the unit cost is published, and the total cost is calculable by anyone who understands basic multiplication.
The metrics that govern Oracle licensing are specified in such a way that they do not align with common sense in terms of the definition of licensing items, and the application of these metrics to actual infrastructure leads to some counterintuitive results that have become well-known within the IT community.
The processor licence metric, for example, applies a core factor table that varies by processor type, and that means the licence cost for the same number of processor cores differs depending on which processor type those cores are implemented on.
The situation becomes even more complicated in a virtualized environment where the set of rules for covering certain physical processors with Oracle licences depends on the type of virtualization technology used. Moreover, the technology that is used most often requires licensing all physical processors regardless of the proportion of the cluster capacity running the Oracle software.
The compliance risk in the Oracle environment tends to cluster around the interaction of the business’s infrastructure planning and Oracle licensing in a way that the business team did not expect when making such infrastructure plans.
A server consolidation project that moves Oracle workloads onto a larger physical host may increase the Oracle licence requirement even if the number of Oracle instances deployed remains constant, because the licence obligation is based on the physical processor capacity of the host, not the capacity allocated to Oracle workloads. A cloud migration that moves Oracle workloads onto a cloud provider whose processor types attract a higher core factor than the on-premises processors being replaced may produce a higher Oracle licence cost in the cloud environment despite running on less physical capacity.
This is why Oracle consulting services that include a licensing review before infrastructure decision-making identify such risks in advance, before Oracle audits reveal them to become risks.
Oracle audits are a mechanism through which Oracle verifies that customers’ deployed usage matches their licensed entitlements, and the frequency and targeting of Oracle audit activity reflects Oracle’s commercial interest in identifying and recovering revenue from under-licensed deployments. A company that has been keeping its Oracle licences up to date according to its own assessment of the licensing status has been keeping them incorrectly without even knowing it in some way, and the result of the audit reveals this gap and leads to a back-licence bill reflecting the whole period of under-licensing.
The specialist knowledge required to maintain an accurate Oracle licence position isn’t primarily knowledge of Oracle’s products. It’s knowledge of Oracle’s licensing rules, which are documented in licensing policies that are detailed, updated periodically, and interpreted in ways that Oracle’s audit team applies consistently and that customers encounter for the first time at audit. An organisation whose Oracle licence position is maintained by someone with that specialist knowledge is in a materially different compliance position from one whose Oracle licensing is managed by people with general IT procurement competence but without Oracle-specific licensing depth.
The licensing process for Oracle is a much more complicated one compared to other enterprise software licensing processes, and this makes it easy for companies to overlook any potential expensive compliance issues.
The use of processors, virtualization, cloud migration, and changing licensing policies, among others, can affect the cost of the software licensing and the audit results. It is advisable to consult an expert before making any infrastructure decisions to save on costs and ensure compliance.
Ans: The thing is that Oracle licensing involves specific metrics such as the number of cores and the use of virtualization technologies, which can have a huge impact on costs of licensing.
Ans: The cost of Oracle licensing can vary greatly depending on such factors as cloud vendor, the type of processors, and the deployment approach.
Ans: The main one is the risk of uncovering under-licensing and having to pay for past violations.
Ans: Some virtualization technologies demand licensing of all physical processors in the cluster despite the fact that Oracle software uses a smaller share of hardware resources.
