Oracle License Types

Oracle License Types

• Perpetual License: One-time purchase for indefinite use.
• Term License: Temporary access for defined periods.
• BYOL: Use existing licenses in the cloud.
• Processor License: Based on physical processors.
• Named User Plus (NUP): Based on individual users or devices.

Introduction To Oracle License Types

Oracle’s licensing models offer a range of options designed to fit different business needs, infrastructure setups, and scalability plans. Selecting the right type of Oracle license is crucial for aligning your organization’s technical requirements with cost-effective, compliant solutions.

Understanding these licensing models helps businesses maximize the value of Oracle’s offerings while ensuring compliance with complex usage terms.

1. Oracle Named User Plus License

Overview of Named User Plus (NUP) Licensing Model

The Named User Plus (NUP) licensing model is based on the number of individuals or devices authorized to use the Oracle software, regardless of whether they actively use it. Each user or device must have a valid license. NUP is ideal for smaller deployments with well-defined and limited user counts, making it a cost-effective solution in controlled environments.

• Key Features: NUP licenses are user-specific and apply to all individuals or devices authorized to use the software. This makes them well-suited for small—to medium-sized organizations with a controlled number of users accessing Oracle databases or other products.

When to Use NUP

• Limited User Environments: NUP licensing is most advantageous in environments with a small, clearly defined number of users, such as internal systems for a department or branch office.
• Cost Efficiency for Small Deployments: The NUP model can be more cost-effective than processor-based licensing if the number of users or devices accessing Oracle products is relatively low.
• Internal Databases: NUP is ideal for applications or databases inaccessible to an external or unlimited audience. This includes internal business applications and non-public web applications.

Compliance Considerations

• User Tracking: Accurately tracking all authorized users or devices is essential to ensure compliance with the NUP agreement. This involves maintaining an up-to-date list of users and keeping records of who can access the Oracle software.
• Minimum User Requirements: Oracle often sets minimum user requirements for NUP licenses, especially in multi-core environments. Ensure compliance by verifying these minimums are met, even in environments with fewer users.
• Internal Audits: Regular internal audits are advisable to verify the number of users against licensed entitlements. This can prevent potential issues during Oracle’s formal audit process.

2. Oracle Processor License

Explanation and Use Cases for Processor Licenses

The Processor License model licenses Oracle software based on the server’s number of physical processor cores. This model is ideal for environments where the number of users cannot be easily quantified or is essentially unlimited, such as publicly accessible web applications. Processor licensing uses Oracle’s Core Factor Table to determine the licensing requirement based on the specific hardware.

• Key Features: Processor licenses are calculated based on the number of processor cores multiplied by a core factor specific to the processor type. This allows for licensing based on computing power rather than the number of users.

Ideal Deployment Scenarios

• High User Count Applications: Processor licensing is often used for large-scale applications with vast or unpredictable users. Examples include public-facing web applications, large enterprise databases, and software accessed by multiple departments.
• Internet-Facing Deployments: If Oracle software is used in an application accessible via the internet, where it’s impossible to track individual users, a processor license is generally required.
• Cloud and Virtualized Environments: Processor licenses are also suitable for cloud or virtualized environments where managing user count is not feasible, but processor capacity can be allocated.

Cost Implications

• Core Factor Calculation: The number of required processor licenses is calculated by multiplying the number of physical cores by a core factor specified in Oracle’s Core Factor Table. For example, Intel Xeon processors may have a core factor of 0.5, reducing the number of licenses needed compared to other hardware types.
• Scalability: Processor licensing can become more cost-effective as the number of users grows, especially in environments where user count is high or fluctuates widely.
• Potential Savings: When implemented in environments with large-scale or unpredictable user bases, processor licensing may provide significant cost savings over individual user licensing models.

3. Oracle Application-Specific Full Use (ASFU)

Guide to ASFU License Type and Its Limitations

The Application-Specific Full Use (ASFU) license is a restricted type of Oracle license that can only be used in conjunction with a specific partner application. Oracle partners typically sell ASFU licenses as part of a broader software solution. Still, these limitations prevent their use outside the context of the specific application for which they were acquired.

• Key Features: ASFU licenses are limited to use with a particular software bundle, meaning they are not transferable for other Oracle software or general use. They offer a cost-effective solution for specific, pre-packaged software applications but lack flexibility for broader deployments.

ASFU vs. Full Use License

