Oracle ULA to Cloud – A Simplified Guide

Introduction to Oracle ULA to Cloud

• Oracle Unlimited License Agreements (ULAs) allow customers to deploy unlimited quantities of specific Oracle products. However, complications arise when non-ULA software is mistakenly deployed.
• The end of an Oracle ULA involves an audit phase, where deployment information is verified. If non-ULA software is found, customers must pay for new licenses or sign a new ULA.
• This article presents three contractual solutions to manage public cloud deployments under Oracle ULAs, providing a simplified understanding of Oracle ULA to Cloud.

Oracle ULAs: The Basics and Challenges

Oracle ULAs are contracts that grant customers the right to deploy unlimited quantities of specific Oracle products. However, deploying non-ULA software can lead to issues during the audit phase at the end of the ULA.

Key Takeaway: Review your Oracle ULA contract and understand your “exit process” to avoid complications.

Oracle ULA 2 Cloud – The Conflict

Customers can deploy Oracle ULA software in any public cloud within their territory deployment during the Oracle ULA. However, any deployments made in the third-party cloud cannot be counted towards your “exit numbers” when the Oracle ULA ends.

Contractual Solutions for Oracle ULAs and Public Cloud

1. No Public Cloud – Standard Option

Under this option, Oracle does not allow customers to count any deployments in a third-party cloud. This standard clause is found in about 90% of all Oracle ULA contracts.

Example: If you have deployed Oracle software in a third-party cloud during your ULA, these deployments will not be counted towards your “exit numbers” at the end of the ULA.

2. Last 365 Average – Option

Oracle allows customers to certify cloud deployments, but they can only count the average number of the last 365 days.

Example: If you have deployed Oracle software in the cloud throughout the year, you can only certify an average of these deployments. You may face compliance challenges if you have deployed a large amount of software in the last six months.

3. Restricted Use Option

Oracle allows customers to certify public cloud deployments, but those licenses are restricted to public cloud or on-premise software.

Example: If you have deployed Oracle software on-premise and in the cloud, you will have two sets of licenses post-Oracle ULA certification – one for on-premise and one for the cloud. This can create difficulty in managing your Oracle software post-ULA.

Recommendation: Review and negotiate your Oracle ULA or PULA contract’s certification clause before signing.

Conclusion and Recommendations

Oracle ULAs offer a lot of flexibility for deploying Oracle products. However, they also come with their own set of challenges, especially when it comes to cloud deployments. Understanding these challenges and the potential solutions can help avoid complications during the audit phase at the end of the ULA.

Key Takeaway: Negotiating the certification clause in your Oracle ULA or Oracle PULA contract can help manage these challenges. This clause deals with not only public cloud deployments but also your exit strategy. By negotiating this clause, you may be able to avoid an audit from Oracle.

FAQ