oracle license agreements

Oracle PULA – Oracle Perpetual ULA

What is Oracle PULA?

  • Perpetual Unlimited License Agreement (PULA).
  • Grants unlimited deployment rights for specific Oracle software.
  • No set end date, unlike ULA.
  • Simplifies asset management.
  • Eliminates license fees for included products.
  • Reduces audit risks.
  • Requires customers to forgo partial termination of unused licenses.

Introduction to Oracle PULA

Introduction to Oracle PULA

The Oracle Perpetual Unlimited License Agreement (PULA) is a distinctive licensing model offered by Oracle. It provides organizations with unlimited deployment rights for a specified set of Oracle software products indefinitely.

Unlike the more common Unlimited License Agreement (ULA), which has a defined end date, a PULA offers a perpetual, ongoing licensing arrangement, thereby eliminating the need for frequent renewals.

This licensing model is particularly significant for organizations seeking long-term, scalable solutions without the constraints of conventional licensing agreements.

Comparison with Other Licensing Models:

  • Perpetual Aspect: PULA’s primary advantage over other licensing models is its perpetual nature, which allows continuous use without periodic renewals or re-negotiations.
  • Unlimited Deployment Rights: Like ULAs, PULAs grant unlimited deployment rights, but with the added benefit of indefinite rights, providing greater long-term flexibility.
  • Simplified Management: PULA simplifies software asset management by providing a single, comprehensive license for multiple Oracle products, reducing administrative overhead and complexity.
  • Cost Predictability: Organizations can better predict and manage their long-term licensing costs by establishing a perpetual agreement.

What is PULA Oracle – Perpetual Unlimited License Agreement?

What is PULA Oracle – Perpetual Unlimited License Agreement?

Oracle PULA is an advanced licensing framework designed to offer extensive deployment rights across various Oracle software products. Here’s a detailed look into what PULA entails:

Detailed Explanation:

  • Unlimited Rights: PULA allows companies to deploy unlimited licenses for specified Oracle products indefinitely.
  • No Partial Termination: In exchange for these rights, organizations must relinquish the ability to partially terminate unused licenses, which requires careful planning and assessment of future needs.
  • Product Selection: Companies can choose which Oracle products to include in the PULA, allowing tailored licensing to meet specific business needs.
  • Geographic Flexibility: The agreement can be negotiated to include deployment rights across various geographic locations, enhancing global operations.

Key Benefits:

  • Simplified Asset Management: PULA streamlines software asset management by consolidating licensing into a single agreement, reducing administrative burden.
  • Elimination of License Fees: PULA eliminates ongoing license fees for included products, which can result in significant cost savings over time.
  • Virtual Environment Deployment: PULA allows Oracle software deployment in virtual environments without additional licensing complexities.
  • Reduced Audit Risk: The risk of Oracle audits is minimized, as compliance is inherently maintained through the perpetual licensing model.

Differences Between Oracle PULA and ULA:

  • Duration: The most notable difference is the perpetual duration of PULA compared to the fixed-term of ULA. PULA does not have an end date, offering indefinite usage rights.
  • Renewal and Certification: While ULA requires certification and possible renewal at the end of the term, PULA eliminates these requirements, providing continuous, uninterrupted usage rights.
  • Flexibility: PULA offers less flexibility in terminating unused licenses but provides greater stability and predictability for long-term software usage.
  • Cost Structure: PULA’s cost structure is typically higher upfront but offers long-term savings by eliminating the need for future license purchases and renewals.

In summary, Oracle PULA is a robust licensing solution for organizations seeking long-term, scalable, and simplified software asset management. Its perpetual nature and unlimited deployment rights make it an attractive option for businesses planning extensive Oracle software usage without the constraints of traditional licensing agreements.

Benefits of the Oracle Perpetual Unlimited License Agreement

Benefits of the Oracle Perpetual Unlimited License Agreement

Simplified Software Asset Management: Oracle PULA streamlines asset management by consolidating multiple licenses into a single agreement. This reduces administrative overhead and simplifies tracking and compliance efforts, making it easier to manage Oracle software assets.

Elimination of License Fees for Included Products: With Oracle PULA, you eliminate the ongoing license fees for the products included in the agreement. This can lead to significant cost savings over time, as there are no additional costs for deploying more instances of the included software.

Flexibility in Virtual Environments: PULA allows for deploying Oracle software in virtual environments without additional licensing complexities. This flexibility supports modern IT infrastructure needs, enabling efficient use of resources and seamless scalability.

Reduced Risk of Oracle Audits: By providing unlimited deployment rights, Oracle PULA minimizes non-compliance risk and reduces the likelihood of audits. This peace of mind allows organizations to focus on growth and innovation rather than regulatory concerns.

Oracle PULA vs. ULA

Oracle PULA vs. ULA