• ASFU License: Restricted to a single partner application. ASFU licenses are generally less expensive but have strict usage constraints that limit their applicability outside the specific bundled software.
• Full Use License: This license allows unrestricted use of the Oracle software in any environment or application. Due to the broader usage rights they grant, Full Use licenses are more flexible but tend to be more costly compared to ASFU.
• Cost Comparison: ASFU licenses can be more cost-effective for organizations needing Oracle software for a third-party solution. Full-use licenses provide greater flexibility at a higher cost.

When to Consider ASFU

• Third-Party Application Bundles: ASFU licenses are best suited for use cases involving third-party applications where Oracle software is embedded as part of the overall solution. For example, a healthcare management system with Oracle Database as its backend might use ASFU licensing.
• Cost-Sensitive Deployments: If cost is a significant factor and the Oracle software will only be used in the context of a particular application, ASFU offers a lower-cost alternative to full-use licensing.
• Limited Scope Deployments: ASFU is ideal for organizations that need Oracle software to perform specific functions within a restricted environment and do not foresee expanding the scope of use beyond the bundled application.

4. Oracle Embedded License

Insights on Embedded Licensing for Oracle Products

An Embedded License is an Oracle license typically bundled with specific software or hardware solutions. These licenses are designed for specific use cases with Oracle products embedded in a broader system. Embedded licenses are commonly seen in scenarios where Oracle software is used by original equipment manufacturers (OEMs) or as part of a proprietary hardware solution provided by Oracle partners.

• Key Features: Embedded licenses are not sold separately. Instead, they come as part of a package deal where Oracle software is pre-configured and embedded into a specific solution, limiting its usage to that context only.

Restrictions and Flexibility

• Limited Use: Embedded licenses are heavily restricted compared to full-use licenses. They are explicitly tied to the hardware or software they were originally bundled, meaning they cannot be used for other purposes or transferred across different environments.
• No Customization: Unlike Full Use or Application Specific Full Use (ASFU) licenses, embedded licenses cannot be customized or repurposed. This limits their flexibility, making them suitable only for specific, controlled applications.
• Non-Transferable: Embedded licenses cannot be transferred between different systems or environments, which further restricts their applicability beyond the original scope defined at the point of purchase.

Common Use Cases

• OEM Hardware: Embedded licenses are often used by Original Equipment Manufacturers (OEMs) that incorporate Oracle databases or middleware into their hardware solutions. For example, an industrial equipment provider might include an embedded Oracle database for managing equipment data.
• Proprietary Software Solutions: Some proprietary software solutions sold to end customers include an embedded Oracle database. This ensures customers have everything they need to run the software effectively without purchasing a separate Oracle license.
• Specialized Devices: Embedded licenses are also used in specialized devices that require pre-installed Oracle software, such as medical equipment or point-of-sale systems, where the Oracle software is an integral part of the device’s functionality.

5. Oracle ULA (Unlimited License Agreement)

Details on ULAs and Enterprise Applications

An Oracle ULA (Unlimited License Agreement) is a contractual agreement that allows an organization unlimited usage rights to specific Oracle products for a defined period, usually three to five years. ULAs are targeted towards large enterprises with growing IT needs that require flexibility in scaling their Oracle software deployments without worrying about incremental licensing costs.

• Key Features: The ULA grants unlimited usage rights to specific Oracle products during the agreement term. At the end of the term, organizations must certify their usage, after which they retain the licenses they’ve deployed.
• Scope: ULAs typically cover products like Oracle Database, middleware, and certain enterprise applications, making them ideal for organizations that use multiple Oracle solutions.

Benefits and Challenges

• Benefits for Large Enterprises: ULAs predict costs for expanding enterprises, allowing unlimited deployment of the specified Oracle products during the contract period. This is advantageous for companies undergoing rapid growth or mergers that expect their Oracle usage to increase significantly.
• Challenges Post-ULA: When a ULA expires, organizations must certify their usage. This process can be complex, requiring thorough documentation of how the Oracle software was deployed. If companies underestimate their needs during certification, they may find themselves under-licensed. Alternatively, if growth expectations do not meet reality, ULAs can result in overpaying for unused capacity.

Best Practices for ULA

