Full narration of the briefing. Click a section heading to jump the player to that moment.
Here is what a certification dispute usually looks like, and it is not what people expect. It is not fraud and it is rarely bad faith. It is two organisations counting the same estate by different rules and arriving at different numbers, both honestly. The rules that produce that gap are the ones nobody wrote down at signature, because at signature everyone was focused on price.
I am Tom, Claire is with me, and this session is the five places those gaps appear and how to close each one before it matters.
Dispute one is virtualisation, and it is the oldest argument in Oracle licensing. The question is not where a database is running today. It is where it could run. Under Oracle's traditional position on soft partitioning, if a virtual machine can move across a cluster, the licensable footprint is the whole cluster rather than the host it happens to sit on.
That single interpretation can multiply a count several times over, in either direction. So the technical facts do not settle it. The contract does, and if your ordering document is silent on how virtualised environments are counted, you are negotiating that at the least convenient moment.
Dispute two is public cloud, and it is now the most common. In our experience, cloud deployment counting was disputed in roughly half of the engagements we see running Oracle Database in public cloud. Half. That is not an edge case, it is the norm.
The questions are specific: does authorised cloud deployment count toward certification at all, how are virtual cores converted to processor licences, and which cloud providers are recognised. Every one of those has a contractual answer, and the answer differs by agreement. Read yours before you build your submission, not after Oracle responds to it.
Disputes three and four are environments. Disaster recovery: a passive standby has different treatment from an active one, and the distinction rests on details like whether it is mounted, how often it is opened for testing, and how long failover runs. Development and test: they generally consume licences under Oracle's rules, but organisations routinely leave them out of a submission because they feel like they should not count. That is entitlement you already hold, thrown away by an assumption.
Include them, evidence them, and let the contract decide what they are worth rather than deciding it for yourself.
Dispute five is anything running on somebody else's infrastructure. Outsourced data centres, managed service providers, partner hosted applications, and systems a supplier runs on your behalf. The question is who holds the licence and whose count it belongs to, and the answer lives in a contract that is often not the Oracle one. It is also the category most likely to be missed entirely, because the servers are not on your network, the invoices come from a third party, and nobody internally thinks of them as your Oracle estate.
They may well be, and at certification they are either entitlement or exposure.
Now the fix, and it is the same for all five. Address certification methodology in the agreement itself rather than at certification time. Write down how virtualised environments are counted, whether and how public cloud deployment counts, how disaster recovery and non production are treated, and what evidence will be accepted. That is a paragraph in an ordering document, negotiated when both sides want the deal to close, which is the moment of maximum goodwill.
The alternative is arguing the same points three years later when the answer is worth millions and the person who sold you the ULA has moved on.
The move from this briefing: take your ordering document and answer five questions from it in writing. How is virtualisation counted. Does public cloud count and at what ratio. How are disaster recovery and non production treated.
What evidence is acceptable. And who counts hosted systems. Any question your contract does not answer is a dispute waiting to happen, and knowing which ones are open is how you prepare for them. Next session: the certification window itself, the thirty to ninety days that fix your position for a decade.
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