Oracle Licensing Basics

//

FF

Oracle Licensing Basics

  • Types: Processor, Named User Plus (NUP), Subscription, BYOL.
  • Models: Perpetual, Term-based, Cloud-specific options.
  • Core Factor: Calculated based on processor type.
  • Compliance: Requires tracking hardware and users carefully.
  • Cloud Transition: BYOL for existing licenses; flexible options.

Oracle Licensing Basics

Oracle Licensing Basics

Oracle licensing can be complex and challenging, especially with various licensing models, metrics, and agreements. However, understanding the key terms, definitions, and licensing structures is crucial for IT managers, procurement specialists, and business decision-makers to ensure compliance, manage costs, and optimize software usage.

This article aims to break down the essentials of Oracle licensing, covering everything from key licensing terms to specific structures that help organizations deploy Oracle products effectively.

Key Terms and Definitions

To understand Oracle licensing, it’s essential to familiarize yourself with some of the common terms used in Oracle’s agreements and licensing models. Below are some of the most critical terms foundational to understanding Oracle licensing.

1. Processor

The Processor licensing metric refers to the physical CPUs in a server. Unlike traditional CPU count-based models, Oracle calculates processors differently, using a “Processor Core Factor Table” that assigns weights based on the processor architecture. This means that different processors may require different numbers of licenses based on their architecture. For instance, Intel or AMD processors may use a core factor of 0.5, while others use a factor of 1.0. This formula is especially important when dealing with modern multi-core CPUs, as it significantly impacts licensing costs.

2. Named User Plus (NUP)

Named User Plus (NUP) licenses are user-based and suitable for environments where the number of users can be easily identified and counted. NUP licenses apply to either individuals or devices that access the Oracle software. These licenses come with minimum user requirements based on the number of processors used, which means that the minimum number of NUP licenses you need depends on the hardware setup. This model is ideal for internal deployments where user numbers are relatively stable.

3. Socket

A Socket refers to the physical slot on a server where a processor is installed. In older Oracle licensing agreements, licensing was tied more closely to sockets, but with modern cloud and virtualized environments, the focus has shifted towards core-based licensing models. Understanding the historical concept of sockets helps with legacy systems that may still be under older licensing agreements.

4. Oracle License and Services Agreement (OLSA)

Oracle Master Agreement (OMA): Typically used for larger clients, this agreement consolidates all licensing and service contracts under a single, overarching document. It’s designed to simplify management for organizations purchasing multiple Oracle products.

5. Core Factor Table

Oracle uses the Core Factor Table to calculate how many processor licenses are needed for a given server. Each processor model and manufacturer is assigned a core factor multiplied by the number of cores to determine the total number of licenses needed. This approach allows Oracle to account for the differences in processing power across various CPU architectures, making licensing more equitable.

6. Oracle Ordering Document

The Oracle Ordering Document lists the specific licenses you have purchased, including their types, quantities, and applicable terms. This document is critical for verifying compliance and understanding your entitlements. It serves as a reference in case of an audit and helps track the scope of licensed products.

Oracle Licensing Models

Oracle Licensing Models

Oracle provides several licensing models designed to accommodate different deployment environments and use cases. Understanding these licensing models helps businesses choose the most cost-effective and compliant approach to using Oracle software.

1. Perpetual Licensing

Perpetual Licenses allow you to use the Oracle software indefinitely. These licenses come with a substantial upfront cost. While they do not have an expiration date, they require separate annual maintenance and support fees if you want continued access to software updates and technical support. This model is often preferred by organizations that need long-term, predictable usage without recurring subscription fees.

2. Subscription Licensing

Subscription Licensing is a newer model that aligns more with the evolving nature of IT environments, especially cloud computing. Instead of paying a large sum upfront, you pay a recurring fee monthly or annually. This model provides flexibility and scales well with growing or shrinking workloads. It also allows organizations to categorize their Oracle software expenses as operational rather than capital expenditures.

3. Term Licensing

Term Licensing is similar to subscription but is defined by a specific period, one, three, or five years. Once the term ends, the license expires unless it is renewed. This model is advantageous for projects with a limited lifespan or when testing Oracle products before committing to a perpetual license.

4. Bring Your Own License (BYOL)

The Bring Your Own License (BYOL) model allows organizations to use their existing on-premises licenses in cloud environments like Oracle Cloud Infrastructure (OCI) or third-party clouds like AWS and Azure. This model provides flexibility and reduces the need to purchase entirely new licenses when migrating to the cloud. BYOL is ideal for businesses transitioning to cloud computing without incurring the costs of acquiring brand-new licenses.

Licensing Structures

Oracle licensing structures determine how licenses are calculated, assigned, and managed. Processor-based and Named User Plus (NUP) licensing are the primary structures.

Processor-Based Licensing

Processor-based licensing is generally used for environments where the number of users is unknown or constantly fluctuating, such as in public-facing applications or high-load systems. The key factor in this model is calculating how many processors (or cores) need to be licensed using Oracle’s core factor. This structure scales effectively for large deployments but can become costly as the hardware footprint increases.