• Plan for Certification: Start preparing for the end-of-term certification well in advance. To simplify the certification process, keep detailed records of deployments throughout the ULA term.
• Maximize Deployments: To maximize the value of a ULA, consider expanding Oracle deployments to cover as many business functions as possible during the agreement period. Deploy additional instances of databases or middleware before the ULA expires to lock in usage rights.
• Regular Internal Reviews: Conduct regular reviews to track the actual usage of Oracle products throughout the ULA term. This helps avoid surprises during certification and ensures you get the most out of your unlimited rights.

6. Oracle Subscription-Based Licensing

Details of Subscription Options in Oracle’s Licensing

Oracle offers Subscription-Based Licensing for products such as Java SE, MySQL, and Solaris. These subscription licenses provide flexible payment terms typically billed monthly or annually, ensuring customers can always access the latest versions, updates, and patches for these products.

• Java SE: Subscription licensing for Java SE allows enterprises to receive regular updates, including security patches and new features, ensuring that Java applications remain secure and compliant. Java SE subscriptions are ideal for businesses that rely on Java runtime for critical operations and need predictable maintenance costs.
• MySQL: MySQL subscription licenses offer access to enterprise-level features, support, and updates. Subscriptions include access to advanced capabilities, such as MySQL Enterprise Backup and MySQL Enterprise Monitor, making them essential for companies using MySQL in production environments where uptime and reliability are crucial.
• Solaris: Oracle Solaris subscriptions ensure continuous access to the latest innovations in the Solaris operating system. This subscription is particularly valuable for enterprises running mission-critical workloads that require a robust, stable, and supported UNIX-based OS.

7. Oracle License Metrics

Key Metrics to Understand for All Oracle Licenses

Oracle licensing involves several key metrics that determine different licensing models’ cost and compliance requirements. Understanding these metrics is crucial to selecting the appropriate license for your deployment.

• Processor Licensing: This metric is based on the number of physical cores in a server, adjusted by a Core Factor that varies depending on the processor type. The Core Factor table multiplies the number of cores to determine how many processor licenses are required. This metric is commonly used for large-scale deployments where user count cannot be easily managed.
• Named User Plus (NUP): The NUP metric is used when licensing Oracle software based on individual users or devices. This licensing metric works well for environments with a defined and limited number of users. Oracle often sets a minimum number of NUP licenses required per processor, depending on the product.
• Core Factor: The Core Factor is a multiplier used to determine the number of processor licenses needed based on the number of physical cores. Different types of processors have different core factors, which are published in Oracle’s Core Factor Table. For example, Intel processors may have a lower core factor than other hardware types, affecting the required licenses.

How Metrics Affect Cost

• Processor vs. NUP: Processor and NUP licensing has significant cost implications. Processor licensing is often more cost-effective when dealing with many users, such as in internet-facing applications. However, NUP licensing may better suit internal applications with a controlled user base.
• Core Factor Considerations: The Core Factor affects the number of licenses required and, ultimately, the cost. Servers with lower core factor processors will require fewer licenses, reducing overall costs. Understanding your server’s hardware specifications is important to calculate licensing costs accurately.
• Deployment Type: The deployment environment—whether on-premises, cloud, or hybrid—will influence which metric is more advantageous. Cloud environments may benefit from subscription-based models that offer metrics different from traditional on-premises deployments.

Tracking Metrics for Compliance

• Oracle LMS Tools: Oracle provides License Management Services (LMS) tools that help organizations track licensing usage metrics. These tools are crucial for maintaining compliance and ensuring usage matches the entitlements.
• Software Asset Management (SAM) Tools: Third-party SAM tools can also monitor license metrics and track compliance. These tools can provide insights into user counts, processor utilization, and overall deployment metrics, ensuring alignment with Oracle licensing agreements.
• Internal Audits: Conducting regular internal audits to track usage metrics against purchased licenses can help prevent compliance issues. By ensuring metrics like user counts and processor utilization are accurate, companies can reduce the risk of non-compliance during an Oracle audit.

8. Oracle Test and Development Licenses

Licensing Options for Development and Testing Environments

Oracle provides specific licensing options for non-production environments, such as development and testing, to support organizations during the software lifecycle without incurring the same costs as production environments.

• Oracle Technology Network (OTN): Oracle offers free developer licenses through the Oracle Technology Network (OTN), which allows using Oracle software in non-production environments for development and testing. However, these licenses are strictly limited to non-commercial use.
• Discounted Development Licenses: Oracle offers discounted development licenses for organizations that require development licenses beyond OTN’s scope. These licenses provide more flexibility while keeping costs lower than full-use production licenses.
• Oracle Cloud Free Tier: The Oracle Cloud Free Tier allows users to test and develop Oracle applications in a cloud environment without incurring significant licensing costs. This includes access to the Oracle Autonomous Database and other cloud services.

