Why the hidden clauses matter.
The headline of an Oracle Unlimited License Agreement is the price, the term, and the product list. The economics of the agreement are decided elsewhere. A buyer who negotiates only the headline gets a deal that looks good on the cover page and performs poorly at certification. The clauses that determine the exit value sit in the definitions, the scope, the cloud deploy provisions, the M&A treatment, the support stream, and the certification mechanics. Each of these is a separate negotiation. Each has a documented set of buyer side levers.
The scope definition.
The scope definition lists the products that are in scope for unlimited deployment. The wording matters more than the list. A scope that names products by SKU is narrower than a scope that names products by family. A scope that includes options and packs is broader than a scope that names only the base product. The buyer side position on scope is to negotiate family level inclusion with named options and packs where possible. The Oracle position is to negotiate SKU level inclusion with options and packs as separate negotiations. The buyer side wins are typically family level inclusion of the named application or technology stack with a documented list of options and packs that are bundled at no additional charge.
The cloud deploy clause.
The cloud deploy clause governs where the unlimited deployment can take place. The standard Oracle position permits deployment on Oracle Cloud Infrastructure at a favourable conversion ratio and on authorised third party clouds at a less favourable conversion ratio. The buyer side levers on cloud deploy include improvement of the conversion ratios, expansion of the authorised cloud provider list, and fixing of the certification methodology version in force at the contract date so that subsequent Oracle methodology changes do not apply. The cloud deploy clause is covered in detail in our cloud deploy rights explainer.
The M&A treatment.
The M&A treatment governs what happens to the ULA when the customer is acquired, divested, or restructured. The standard Oracle position is that an acquisition by another entity terminates the ULA and that any extension of the unlimited deployment to the acquirer requires a new ULA. The buyer side position is to negotiate a defined period during which the unlimited deployment extends to the acquirer pending a renegotiation. The buyer side levers include the length of the transition period, the products covered during the transition, and the pricing of the post transition arrangement. The M&A treatment becomes material when the customer is contemplating a corporate transaction during the ULA term and is often overlooked when the customer is not.
Hidden clauses checklist
- Scope definition with named options and packs.
- Cloud deploy with fixed conversion methodology.
- M&A treatment with transition period and pricing.
- Support stream pricing after certification.
- Audit rights during the ULA term.
- Certification mechanics and Oracle script governance.
- Termination for convenience and divestiture rights.
- Most favoured customer provisions.
The support stream after certification.
The support stream after certification is the largest dollar item in the post ULA period. The standard Oracle position is that support continues on the certified quantity at the rate fixed in the original ULA contract, subject to the standard Oracle support uplift. The buyer side levers include a cap on the support uplift, a fix of the support rate at certification, and a defined right to reduce the support footprint at certification. The reduction right is particularly valuable. It permits the customer to certify a lower quantity than the maximum permitted under the contract, and to fix the support stream at the lower quantity. The reduction right is almost never offered without buyer side negotiation.
The audit rights during the term.
The audit rights during the ULA term govern what Oracle can audit during the unlimited deployment period. The standard Oracle position is that Oracle may audit at any time on reasonable notice and may audit all Oracle products, in scope and out of scope. The buyer side position is to limit the audit to out of scope products during the ULA term and to define a single certification audit at the end of the term. The buyer side levers include the audit notice period, the audit scope, the audit methodology, and the buyer side rehearsal right. The buyer side rehearsal right is the most valuable. It permits the customer to run the Oracle audit scripts in a controlled environment before the formal audit submission.
The certification mechanics.
The certification mechanics govern how the certified quantity is determined at the end of the ULA term. The standard Oracle position is that the certified quantity is the output of the Oracle discovery script. The buyer side position is that the certified quantity is the deployed quantity under the contract definition, which may differ from the script output. The buyer side levers include the script version control, the buyer side rehearsal right, the documentation requirements, and the dispute resolution process for certification disagreements. The certification mechanics are covered in detail in our ULA true up process explainer.
Related resources.
- ULA Negotiation pillar guide
- ULA Negotiation service
- Contract Review service
- ULA deal type page
- Oracle Database product page
- The ULA Exit Framework 49 page reference paper.
- Oracle ULA Cloud Deploy Rights related sub article.