Key Differences in Certification, Deployment Rights, and Contract Duration:


  • PULA: No need for periodic certification, as the agreement is perpetual.
  • ULA: This requires certification at the end of the term, where usage is documented, and the agreement may need renewal or conversion.

Deployment Rights:

  • PULA: Grants perpetual, unlimited deployment rights for specified Oracle products.
  • ULA: Grants unlimited deployment rights only for the duration of the agreement, which must be certified and potentially renewed at the end of the term.

Contract Duration:

  • PULA: Indefinite duration, providing continuous and uninterrupted usage rights.
  • ULA: Fixed-term duration, typically three to five years, requiring renegotiation and certification upon expiration.

Impact on Business Strategy and Licensing Management:

Business Strategy:

  • PULA supports long-term strategic planning with predictable costs and stable licensing terms. It is ideal for organizations with stable, long-term Oracle software needs.
  • ULA: Better suited for organizations with short-to-mid-term growth plans. The need for periodic renewal allows for adjustments based on changing business requirements.

Licensing Management:

  • PULA: Simplifies licensing management with a one-time agreement, reducing the need for ongoing negotiations and certifications. This is advantageous for organizations seeking stability and simplicity.
  • ULA: This agreement offers more flexibility in adjusting the scope at renewal points. This can benefit businesses anticipating significant software usage changes or organizational structure changes.

In conclusion, Oracle PULA offers a perpetual and simplified approach to licensing, providing significant benefits in terms of cost savings, compliance, and flexibility.

In contrast, the ULA offers more periodic flexibility and the opportunity to reassess needs at regular intervals. Understanding these differences helps organizations choose the licensing model that best aligns with their business strategy and operational needs.

Certifying Your Oracle Perpetual Unlimited License Agreement (PULA)

Certifying Your Oracle Perpetual Unlimited License Agreement (PULA)

Importance of Certification for Compliance and Cost Optimization: Certifying your Oracle PULA ensures you remain compliant with Oracle’s licensing terms and helps optimize costs by verifying your usage against the agreement’s terms.

Three Approaches to Certification:

1. Acquisition by Another Company: The new entity assumes responsibility for certifying the Oracle PULA.

2. Addressing Non-Compliance: If the contract is breached, corrective actions must be taken to align with the PULA terms to achieve certification.

3. Maintaining Total Technical Support Stream: Ensuring continuous Total Technical Support (TTS) is crucial. Failure to maintain TTS can result in losing certification.

Steps to Achieve and Maintain Certification:

1. Review Contract for Certification Rights: Ensure your contract allows for independent certification. If not, negotiate this term with Oracle.

2. Conduct Oracle License Measurement: Use Oracle LMS Scripts to measure deployments and determine the licenses needed.

3. Address Noncompliance: Resolve any discrepancies found during measurement to align with PULA terms.

4. Optimize Deployments: Utilize virtual platforms like VMware to maximize efficiency and compliance.

5. Initiate the Certification Process: Submit the required documentation and reports to Oracle for certification.

Critical Considerations Before Signing an Oracle PULA

Critical Considerations Before Signing an Oracle PULA

Separate PULAs for Database and Middleware: Consider having distinct PULAs for Oracle Database and Middleware to allow for flexible support termination without affecting the other.

Impact of Multiple Legacy Support Agreements: Having multiple legacy support agreements can increase the cost of Oracle PULAs. Organizations without extensive existing Oracle support agreements benefit the most.

Suitability for Customers with Minimal Legacy Support: PULAs are best suited for customers with minimal legacy support, making it easier to manage and integrate the new agreement.

Considerations for Public Cloud Transitions: If transitioning to the public cloud, an Oracle PULA might not be ideal, as public cloud deployments typically cannot be counted towards certification numbers. Negotiate specific contract terms for cloud deployments before committing to an Oracle ULA.

Importance of Terms and Conditions: Review the PULA terms thoroughly, as they are one of the most significant agreements with Oracle. Ensure they align with your long-term business strategy.

Verification by an Independent Consultant: Engage an independent consultant to verify the agreement details and ensure you are not overpaying Oracle.

Potential Benefits of Oracle OCI Support Rewards: Utilizing Oracle OCI may qualify you for support rewards, potentially reducing support costs by 33%. This benefit can be a crucial factor when considering an Oracle PULA.

These steps and considerations are vital for effectively managing an Oracle PULA, ensuring compliance, optimizing costs, and aligning the agreement with your organization’s strategic goals.

How to Initiate the Oracle PULA Certification

Review of Certification Process Alternatives: Examine your contract to identify available certification processes. Determine if you have the independent right to start the certification or if you need to negotiate with Oracle.

Conducting Oracle License Measurement: Perform a detailed license measurement using Oracle LMS Scripts. This helps identify the actual usage and ensures accurate reporting to Oracle.

Addressing Non-Compliance and Optimizing Deployments: Identify and resolve any non-compliance issues. Optimize your Oracle deployments to align with the PULA terms, using virtualization strategies if necessary.