Restricted Usage

• Non-Commercial Purposes: Development and testing licenses are strictly for non-commercial use. This means they cannot be used in production or for any revenue-generating workload.
• Limited Deployment: These licenses generally cannot be used beyond the scope of testing and development, meaning they cannot be used for load testing in a production-like environment. Misuse of these licenses can lead to severe compliance issues.
• Time Limits: Some test licenses may also have a time limitation, meaning they can only be used for a specific period before requiring renewal or conversion to a full-use license.

Cost-Effective Testing

• Use OTN for Small Projects: For small-scale projects and initial prototyping, leveraging OTN developer licenses can effectively reduce costs while gaining access to Oracle’s powerful software.
• Cloud Testing: Using the Oracle Cloud Free Tier allows developers to test applications in a cloud environment, providing an experience that closely mirrors production without the associated costs.
• Discounted Licenses for Larger Teams: For larger development teams or projects requiring extensive testing, purchasing discounted development licenses ensures compliance while maintaining cost efficiency.

9. Oracle Licensing for SaaS

Overview of SaaS-Specific Licensing with Oracle

Software as a Service (SaaS) licensing with Oracle provides access to fully managed applications through a subscription model. Oracle handles all maintenance, updates, and infrastructure aspects, allowing organizations to focus on using the software rather than managing it.

• Subscription Model: Oracle SaaS offerings, such as Oracle ERP Cloud or Oracle HCM Cloud, are licensed on a subscription basis. These typically include the software, hosting, maintenance, and support services rolled into one package.
• Inclusive Features: SaaS subscriptions include access to the software, automatic updates, scalability options, and integrated security measures. This helps ensure that the software remains up-to-date and compliant with industry standards.

Benefits for Enterprises

• Scalability: SaaS licenses offer high scalability, making it easy for organizations to adjust usage based on their evolving needs. This is particularly advantageous for businesses experiencing growth or seasonal fluctuations.
• Reduced IT Overhead: Oracle handles the infrastructure, maintenance, and support for SaaS products, reducing the burden on internal IT departments. This allows IT teams to focus on strategic initiatives rather than day-to-day system management.
• Cost Predictability: The subscription model provides predictable monthly or annual costs, simplifying budgeting for IT expenses and avoiding large upfront capital expenditures.

Integration with On-Premises Solutions

• Hybrid Deployments: Oracle’s SaaS offerings can be integrated with on-premises Oracle software, creating a hybrid environment allowing seamless data flow between cloud-based and on-premises systems. This approach helps companies leverage the flexibility of the cloud while maintaining critical workloads on-premises.
• BYOL Compatibility: In some cases, businesses using SaaS can take advantage of Oracle’s Bring Your Own License (BYOL) program for other Oracle services, creating a cohesive licensing strategy that encompasses both cloud and on-premises resources.
• Data Integration Tools: Oracle provides tools like Oracle Integration Cloud to facilitate smooth interaction between SaaS and on-premises systems, ensuring consistent workflows and data synchronization across different environments.

10. Oracle Perpetual Licensing

Perpetual License Agreements with Oracle

The Perpetual Licensing model is a traditional approach in which customers make a one-time payment to gain indefinite use of Oracle software. Once purchased, perpetual licenses allow the business to use the software without any time constraints, providing long-term access without recurring fees, apart from optional support or maintenance agreements.

• Key Features: The perpetual license grants indefinite rights to use Oracle products. Customers can add Software Update License & Support (SULS) for ongoing maintenance and updates, typically costing a percentage of the original purchase price annually.

Cost vs. Long-Term Value

• Upfront Costs: Perpetual licenses come with a significant upfront cost compared to subscription models. The initial purchase is a capital expense, which may require substantial budget approval.
• Lower Long-Term Costs: Perpetual licenses can prove more cost-effective over the long term, especially in stable environments where the Oracle software is expected to be in use for many years. The one-time investment shields organizations from price hikes or subscription rate changes.
• Maintenance Costs: To keep Oracle software up to date, perpetual license holders often subscribe to SULS, which incurs an annual fee, usually around 22% of the license cost. Despite this, the overall expenses can still be lower than subscription fees over a similar timeframe.

