Oracle BYOL – How to Use Existing Licenses in cloud

Oracle BYOL (Bring Your Own License):

• Flexibility: Use existing licenses in the cloud.
• Cost Savings: Leverage current Oracle investments.
• Cloud Compatibility: OCI, Azure, AWS.
• Inventory Management: Maintain accurate license records.

Oracle BYOL – How to Use Existing Licenses in Cloud

Oracle’s Bring Your License (BYOL) program allows customers to leverage existing Oracle licenses in cloud environments, including Oracle Cloud Infrastructure (OCI) and third-party public clouds like AWS, Microsoft Azure, and Google Cloud Platform (GCP).

While BYOL offers significant cost benefits and flexibility, navigating the licensing rules, compliance requirements, and nuances across cloud providers can be challenging.

This article explains how Oracle BYOL works, outlines best practices for using your existing Oracle licenses in OCI and major public cloud providers, and discusses compliance risks to avoid.

Understanding Oracle BYOL Licensing

What is Oracle BYOL?

Oracle BYOL permits customers to deploy their pre-existing on-premise Oracle licenses to cloud infrastructure, reducing licensing costs and maximizing the return on existing investments. Key points include:

• License Portability:
  Customers use previously purchased licenses rather than new ones from cloud providers or Oracle.
• Reduced Costs:
  Eliminates the need to procure additional cloud-specific Oracle licenses, significantly reducing the total cost of ownership.
• Flexibility and Control:
  Provides the freedom to choose cloud providers based on business and technical needs rather than license availability.

Which Oracle Licenses Qualify for BYOL?

Most Oracle licenses, especially perpetual licenses, are eligible for BYOL, including:

• Oracle Database (Enterprise, Standard Editions)
• Oracle Middleware Products (WebLogic, SOA Suite, etc.)
• Oracle Applications (E-Business Suite, JD Edwards, Siebel, etc.)
• Oracle Database Options and Packs

However, Oracle’s license portability rules and counting methodologies vary significantly by cloud provider.

Using Oracle BYOL in Oracle Cloud Infrastructure (OCI)

Oracle BYOL Benefits on OCI

Oracle actively encourages BYOL usage in OCI through more favorable licensing terms compared to other clouds:

• Processor Licensing Advantage:
  Oracle calculates licenses in OCI by counting only physical OCPUs (Oracle Compute Units), which typically leads to lower license consumption compared to third-party clouds.
• BYOL Automation:
  Oracle Cloud offers built-in BYOL automation tools that simplify license tracking, compliance management, and reporting.
• Extended License Coverage:
  Licenses under active Oracle support can easily transition to OCI without additional fees.

OCI BYOL Licensing Rules and Counting

• Counting Methodology:
  Oracle licenses in OCI are calculated per OCPU (equivalent to one physical core with hyper-threading).
• Example Calculation:
  Deploying Oracle Database Enterprise Edition on an OCI virtual machine with 8 OCPUs requires licensing 8 processor cores. If using Intel processors (core factor 0.5), this translates to 8 × 0.5 = 4 processor licenses.
• Licensing Oracle Database Options in OCI:
  Database options (Partitioning, Active Data Guard, Advanced Security, etc.) require identical licensing as the core database software based on OCPU count.

Oracle BYOL Licensing in AWS

AWS Licensing Model for Oracle

Deploying Oracle products on Amazon Web Services (AWS) involves specific licensing rules defined by Oracle’s “Licensing Oracle Software in the Cloud Computing Environment” policy:

• vCPU Licensing Metric:
  Oracle licenses on AWS are calculated based on virtual CPUs (vCPUs), not physical processor cores, using Oracle’s cloud policy formula: 1 Oracle Processor license = 2 AWS vCPUs

AWS BYOL License Counting Example

• Example Scenario:
  Deploying Oracle Database EE on an AWS EC2 instance with 16 vCPUs requires: 16 AWS vCPUs / 2 = 8 Oracle processor licenses If the instance uses Database Options like Partitioning or Diagnostics Pack, licenses must match the Oracle database licenses (8 processor licenses).
• Licensing in AWS Dedicated Hosts:
  Dedicated hosts may reduce license usage, as customers can license based on physical cores instead of vCPUs.

Oracle BYOL Licensing in Microsoft Azure

Azure Licensing Model for Oracle

Azure licensing for Oracle closely resembles AWS but contains specific rules:

• vCPU Licensing Metric:
  Like AWS, Oracle licenses in Azure use vCPUs. Azure hyper-threaded vCPUs require the same Oracle cloud licensing formula:t1 Oracle Processor license = 2 Azure vCPUs

Azure BYOL License Counting Example

• Example Calculation:
  Running Oracle Database Enterprise Edition on an Azure VM with 12 vCPUs requires: 12 Azure vCPUs / 2 = 6 Oracle processor licenses
• Azure Dedicated Hosts:
  Like AWS, deploying Oracle products on Azure Dedicated Hosts can allow licensing at physical core levels, potentially lowering license counts.

Oracle BYOL Licensing in Google Cloud Platform (GCP)

GCP Licensing Model for Oracle

Google Cloud Platform follows similar rules to AWS and Azure, requiring careful management:

• vCPU Licensing Metric:
  Oracle’s policy for GCP licensing follows the same ratio as AWS and Azure: 1 Oracle Processor license = 2 GCP vCPUs

GCP BYOL License Counting Example

• Example Scenario:
  Deploying Oracle Database EE on a GCP Compute Engine VM instance with 8 vCPUs: CopyEdit8 GCP vCPUs / 2 = 4 Oracle processor licenses
• Important Consideration:
  Currently, GCP offers fewer options for Oracle-specific licensing optimizations like Dedicated Hosts than AWS or Azure.

Compliance Risks and Challenges with Oracle BYOL

Frequent License Compliance Issues

Misunderstanding Oracle’s BYOL rules across different cloud providers commonly leads to costly compliance issues during audits, including:

• Under-licensing due to incorrect vCPU counting.
• Failure to license Oracle Database Options and Packs accurately.
• Overlooking virtualization policies and Oracle Partitioning Policy rules.

Oracle Audit Practices

Oracle frequently audits BYOL deployments to verify compliance:

• Oracle audits typically involve detailed reviews of cloud deployment architectures, vCPU configurations, database usage, and options/packs deployment.
• Non-compliance results in significant financial penalties, including retroactive license and support fees.

Compliance Management Best Practices

• Conduct regular internal compliance reviews of BYOL deployments.
• Use Oracle-specific Software Asset Management (SAM) tools to track Oracle licensing accurately.
• Document license calculations, deployments, and cloud architecture choices.

Practical Steps to Successful Oracle BYOL Management

Step-by-Step BYOL Planning

1. Assess License Entitlements:
   • Document existing Oracle license entitlements.
   • Confirm active support status, which is required for BYOL transfers.
2. Choose Your Cloud Provider Carefully:
   • Compare licensing costs (OCI vs AWS vs Azure vs GCP).
   • Evaluate provider-specific licensing benefits, such as Dedicated Hosts or Oracle’s OCI OCPU advantages.
3. Calculate License Requirements Accurately:
   • Follow cloud-specific counting methodologies (vCPUs or OCPUs).
   • Include Database Options and Packs in calculations.
4. Deploy and Document Clearly:
   • Document cloud deployment architectures, configurations, and corresponding Oracle licensing calculations.
5. Regular Compliance Checks:
   • Conduct periodic internal license compliance audits.
   • Adjust license entitlements and deployments proactively to maintain compliance.

Leveraging Oracle BYOL Negotiation Strategies

• Renewals and License Negotiations:
  Strategically negotiate Oracle agreements to explicitly include favorable BYOL terms.
• Contract Clarity:
  Define clear language for cloud deployments, license portability, and virtualization rules within Oracle contracts to minimize ambiguity and compliance risk.
• Oracle Sales Engagement:
  Engage Oracle sales teams proactively, clarifying expectations and BYOL plans, especially during renewal or procurement processes.

Conclusion: Optimizing Oracle BYOL in the Cloud

Oracle BYOL offers significant advantages for leveraging existing licenses in the cloud, reducing licensing costs, and improving flexibility. However, successfully navigating Oracle’s licensing policies across OCI, AWS, Azure, and GCP requires a thorough understanding, careful compliance management, and accurate license counting.

By clearly understanding cloud-specific licensing rules, proactively managing compliance, effectively leveraging vendor negotiations, and consistently documenting license usage, organizations can fully realize the benefits of Oracle BYOL while minimizing compliance risks and maximizing their Oracle software investments in cloud environments.

Do you want to know more about our Oracle Advisory Services?

Please enable JavaScript in your browser to complete this form.

Name *

Email *

Company

Message *

Submit