Steps to Initiate and Complete the Certification Process:

  1. Review Certification Rights: Ensure you can independently initiate the process or negotiate for this right.
  2. Conduct License Measurement: Use LMS Scripts to measure deployments accurately.
  3. Resolve Non-Compliance: Address any compliance issues.
  4. Optimize Deployments: Ensure your infrastructure aligns with Oracle’s requirements.
  5. Initiate Certification: Contact Oracle to start the formal certification process.
  6. Complete Documentation: Fill out and submit the necessary certification documents to Oracle.

Oracle ULA vs PULA: Understanding the Differences

Comparison of Merger and Acquisitions Considerations: ULAs typically allow adding new entities up to a certain threshold (e.g., 10% of revenue or employee size). PULAs require more careful consideration for M&A activities, as they might impose stricter limitations.

Flexibility in Product Management: ULAs offer flexibility to add or remove products during contract renewals. PULAs, however, only allow adding products without the option to remove any, potentially leading to higher long-term costs.

Vendor Lock-In and Support Contracts: ULAs consolidate all existing support contracts into one, limiting the ability to terminate unused software. PULAs also aim to lock in support contracts but are more restrictive in allowing partial terminations.

Pricing Differences and Strategic Implications: PULAs are generally 30-50% higher than ULAs due to their perpetual nature and the additional value Oracle perceives. This pricing strategy necessitates a careful evaluation of your organization’s long-term needs and potential flexibility.

Key Contract Terms to Focus on When Signing an Oracle PULA

Key Contract Terms to Focus on When Signing an Oracle PULA

Customer Definition to Include All Entities Accessing Software: Ensure the customer definition in the contract covers all entities using the software to avoid licensing gaps.

Territory Clause for Deployment Flexibility: Verify that the territory clause allows software deployment in all required locations, including public cloud zones outside your primary territory.

Options for Capping Support Fees: Explore options to cap annual support fee increases, typically 8%, to control long-term costs.

Provisions for Mergers and Acquisitions: Include clauses to seamlessly incorporate new entities acquired during the PULA term, maintaining comprehensive coverage.

ULA Certification Clause Specifics: Detail the audit process, required cooperation level, and how public cloud deployments are counted to ensure favorable certification terms.

Impact on Public Cloud Deployments: If applicable, ensure the contract language includes provisions for deploying Oracle software in public cloud environments.

FAQ: Oracle PULA

What is an Oracle PULA?
Oracle PULA, or Perpetual Unlimited License Agreement, grants unlimited deployment rights for specific Oracle products without an end date.

How does a PULA differ from a ULA?
A PULA has no set end date, while a ULA requires certification at the end of its term.

What are the benefits of an Oracle PULA?
Benefits include simplified asset management, elimination of additional license fees, and reduced audit risks.

Who should consider an Oracle PULA?
Organizations with stable, long-term Oracle software needs and minimal legacy support requirements should consider a PULA.

Can Oracle PULA be used in virtual environments?
Yes, Oracle PULA allows deployments in virtual environments, providing flexibility in software usage.

How does PULA impact Oracle audits?
PULA reduces the risk of Oracle audits, as the agreement covers unlimited usage rights for the included products.

What products can be included in an Oracle PULA?
Products typically include Oracle databases, middleware, and other specific Oracle software products.

Is there a certification process for Oracle PULA?
Certification involves ensuring compliance and cost optimization. Approaches include addressing non-compliance, maintaining support streams, and managing acquisitions.

What should be considered before signing an Oracle PULA?
Considerations include the impact of legacy support agreements, suitability for public cloud transitions, and the importance of contract terms.

How can merging companies handle Oracle PULA?
Ensure the PULA includes provisions for incorporating new entities acquired during the agreement term.

What is the impact of Oracle PULA on support fees?
Options for capping support fees should be explored to manage long-term costs effectively.

Can Oracle PULA be used in public cloud environments?
Yes, but ensure contract language includes provisions for deploying software in public cloud environments.

What happens if there is non-compliance with Oracle PULA?
Address non-compliance promptly to align with contractual terms and maintain certification.

How does PULA pricing compare to ULA pricing?
PULA pricing is typically higher than ULA, reflecting the perpetual nature of the agreement.

Can Oracle PULA agreements be customized?
Yes, negotiate terms and conditions to ensure the agreement aligns with your organization’s needs and provides flexibility for future changes.


  • Fredrik Filipsson

    Fredrik Filipsson brings two decades of Oracle license management experience, including a nine-year tenure at Oracle and 11 years in Oracle license consulting. His expertise extends across leading IT corporations like IBM, enriching his profile with a broad spectrum of software and cloud projects. Filipsson's proficiency encompasses IBM, SAP, Microsoft, and Salesforce platforms, alongside significant involvement in Microsoft Copilot and AI initiatives, enhancing organizational efficiency.