When Perpetual Licensing Is the Best Fit

• Long-Term Projects: Perpetual licensing is ideal for projects expected to last several years or more, where the one-time cost becomes economical compared to recurring subscription fees.
• Stable Environments: A perpetual license provides a cost-effective solution if the infrastructure and business operations are stable, with no expected changes in user count or workload.
• Regulated Industries: Industries with stringent regulatory requirements that prefer on-premises control over their software and avoid constant dependency on vendors may benefit from the perpetual model, which ensures long-term access without ongoing contractual renewals.

11. Oracle Term Licensing

Short-Term Licensing and Its Applications

Term Licensing provides short-term access to Oracle software for a specific period, usually one to five years. Unlike perpetual licenses, term licenses grant usage rights for a limited time, after which they must be renewed or terminated.

• Key Features: Term licenses require lower upfront costs and provide flexibility for organizations that do not need indefinite access. They are typically structured as an operational expense rather than a capital expense, making them more appealing for short-term projects or temporary needs.

Differences from Perpetual and Subscription Models

• Time Constraints: Unlike perpetual licenses, which are indefinite, term licenses have a defined end date. After expiration, the software must either be renewed or stopped.
• Lower Initial Investment: Term licensing offers a lower initial cost than perpetual licenses, as there is no large upfront payment. However, unlike subscription models that may offer cloud-based access, term licenses are typically associated with on-premises installations.
• Flexibility: Term licensing provides more flexibility than perpetual licensing when the usage requirements are uncertain but has less scalability compared to cloud subscriptions, which can be adjusted monthly or annually.

Best Use Cases for Term Licensing

• Temporary Projects: Term licensing is well-suited for projects with a clear end date, such as proof of concept (POC) deployments or testing new business applications before making a long-term commitment.
• Budget Constraints: Organizations looking to reduce upfront investments and maintain flexibility in their budgeting can benefit from term licenses, as they are considered operational expenses.
• Interim Solutions: When transitioning from one system to another, term licenses provide a cost-effective interim solution that allows access to Oracle products without long-term commitments.

12. Oracle Licensing for Third-Party Clouds

How to Navigate Oracle Licensing in Non-Oracle Cloud Environments

Deploying Oracle software in non-Oracle cloud environments such as AWS, Azure, or Google Cloud involves unique challenges and considerations. Oracle licenses can be used in third-party cloud environments, but careful attention must be paid to Oracle’s licensing terms and conditions.

• License Mobility: Oracle allows certain licenses to be deployed in third-party clouds under the Bring Your Own License (BYOL) model. However, ensuring that the third-party cloud infrastructure complies with Oracle’s technical requirements, including the proper configuration of virtual cores, is crucial.
• Regional Compliance: The licensing rules may vary by region, particularly regarding cloud deployment. Organizations must ensure the cloud provider complies with local regulations to avoid penalties.

BYOL and Licensing Compliance

• BYOL (Bring Your Own License): Oracle’s BYOL program enables customers to transfer their existing on-premises licenses to supported cloud environments, which can significantly reduce costs. Oracle must approve the cloud provider and the software must be deployed by Oracle’s licensing policies.
• License Tracking: Compliance can be challenging when using BYOL in third-party clouds. Proper tracking of virtual machine instances, cores, and usage hours is essential to ensure the deployment remains within the agreed licensing terms.
• Audit Risks: Deployments in non-Oracle cloud environments may be subject to Oracle audits. Organizations should thoroughly document how and where licenses are used to avoid potential compliance risks.

Cost Comparisons

• Oracle Cloud vs. Third-Party Providers: While Oracle Cloud Infrastructure (OCI) may offer simplified and often discounted licensing options for Oracle software, third-party clouds like AWS or Azure may require additional licensing considerations that impact cost. Compared to deploying in third-party environments, Universal Credits in OCI can provide flexibility and potential cost savings.
• Hidden Costs: Using Oracle software in non-Oracle clouds can lead to unexpected costs, such as higher infrastructure expenses due to the need for additional licenses. For example, Oracle’s licensing requirements for virtualized environments may require licensing the entire underlying hardware if Oracle products are used in a virtual machine, which may significantly increase costs.
• Cloud Integration: The costs associated with deploying Oracle software in third-party clouds are often higher if integration with other Oracle Cloud services is needed, as OCI provides native integration benefits unavailable on other cloud platforms.

13. Oracle BYOL Licensing Conditions

