Licensing Oracle on Amazon EC2 and RDS – previous VS. current version

09 feb '17 - : Adrian Cristache & Andra Tarata - share: LinkedIN Mail
licensing-oracle-amazon-ec2-and-rds-previous-vs-current-version

The news on everyone in the licensing management industry’s lips in the last weeks was the big change of Oracle licensing policies for the so called “Authorized Cloud Environments”.

Even though Oracle initially stated that for the “Authorized Cloud Environments” end users would need to consider each virtual core as a physical core to determine the number of “Processors” that were required to be licensed, this changed since 23 of January 2017.

Until January 23rd, 2017, end users were required to count each virtual core as a physical core, in case the Oracle programs were deployed on Amazon EC2, Amazon RDS and/or Microsoft Azure. This number of cores would then need to be multiplied with the applicable core factor as per Oracle’s Processor Core Factor Table, to determine the required number of licenses. This policy applied to all Oracle programs available on a Processor metric.

Under the new policy, the following counting methodologies are applicable for Amazon EC2, Amazon RDS and Microsoft Azure.

Amazon EC2 and RDS:

  • If hyper-threading is enabled:
    • end users are required to count two vCPUs = one Oracle Processor license
  • If hyper-threading is NOT enabled:
    • end users are required to count one vCPU = one Oracle Processor license

 

Microsoft Azure:

  • End users are required to count one Azure CPU Core = one Oracle Processor license.

 

Under the old policy, the methodology applied to all Oracle programs available on a Processor metric. Under the new policy, the methodology is only applicable to a subset of Oracle’s programs which can be found here.

Read our latest white paper “Licensing Oracle on Amazon EC2 and RDS – Twice as expensive since last week!” to find out how to count the required number of licenses in Amazon EC2, Amazon RDS and Microsoft Azure cloud environments and how to differentiate between virtual cores, vCPUs, physical cores and more.

Our new white paper format is really mobile friendly, so you can easily read it on your tablet or mobile phone. 

Download Our Free White Paper: 
Licensing Oracle on Amazon EC2, RDS and Microsoft Azure - now twice as expensive!

Self Audit for Compliance with Zyncc

Ongoing license control is difficult to achieve, but periodic self audits can help you stay in control, remain compliant, and stay one step ahead of software publishers. Conducting these audits requires sound understanding of common mistakes and where to look for them. This can be especially challenging in a continually changing environment with new products and versions of products being deployed.

Self Audit for Compliance with Zyncc

Download

Fill out this form to download our free whitepaper

Please make sure you've filled out the form correctly.