Full narration of the briefing. Click a section heading to jump the player to that moment.
The most uncomfortable finding in Oracle licensing is a compliance exposure inside a ULA. Customers assume the word unlimited means the audit conversation is over for three years, and then a review finds unlicensed deployment anyway. It happens regularly, and it is never because Oracle changed the rules. It is because deployment drifted outside boundaries that were written into the contract on day one and never read again.
I am Daniel, Claire is with me, and this session is the four boundaries and how estates cross them without anyone deciding to.
Boundary one is the product list, and it is the most common breach. Your ULA names specific products and specific options. If it is not named, it is not covered, no matter how naturally it belongs beside something that is. Database Enterprise Edition in your ULA does not carry Partitioning, Advanced Security, Diagnostics Pack or Tuning Pack unless each is listed.
Those options install easily, they get switched on by a DBA solving a real problem, and they are separately licensable. So take your ordering document and your actual deployed feature usage and compare them line by line, because that is exactly the comparison Oracle will make.
Boundary two is legal entity scope, and this is where corporate activity does the damage. A ULA covers the legal entities named in it. Not your group. Not every subsidiary.
Not the company you acquired in year two, whose data centre quietly started running your Oracle estate because integration was going well. Joint ventures sit outside by default, and so do entities you divested but continue to serve under a transition agreement. Every one of those is a normal business event that creates an abnormal licensing position, and none of them announce themselves. If your organisation buys or sells anything during a ULA term, that is a licensing event too.
Boundaries three and four are geography and environment. Many ULAs are scoped to named countries, so a deployment in an unlisted territory is outside the grant even though it is your company, your staff and your data. And environments: disaster recovery, development, test and integration all consume licences under Oracle's rules unless the contract says otherwise, and cloud regions can fall outside scope entirely. That last one matters most in 2026, because public cloud counting was disputed in roughly half of the engagements we see running Oracle Database in public cloud.
Not a technicality. A live argument with money attached.
Notice what all four have in common. Nobody decides to breach a ULA. A DBA enables a pack to fix a performance problem. An integration team stands up an instance in a new region because that is where the workload lives.
An acquisition is welcomed onto the shared platform because that is the point of acquiring it. Each decision is locally correct and made by somebody who has never read the ordering document, which is usually held by procurement or legal and not by anyone touching infrastructure. The gap is organisational, not technical, and it is why the fix is a process rather than a tool.
Here is why this matters more in a ULA than anywhere else, and it is the detail most people miss. Out of scope deployment does not simply sit there as a risk. At certification it counts for nothing, because you can only certify what the agreement covered. So you have carried the cost and the risk of running it, and at the end you receive no perpetual entitlement for it, and you may owe licences for it as well.
That is the worst of both outcomes, and it is entirely avoidable with a scope review that takes days rather than months.
The move from this briefing: build a four column check. Products listed against products deployed. Entities named against entities running Oracle. Territories listed against where it actually runs.
Environments covered against environments in use. One afternoon with your DBA team and your ordering document, and any gap you find now is a problem you can still solve rather than one you discover at certification. Next session: the perpetual version, the PULA, and why the missing certification day is the thing to price. See you there.
Redress Compliance works on contingency: our fee is 25 percent of what we save you. Nothing saved, nothing paid. Independent, buyer side only, never vendor funded. Want Redress to contact you? Reach out and we respond the same day.
Talk to a Oracle negotiator