Oracle ULA to Cloud – Three solutions



Oracle ULA to Cloud – Introduction

Oracle ULA to cloud is one of the most common challenges customers face with enterprise agreements from Oracle. The Oracle Unlimited Agreement (ULA) offers customers the privilege of deploying an unlimited number of Oracle products that are part of the ULA. However, a common mistake made by ULA customers is the deployment of non-ULA software, which leads to detection during the audit phase at the end of the ULA. To help ULA customers avoid forced ULA renewals, the article outlines four main challenges faced by them.

At the end of an Oracle ULA, if a customer wants to exit or not renew the agreement, they are obligated to declare the quantities of their Oracle ULA deployments. This requires the customer to provide information on the amount of Oracle software deployed, with an audit often involved to verify the deployments of both ULA and non-ULA software. The licenses deployed during the ULA will then be converted into a fixed volume, and any non-ULA software detected will require the customer to pay for new licenses or sign a new ULA that includes those products.

The article recommends that ULA customers find their ULA contract and understand the certification clause, as there are customizations to this term that can be both good and bad.

Oracle ULA vs Public Cloud

Regarding the clash between Oracle ULA’s and public cloud, during the ULA, customers are free to deploy ULA software in any public cloud within their territory deployment. However, when the ULA ends, any deployments made in a third-party cloud cannot be counted towards the exit numbers. The article outlines three contractual solutions for how ULA’s manage public cloud:

  1. No Public Cloud – This is the standard clause for about 90% of all Oracle ULA contracts, where Oracle does not allow customers to count any deployments in a third-party cloud. This clause is almost a copy of Oracle’s licensing policy for licensing software in public clouds.
  2. Last 365 Average – Oracle gives customers the right to certify cloud deployments, but only the average number of the last 365 days can be counted. This term gives companies the right to claim licenses at the end of the ULA, but with the restriction of only certifying an average of the past 365 days.
  3. Restricted Use Option – Oracle gives customers the right to certify public cloud deployments, but those licenses are then restricted to public cloud or on-premise software. Customers need to specify which software is running in the public cloud and on-premise in the certification documents. This results in having two different license sets, which can create difficulties in managing the software post-ULA.

The article concludes by recommending that customers review and negotiate the certification clause before signing an Oracle ULA or PULA. This not only deals with public cloud but also the exit process, which could potentially save customers from undergoing an audit from Oracle. Option 2 should be acceptable to most ULA customers, but they must ensure they manage their ULA and avoid deploying large amounts of software in public cloud in the last 6 months.

Leave a Comment