Example: If you are running Oracle Database on a server with two CPUs, each having eight cores, and the core factor is 0.5, the total number of processor licenses required would be licensed.

Named User Plus (NUP) Licensing

NUP Licensing is suitable for internal systems with a defined user base. This structure is user-centric, meaning each Oracle software user needs a license. However, Oracle has established a minimum number of NUP licenses per processor, which varies depending on the software product and deployment specifics. This makes NUP licensing ideal for smaller, well-defined environments.

Example: If a small Oracle instance runs internally with 30 active users, you would opt for NUP licensing. Depending on the hardware, Oracle may set a minimum of 25 users per processor, meaning you need at least 50 NUP licenses if running on a two-processor server.

Licensing for Cloud and Virtual Environments

Licensing for Cloud and Virtual Environments

With the rise of cloud computing and virtualized environments, Oracle licensing has adapted to meet these new challenges. However, licensing in cloud and virtual environments is complex, and a thorough understanding of Oracle’s policies is essential to remain compliant.

Virtualization Considerations

Oracle often requires licensing all cores within the physical cluster for virtual environments, even if Oracle software runs on only a subset of nodes. This policy is especially true for third-party virtualization platforms like VMware. This broad requirement can lead to significantly increased costs if not properly planned. Using Oracle VM or deploying on Oracle Cloud Infrastructure may simplify licensing and reduce costs.

Cloud Licensing

Oracle offers specific licensing models in the cloud, such as BYOL and Universal Credits. The Universal Credit Model allows organizations to use Oracle Cloud services with a pre-purchased pool of credits, offering the flexibility to allocate these credits to various services as needed. BYOL allows organizations to leverage existing investments while leveraging Oracle’s cloud infrastructure.

Best Practices for Oracle Licensing

To optimize Oracle licensing, organizations should consider the following best practices:

1. Conduct Regular License Reviews

Regular internal audits of your Oracle licenses and software deployments help maintain compliance and avoid penalties during an official Oracle audit. Identify underutilized licenses or instances where licenses may be misallocated.

2. Align License Type to Deployment Needs

Choosing between Processor-Based and NUP licensing should be based on the specific characteristics of your deployment. Processor-based is generally better for public-facing or dynamic workloads, while NUP suits predictable, smaller internal environments.

3. Utilize License Management Tools

Tools like Oracle LMS (License Management Services) or third-party software asset management tools can help track usage, maintain compliance, and optimize license allocation.

4. Stay Informed of Policy Updates

Oracle frequently updates its licensing policies, especially concerning virtualization and cloud deployments. Staying informed helps avoid non-compliance issues and can save costs using new programs like BYOL.

5. Plan for Cloud Transition

Understanding Oracle’s licensing models is critical if your organization transitions to the cloud. Consider using BYOL to reduce costs and ensure your current licenses are applied effectively in cloud environments.

Oracle Licensing Basics FAQ

What is Processor-based licensing in Oracle?
Processor licensing is based on the number of physical cores, adjusted by Oracle’s Core Factor Table to calculate the licenses required.

How does Named User Plus (NUP) licensing work?
NUP is a user-based license that covers individuals or devices accessing Oracle software. The minimums are based on server processor count.

What is an Oracle Master Agreement (OMA)?
The OMA is the primary contract outlining the terms of software use, covering rights, obligations, and limitations.

Can I use my existing licenses in the cloud?
Yes, using Oracle’s BYOL program, on-premises licenses can be used in Oracle Cloud, reducing additional licensing costs.

What is Bring Your Own License (BYOL)?
BYOL allows companies to use their existing licenses in a cloud environment like Oracle Cloud Infrastructure or third-party clouds.

How is the core factor calculated?
The Core Factor is applied to the number of processor cores to determine licensing requirements and varies by processor type, as per Oracle’s Core Factor Table.

What are the main Oracle licensing types?
The main types are Processor, Named User Plus (NUP), Subscription, and Cloud-specific options like BYOL.

How do I choose between NUP and Processor licensing?
Use NUP if users are countable and stable; use Processor licensing for dynamic environments or public-facing systems where user count is uncertain.

What is the term licensing?
Term licensing is a time-limited license, often one to five years, offering cost-effective licensing for specific projects or temporary needs.

Does Oracle require licenses for virtualized environments?
Yes, in most cases, Oracle requires licensing for all physical cores in the virtual environment, not just the nodes running Oracle software.

What is perpetual licensing?
Perpetual licensing allows indefinite use of the software with a one-time cost, but maintenance and support are paid annually.

Can Oracle licenses be transferred between servers?
Licenses can be transferred, but Oracle often has a 90-day reassignment rule, especially in virtual and cloud environments.

What tools help manage Oracle licenses?
Oracle LMS and third-party asset management tools help track usage and compliance and optimize license costs.

What happens during an Oracle audit?
Oracle audits verify compliance; if non-compliance is found, customers must purchase additional licenses, often with backdated fees and penalties.

How can I minimize Oracle licensing costs?
Conduct regular internal audits, utilize the BYOL program, align the right license types with specific deployments, and stay updated on policy changes.

Author