Oracle's contracts say you cannot transfer licenses, and in the United States that position largely holds. In the EU, the UsedSoft judgment says otherwise for perpetual licenses bought outright, but the practical outcome, including what happened to UsedSoft itself, is far messier than resellers admit.
Oracle's contracts say you cannot transfer licenses, and in the United States that position largely holds. In the EU, the UsedSoft judgment says otherwise for perpetual licenses bought outright, but the practical outcome, including what happened to UsedSoft itself, is far messier than resellers admit.
Start with the paper, because every secondary-market conversation ends there. Oracle's Online Transactional OMA (document reference lic-online-toma-us-eng-v040119) states it plainly: "You may not assign the Master Agreement or give or transfer the Programs, Operating System, Integrated Software and/or any Service Offerings or an interest in them to another individual or entity." Note the drafting. It is not just assignment of the agreement that is blocked, it is the transfer of "an interest in" the Programs, which is deliberately broad enough to capture creative structures such as sub-licensing, hosting arrangements, or a share-purchase dressed up as a license move. Schedule H tightens it further for hardware-adjacent entitlements, granting a "limited, non-exclusive, royalty free, non-transferable, non-assignable right to use Integrated Software delivered with the Hardware." If your target asset is an Exadata or ODA stack, the integrated software riding on it is contractually welded to the original customer, and no broker invoice changes that.
Now the sentence that pays for the rest of this article. Schedule P of the same paper applies the prohibition "except to the extent that such prohibition is rendered unenforceable under applicable law." Oracle wrote its own legal ceiling into its own contract. That carve-out is the hook every EU secondary-market seller hangs its pitch on, and it is genuine, but it is a limitation on enforceability, not an affirmative grant of transfer rights. In twenty-five years of negotiating this vendor's paper, I have never seen Oracle voluntarily concede a transfer post-signature that was not already documented in an ordering document or amendment. The operating rule is simple: the contractual default is no transfer, and any deviation must exist in writing, signed by Oracle, before money moves. Read our detailed breakdown of what you can actually move, sell, or reassign under Oracle contracts before you take a broker's word for it. Transfer and assignment provisions are negotiable at signature, alongside virtualization rights, audit scope, and support fee caps. They are effectively unbuyable afterward.
Oracle wrote its own legal ceiling into its own contract, and that carve-out limits enforceability, it does not grant you a transfer right.
The second wall is definitional. Oracle defines the licensed customer as the contracting legal entity plus its majority-owned subsidiaries, meaning ownership above 50 percent. Everything flows from that threshold. An entity you acquire tomorrow is not automatically covered by your OMA, which means the acquisition target's Oracle estate does not inherit your pricing, your discounts, or your rights, and its deployments do not become compliant simply because you now own it. Symmetrically, a business you divest loses its rights the moment ownership drops below the majority threshold. The licenses do not follow the servers, the people, or the P&L. They stay with the contracting entity, and the departing business becomes an unlicensed user overnight unless something has been signed.
The transition mechanics are unforgiving. Standard Oracle terms permit a divested entity to keep using the programs under the seller's agreement for a short transition period, commonly 90 days, after which it must buy its own licenses at list, from a standing start, with no accumulated discount history and no leverage. In my experience, this is where buyers discover the real cost of a carve-out deal, typically after the transaction services agreement has already been signed and the negotiating window has closed. The fix has to be pre-negotiated. One global retailer added an OMA clause permitting a one-time license transfer to an acquirer in a divestiture, and that single sentence later let the divested division keep running its Oracle databases without a forced repurchase. At minimum, insist on language stating Oracle will not unreasonably withhold consent to a transfer.
This is exactly why the standard seller pitch collapses. "We have 40 surplus processor licenses to offload" assumes a license block can be split, but partial carve-outs of a block are rarely permitted without Oracle's written agreement, and Oracle has no commercial reason to agree. Splitting also creates support chaos: CSI numbers, renewal streams, and the matching service levels policy do not divide cleanly. If a transfer is genuinely on the table, the artifact you demand is the Oracle License Assignment Document, executed by Oracle, not a reseller's purchase order or a lawyer's opinion letter. Anything less and you have bought an audit finding. Before engaging any intermediary, understand the real pros and cons of working through an Oracle license reseller, because their incentives and your compliance exposure are not aligned.
On 3 July 2012 the Court of Justice of the European Union handed down Case C-128/11, UsedSoft GmbH v Oracle International Corp, and it remains the only authority that seriously dents Oracle's transfer prohibition. The holding is narrow and technical: the copyright holder's exclusive distribution right in a computer program is exhausted on the first sale of the program or of a licence to it, and that exhaustion applies irrespective of whether the copy arrived as a download or on physical media such as a DVD or CD-ROM. The court's own press release put it in plain language: an author of software cannot oppose the resale of his used licences allowing the use of programs downloaded from the internet. The practical consequence for anyone reading Oracle paper in Europe is that the clause reciting the programs are non-transferable and non-assignable does not automatically hold. Oracle itself concedes the ceiling in Schedule P of its Online Transactional OMA, where the prohibition applies "except to the extent that such prohibition is rendered unenforceable under applicable law." That sentence is the entire European argument, and it is Oracle's own drafting.
Now the scope conditions, which resellers quote selectively. Exhaustion applies only where the licence was granted in return for a one-off fee and conferred the right to use the copy for an unlimited period. That is a perpetual licence bought outright and nothing else. It excludes subscriptions, term licences, Unlimited License Agreements during their term (the certification event, not the ULA itself, is where perpetual entitlements crystallise), Java subscription metrics, and every SaaS product Oracle sells. Two further conditions bite hard. First, maintenance and support are not exhausted: the CJEU treated the maintenance agreement separately, and exhaustion extends only to the copy originally sold. Support does not travel with the licence. Second, the seller must uninstall and render its own copy unusable at the point of sale. A seller that keeps running the software has not exhausted anything, it has made an unauthorised copy, and the buyer inherits that defect. Before you rely on any of this, read our detailed breakdown of what Oracle licenses you can actually move, sell, or reassign, because the contractual mechanics matter more than the case law once Oracle sends the audit letter.
Exhaustion covers the licence, not the support contract, and Oracle knows exactly which of those two you actually need.
Here is the outcome nobody puts in the sales deck. After winning the reference at the CJEU in 2012, UsedSoft did not walk away with a functioning business model. The German proceedings ground on, and the litigation ultimately ended with UsedSoft withdrawing its appeal and signing a cease-and-desist undertaking after roughly eight years of argument. The company that won the landmark European software resale case stopped resisting. That is the fact pattern buyers need to hold in their heads: a favourable ruling on a legal principle is not the same thing as an enforceable commercial position. The CJEU decided an abstract question about the distribution right. It did not decide whether your specific block of forty processor licences, sourced through a broker in Rotterdam, with a support contract that terminated in 2019 and an unverifiable uninstall attestation, is validly transferred. That question gets decided in a national court, over years, at your expense.
Understand who funds that fight. The broker takes a margin at the point of sale and moves on. When Oracle's audit team, or LMS under whatever name it now trades, opens a review and refuses to recognise the entitlement, the party sitting on unusable software, an unlicensed production estate, and a back-support demand is the buyer. In our negotiation practice the pattern is consistent: Oracle does not sue the reseller, it invoices the end customer, because the end customer is the one with the running database and the audit clause. Compare that exposure to the risk profile of buying through Oracle's own channel, covered in our assessment of what an Oracle license reseller actually gives you, and the arbitrage on a used block looks a lot thinner.
Splitting a licence block remains genuinely unresolved. In Adobe v UsedSoft (18 December 2012, AZ. 11 U 68/11) the German court examined a set of forty licences carrying a single uniform serial number and had to decide whether that set could legitimately be divided among different buyers. Pointing the other way, the Court of First Instance in Ghent in Flexsoft v Desatel (26 January 2015, Case No 2012/AR/3254) confirmed UsedSoft applies and held that exhaustion is not confined to one physical copy but can extend to multiple licence keys delivered to a reseller expressly for resale. Two national courts, two directions, no CJEU tiebreaker. If your proposed purchase involves a partial block carved out of a larger original order, assume the point is contested and price the litigation risk into the discount, or walk.
If you are going to buy used Oracle licenses anyway, treat the transaction the way you would treat buying a building with no title deed. The seller's confidence is not evidence. Brokers routinely present a purchase invoice, a signed statement of uninstallation, or a notarised affidavit and call that a chain of title. Oracle recognises none of those. The only artifact Oracle's own process produces is the Oracle License Assignment Document, executed by Oracle alongside the underlying Master Agreement, ordering document, amendments and support renewals. If the seller cannot produce a countersigned assignment, you are not buying licenses, you are buying a legal argument that you will have to run yourself, in a European court, against Oracle's counsel, several years after your deployment is already in production. Everything below the assignment document is verification of whether the underlying transfer even qualifies under the exhaustion doctrine: perpetual grant, one-off fee, EU first sale, EU resale, and full extinguishment at the seller. Miss any one of those five and the CJEU reasoning in Case C-128/11 does not reach you.
| What to verify | Acceptable evidence | Why it kills the deal if missing |
|---|---|---|
| Original ordering document plus signed OMA, seller named as licensee | Full PDF set, unredacted entity name, order number, CSI | Without the named contracting entity, you cannot prove first sale to that party |
| Perpetual grant, not term or subscription | Ordering document showing unlimited duration | UsedSoft exhaustion applies only to perpetual grants for a one-off fee |
| One-off licence fee actually paid in full | Paid invoice and proof of settlement | Unpaid or instalment fees defeat the "sold" characterisation |
| First sale occurred in the EU or EEA, resale also in EU or EEA | Original order territory, seller and buyer entity registration | US first sale means no exhaustion, and the contract prohibition stands |
| Written proof of uninstallation and deletion at the seller | Signed technical attestation plus decommission evidence and audit logs | If the seller still runs the copy, both parties are unlicensed |
| Whether the block is being split | Original quantity versus quantity offered | Splitting a set remains contested, see Adobe v UsedSoft (AZ. 11 U 68/11) versus Flexsoft v Desatel (2012/AR/3254) |
| Support contract status and CSI history | Renewal invoices, CSI numbers, lapse dates | Determines reinstatement exposure and back-support arithmetic |
| Prior Oracle audit or LMS correspondence at the seller | Audit closure letters | Inherited disputes attach to the estate you are buying |
State this to your board in plain words before signing anything: Oracle's LMS or Global Licensing and Advisory Services will treat any deployment it cannot tie to an Oracle-recognised entitlement record as unlicensed, regardless of what the seller, the broker, or the broker's lawyer told you. The audit script does not include a step where the auditor evaluates CJEU case law on your behalf. In our experience advising buyers through these transactions, the deals that survive scrutiny are the small number where the seller was a divesting European group with a clean single order line, and Oracle was engaged in writing before money moved.
Assume the best case. The transfer is clean, the assignment document is signed, the exhaustion argument holds. You still have a serious problem: support does not travel with the license. The CJEU was explicit that exhaustion extends only to the copy originally sold and that the maintenance agreement is not exhausted. So the buyer inherits an entitlement with no CSI, no patch access, no Critical Patch Updates, and no right to future versions. Two paths follow, and both are expensive. Run unsupported, which for a Database Enterprise Edition estate means you are consuming quarterly CPUs you are no longer entitled to receive, an unacceptable position for most regulated firms and most cyber insurers. Or negotiate a new support contract, at which point Oracle reprices the support base from list, not from the discounted price the original owner paid, and adds reinstatement fees plus back-support for the lapsed period.
The arithmetic is the part resellers skip. Say a broker offers 50 Database Enterprise Edition processor licenses at 60 percent off list, and list is 47,500 dollars per processor. You save roughly 1.4 million dollars against a fresh Oracle order at the same discount you could probably have negotiated anyway. Then Oracle prices support at the standard 22 percent of the list value, roughly 522,500 dollars per year, rather than 22 percent of a discounted net. Add reinstatement and back-support for the lapsed interval and the first-year cash outflow commonly lands between 700,000 and 900,000 dollars. In our negotiations, the acquisition saving is typically erased inside two to three years, and after that the buyer is carrying a permanently inflated support base with no discount protection and no cap on the annual uplift.
A used license bought at 60 percent off, then supported at 22 percent of list, is a discount you rent for two years and then pay back forever.
Compare that against where recovered spend actually sits. Terminating genuinely unused licenses and repricing the remaining support base produces cash without any transfer risk, any audit exposure, or any dependence on a foreign court. Costco removed 4.2 million dollars of annual Oracle support through termination and repricing, and LVMH took out 10.5 million euros across three years on the same mechanism. Before you spend a quarter on secondary-market diligence, model termination and repricing on your existing estate. That is almost always the larger number, and it is the one Oracle cannot litigate away.
Treat resale as the last item on the list, not the first. Before any broker conversation, count what you actually own: pull every ordering document, OMA, amendment and support renewal, then run a deployment reconciliation against entitlements. In our experience most organizations chasing the secondary market discover their real problem is not surplus licenses to sell but unreconciled deployments they cannot prove. Once you have a clean position, the two levers that reliably produce cash are termination of genuinely unused licenses and repricing of the support stream, both of which Oracle will contest but both of which work without depending on any third party's title. Redress clients have taken seven and eight figure amounts out of support this way, including Costco's 4.2 million dollar reduction and LVMH's 10.5 million euro program. Neither required a transfer.
If a transfer is unavoidable, negotiate it at signature or renewal, never afterward. Oracle presents standard terms as fixed, but transfer and assignment provisions are routinely modified in ordering document special terms. Ask for a one-time transfer right on divestiture, the pattern a global retailer used to let a divested division keep running Oracle without repurchasing, and at minimum a clause that Oracle will not unreasonably withhold consent. On the buy side, never wire funds without the executed Oracle License Assignment Document in hand: a broker invoice, a chain-of-title affidavit and a deletion certificate are not the same instrument, and Oracle will not honor them at audit. Our guide on what you can actually move, sell, or reassign sets out the verification sequence.
In the EU, the CJEU held in UsedSoft v Oracle (C-128/11) that Oracle's distribution right is exhausted on first sale, so perpetual licenses bought for a one-off fee can be resold within the EU. Outside the EU, notably in the United States, Oracle's contractual prohibition on assignment and transfer generally holds and there is no equivalent exhaustion doctrine for software licenses. The legality therefore depends entirely on the territory of original purchase and resale, not on what the broker's terms of sale claim.
Not without an Oracle License Assignment Document executed alongside the original OMA, ordering document and support renewals. Oracle's audit teams treat a broker invoice or a bill of sale as evidence of nothing, and undocumented deployments are recorded as unlicensed usage. If the seller cannot produce the original contract chain and Oracle has not signed off on the assignment, you are buying litigation risk, not entitlement.
Splitting is the most contested area. German courts questioned whether a license set covered by a single serial number could be divided, while the Ghent Court of First Instance in Flexsoft v Desatel accepted exhaustion across multiple license keys delivered for resale. Oracle's own position is that partial carve-outs are rarely permitted without written agreement, so any partial sale should be treated as high risk until Oracle signs an assignment document.
No. The CJEU expressly held that the maintenance agreement is not exhausted, so support does not travel with the resold copy. A buyer typically runs unsupported, meaning no patches, no critical patch updates and no right to new versions, or must negotiate a fresh support contract with Oracle, which usually means list-based fees plus reinstatement charges that eliminate the discount on the used license.
No. Exhaustion applies only where the right to use was granted for an unlimited period in return for a one-off fee. Term licenses, cloud subscriptions, SaaS entitlements and Unlimited License Agreements during their term all fall outside the UsedSoft scope. Only perpetual licenses paid outright are candidates, and even then the seller must fully uninstall its copies.
Reconcile deployments against entitlements first, because most organisations are already over-licensed in some products while under-licensed in others. Terminating genuinely unused licenses and repricing support has produced recoveries in the millions for large estates without any legal exposure. If you need transfer rights, negotiate them into the contract at signature or renewal rather than trying to buy your way out of a restriction later.
Oracle Analytics is sold as a perpetual per-processor server (OAS) and a per-OCPU cloud subscription (OAC). The prices, the metric math, and why the migration to OAC does not rever
Gated with a work email on the download page. No sales follow up you did not ask for.
Get the White Paper →
500+ enterprise clients. 11 vendor practices. Industry recognized. One conversation can change what you pay for the next three years.
One buyer side briefing a week. Renewal signals, audit moves, and the levers that work. No vendor spin.
