The Oracle Unlimited License Agreement is sold as a clean entitlement that allows a buyer to deploy without counting for the term. The contractual reality is more complicated. The ULA carries a territorial scope clause that defines which legal entities and which geographies the deal covers. Deployments that fall outside the scope are not entitled. When the certification window opens the buyer is required to count entitled deployments only. Items outside the scope produce an entitlement gap. A buyer that ignored the territorial language at entry can arrive at certification with a perpetual entitlement that is materially smaller than the deployed footprint. The geography clause is therefore not a procedural detail. It is a structural component of the deal that should be examined at entry, monitored through the term, and reconciled at exit. This article describes the operational pattern for managing the geography clause.
The structure of the territorial scope clause.
The territorial scope clause typically appears in the product schedule and identifies the licensed territories by country or by region. The clause often names the parent entity and lists the affiliated entities that are within scope. The standard Oracle template lists territories at the country level. Some templates list regions such as North America, Europe Middle East and Africa, and Asia Pacific. The buyer should read the clause carefully and confirm that the listed territories match the actual deployment plan for the term.
The scope clause interacts with the deployment locations clause and the use rights clause. The deployment locations clause restricts where the software may be installed. The use rights clause restricts who may access the software. A buyer that wants global deployment with global user access needs all three clauses to align. A clause that names only the parent legal entity will not cover affiliates. A clause that lists only one region will not cover deployments in another region. The drafting language matters at the word level.
A common drafting failure is the use of the phrase Customer and its Affiliates without a definition of Affiliates that survives the term. Oracle template definitions of Affiliate often require a percentage ownership threshold and often exclude entities acquired after the effective date. Buyers should not accept a definition that excludes future acquisitions if the buyer expects acquisitions during the term.
Acquisitions during the term.
Acquisitions during the ULA term are the single largest source of geography related entitlement gaps. The acquired entity may use Oracle technology that was deployed under a separate contract or that was not contractually covered at all. The ULA scope may or may not extend to the acquired entity. Whether it does depends on the Affiliate definition and on the acquisition mechanics. A share purchase typically brings the target into the parent entity for the purposes of group definitions. An asset purchase does not.
Buyers that intend to grow through acquisition should negotiate an acquisition rider at entry. The rider should allow newly acquired entities to fall within the ULA scope automatically for a defined period after the acquisition closes. The rider should specify whether the acquired entity is permitted to continue running Oracle workloads it inherited and whether those workloads count toward the certification at exit. Without the rider every acquisition becomes a separate licensing conversation with Oracle and a potential audit exposure.
For the broader acquisition mechanics see the ULA exit strategy playbook and the stay versus exit cost model.
Cloud regions and the deployment location clause.
Cloud deployment introduces a second territorial question. The ULA was drafted at a time when on premises deployment was the dominant pattern. The scope clause typically names physical territories. Cloud regions are not territories in the same legal sense. A workload running in an AWS region located in Frankfurt is physically in Germany but is operated by the buyer from wherever the buyer is. Oracle has issued guidance over time that treats authorised cloud environments as deployment locations subject to the scope of the contract.
Buyers should confirm at entry whether the ULA permits deployment in the major hyperscaler clouds and whether each authorised cloud region falls within the licensed territories. Buyers should also confirm that the workload definition is not narrower than the buyer plan. Some ULA scope clauses limit deployment to production workloads. Others limit deployment to internal business operations. A buyer that intends to host a Software as a Service offering on top of Oracle technology will need broader use rights than a buyer that runs only internal operations.
See the Oracle Database product page for the technical scope considerations on Database workloads.
Joint ventures and shared infrastructure.
Joint ventures and shared services entities are the second most common source of entitlement gaps. A joint venture that is not majority owned by the buyer typically falls outside the standard Affiliate definition. If the joint venture uses Oracle technology that was deployed under the ULA the joint venture is using software it is not entitled to use. At certification the deployment in the joint venture is not counted toward the perpetual entitlement. The joint venture would need its own licence after term end.
Shared services entities that the buyer uses to deliver internal services to affiliates and to third parties present a similar problem. If the shared services entity operates as a captive of the buyer group it may or may not fall within the Affiliate definition. If the entity delivers services to third parties the deployment may fall outside the internal business operations restriction. Each shared services arrangement should be examined against the contract language and documented internally before certification.
Documentation discipline through the term.
A buyer that intends to certify cleanly at term end should maintain a deployment register through the term that records every deployment by legal entity, by physical location, and by cloud region. The register should be updated whenever new workloads are deployed and whenever the corporate structure changes through acquisition or disposal. The register is the source document for the certification count and the source document for the audit defence position if Oracle challenges the count.
The register should be accompanied by a scope log that records each scope question that arose during the term and the resolution. The scope log demonstrates that the buyer applied the contract language consistently. Where the scope question was resolved by an internal interpretation the log should record the interpretation and the reasoning. Where the question was raised with Oracle and resolved through correspondence the log should reference the correspondence.
The certification count and out of scope deployments.
At certification the buyer counts entitled deployments only. Items that fall outside the territorial scope, outside the Affiliate definition, or outside the use rights are excluded. The exclusions should be documented and explained in the methodology note that accompanies the certification letter. The methodology note should reference the contract clauses that produced the exclusions.
Out of scope deployments become unlicensed deployments at certification. The buyer has three options for each unlicensed deployment. Transition the workload to a licensed entity within the scope. Decommission the workload. Purchase a separate licence to cover the workload. The right option depends on the workload importance and on the commercial cost of each option. The decision should be made before the certification letter is signed.
Engaging an independent advisor.
The geography clause analysis benefits from an external perspective. An independent advisor that has reviewed many ULAs can identify scope ambiguities that an internal team would miss. The advisor can also draft contract language that closes the ambiguities at entry or that resolves them through an amendment during the term. For the certification window the advisor can sit alongside the internal team and review the deployment register against the contract clauses before the certification letter is drafted.
For the full ULA cluster see ULA Negotiation. For the service see ULA Negotiation. For the deal structure see the ULA deal page. For the full research read the Oracle ULA Exit Framework white paper.
The amendment process during the term.
A scope clause that is found to be too narrow during the term can be amended through a contract amendment. The amendment process is initiated by the buyer through the Oracle account team. The amendment is typically routed through Oracle deal desk and Oracle legal. The process can take several months and the outcome depends on the negotiation leverage at the time of the request.
The amendment is easier to obtain during a contract event such as a renewal or a new licence purchase. The amendment is harder to obtain as a standalone request because Oracle has no commercial incentive to add scope without consideration. Buyers should plan scope amendments to coincide with the next contract event. Where the scope gap is urgent and cannot wait for the next event the buyer should be prepared to provide commercial consideration in exchange for the amendment.
The amendment should be drafted to address the specific scope question rather than to expand the scope broadly. A broad amendment can trigger commercial demands that the buyer would prefer to avoid. A narrow amendment that resolves the specific question is typically more acceptable to Oracle and produces the buyer outcome with the least commercial cost.
A worked example.
A European industrial group entered a three year ULA in 2022 with a territorial scope that listed the European Union member states. The group acquired a manufacturer in the United Kingdom in 2023. The acquisition was a share purchase and the acquired entity used the Oracle Database for the manufacturing applications. The group treated the acquired entity as within the ULA scope because the United Kingdom had been part of the European Union until 2020.
At certification in 2025 the Oracle license management services team identified the United Kingdom deployment and asked for the contract basis for the deployment. The group could not produce a contract basis because the territorial scope clause referenced European Union member states by name and the United Kingdom was no longer a member state at the time of the deployment. The deployment was identified as an entitlement gap and was settled through a new licence purchase at the time of the certification.
The settlement was avoidable. A scope amendment at the time of the acquisition would have brought the United Kingdom into the scope and would have preserved the deployment for the perpetual entitlement. The group did not initiate the amendment because the internal team did not recognise the scope question. An external review of the territorial language at the time of the acquisition would have identified the question and would have produced a different outcome.