Full Guide to Bring Your Own License Conditions with Oracle

The Bring Your Own License (BYOL) program allows Oracle customers to apply their existing on-premises licenses to Oracle Cloud Infrastructure (OCI) or third-party clouds like AWS and Azure. This approach helps organizations maximize their current investments while benefiting from cloud scalability and flexibility.

• Key Features: With BYOL, customers can transfer their existing Oracle licenses to the cloud, enabling them to reduce new licensing costs when adopting cloud services. This program applies to various Oracle products, including databases, middleware, and applications.

Eligibility Criteria

• Eligible Licenses: Not all Oracle licenses qualify for BYOL. Typically, only Full-Use licenses purchased without any deployment restrictions are eligible. Licenses obtained under special programs or restricted use licenses, such as Application-Specific Full Use (ASFU), may not be eligible.
• Version Requirements: Under the BYOL model, only specific versions of Oracle software are sometimes allowed. Verifying eligibility based on the product version and any associated technical requirements is important.
• Cloud Provider Compliance: The cloud provider where you intend to use BYOL must meet Oracle’s technical requirements for licensing, including CPU allocation, virtualization, and deployment transparency. Only approved providers, like OCI, AWS, and Azure, offer full support for BYOL.

Benefits of BYOL

• Cost Savings: BYOL allows organizations to leverage their existing investment in Oracle licenses, reducing the costs of adopting cloud services. This can significantly lower the Total Cost of Ownership (TCO) for cloud deployments.
• Flexibility: With BYOL, businesses can move workloads between on-premises and cloud environments. This is ideal for companies that require hybrid or multi-cloud strategies and want to avoid additional licensing costs.
• Optimal Utilization: Using BYOL ensures that Oracle licenses are fully utilized across environments, maximizing the value of the original purchase. This also allows businesses to seamlessly transition to cloud environments while maintaining compliance and minimizing overhead.

Oracle License Types FAQ

What is an Oracle Perpetual License? A perpetual license is a one-time purchase that grants indefinite use of Oracle software without recurring license fees, though maintenance costs may apply.

How does Term Licensing differ from Perpetual Licensing? Term licensing grants temporary access, usually one to five years, while perpetual licenses offer indefinite use after a one-time payment.

Can Oracle licenses be moved to the cloud? Oracle’s Bring Your Own License (BYOL) program allows existing licenses to be used in approved cloud environments like Oracle Cloud Infrastructure, AWS, and Azure.

What is the Processor License model? Processor licenses are calculated based on the number of physical cores in the server, using a core factor table to determine the number of licenses needed.

When should I use a Named User Plus (NUP) License? NUP licensing is best when a controlled, defined number of users or devices access Oracle software, making it cost-effective for internal use.

What is Application-Specific Full Use (ASFU) licensing? ASFU licenses are restricted to a specific partner application and cannot be used outside the context of that application. They are usually bundled with third-party software.

How do I stay compliant with Oracle Processor Licensing? Track the physical processors in your environment, calculate required licenses using Oracle’s core factor table, and ensure all usage matches licensing entitlements.

What are the advantages of BYOL for cloud deployments? BYOL allows you to leverage existing Oracle licenses, reducing cloud costs and maintaining compliance during cloud migrations or hybrid cloud setups.

Can Term Licenses be extended? Yes, term licenses can be extended upon expiration. This allows for flexibility if a temporary project needs more time or becomes permanent.

How does Oracle handle licensing audits? Oracle conducts audits to verify compliance. Organizations must provide detailed usage and deployment information to ensure all software is appropriately licensed.

What is Oracle’s Core Factor Table? The Core Factor Table is a multiplier used by Oracle to calculate the number of processor licenses needed based on the type of server hardware being used.

Are Oracle SaaS licenses perpetual or subscription-based? Oracle SaaS licenses are subscription-based, which includes software access, maintenance, and support for a recurring fee rather than a one-time purchase.

Can I mix license types for different Oracle products? Yes, you can mix and match different license types depending on your environment and needs, such as using BYOL for cloud and perpetual licenses for on-premises.

What are Oracle Test and Development Licenses? These are non-production licenses provided for development or testing purposes only. They cannot be used in production environments and are typically offered at reduced cost.

What happens when an Oracle ULA expires? Upon expiration of a ULA, you must certify your usage. After certification, you retain perpetual rights to the licenses deployed during the ULA term, but additional deployments will require new licensing.