Reviewers look in the same places every time: unisolated virtualization, cloud counted against the wrong conditions, unlicensed options in use, out of scope deployments, and numbers with no evidence. These are the errors that move money, and almost all of them are cheap to close before you submit.
By the Meridian advisory team · Ex Oracle licensing analysts · Updated June 2026
The list is short because the money is concentrated. A reviewer checking a ULA certification gravitates to virtualization that was never isolated, cloud deployments counted without meeting the contract's conditions, database options and management packs in use outside the licensed scope, deployments sitting in an entity or territory the agreement does not cover, and certified numbers with no evidence behind them. These five areas are where certifications most often go wrong, in both directions, which is exactly why they attract scrutiny. Knowing the list is half the defense, because every error on it can be closed before the submission ever reaches a reviewer.
Run your own review before Oracle runs theirs. The same five errors that cost customers at the table are visible to anyone who looks for them in advance. Find them early and they are corrections. Find them late and they are concessions.
Under Oracle's partitioning stance, soft partitioning does not limit scope, so an Oracle instance on a shared cluster can, in Oracle's view, require licensing across every host the cluster can reach. This is the error reviewers most enjoy finding, because it can multiply the footprint. The fix is isolation: place Oracle on dedicated hosts, bound the environment, and document the topology before the measurement point. Cluster design cannot be unwound in the final weeks, so this is an early move.
Cloud counting is contract specific. Many ULAs require deployments in AWS or Azure to run for 365 continuous days to count toward the certification baseline, and some exclude public cloud entirely. Contracts are often silent on Google Cloud, and silence is not inclusion. Counting cloud that does not meet your conditions is an error, and failing to count cloud that does meet them surrenders entitlement. The fix is to read the cloud language in your own contract and count exactly to it.
Options and packs are easy to enable and easy to forget, and usage of one outside your named scope is exposure rather than entitlement. A reviewer can probe for it. The fix is to account for option usage honestly during preparation and keep deployment inside the scope your agreement actually grants.
The customer definition, the entity list, and the territory clause all bind the right. A deployment in a subsidiary or territory outside scope can trigger a remediation demand rather than add to the count, and this risk rises sharply after a merger or acquisition. The fix is to reconcile the estate against the scope language before certifying, so nothing out of scope is in the count and nothing in scope is missed.
A certified number that cannot be traced to a server list, tool output, and a written methodology is a question waiting to be asked, both at the review and in the two years of raised audit risk that follow. The fix is to build the evidence file as you build the count, so every number has a source behind it.
It is tempting to read this list as only Oracle's advantage, but that is not the full picture. Two of these errors, missed cloud that genuinely counts and conservative virtualization, cost the customer by undercounting legitimate deployment and surrendering permanent entitlement. The others create exposure by overcounting without evidence or counting outside scope. A proper review works both sides: it captures everything you are entitled to claim and removes everything you cannot defend. The goal is not the highest number or the lowest, it is the complete, defensible number.
Take an anonymized example with indicative figures. A manufacturer ran an independent review before submitting and found three of the five errors live in its draft: a shared cluster that had never been isolated, a set of Azure instances counted without meeting the 365 day condition, and a recently acquired subsidiary deploying outside the entity scope. It isolated the cluster, recounted cloud to the contract, and resolved the subsidiary before certifying, turning three future concessions into three quiet corrections. A comparable firm submitted without a pre review and met all three at the table, from the weaker side. The drafts were similar. The timing of the review was not.
Every error on this list is cheaper to fix at the draft stage than to argue at the table, and most are invisible until someone looks for them deliberately. An independent pre certification review run against your own contract is the most direct way to find them while they are still corrections. Read processor counting rules at certification to understand how these errors move the number, and server lists, screenshots, and tool output to build the evidence that closes the fifth one. When you want your draft reviewed before Oracle sees it, our Oracle ULA certification guide is the pillar that covers counting and certification in full.
Reviewers focus on a short list: unisolated virtualization that should sweep in more hardware, cloud deployments counted without meeting the contract conditions, unlicensed options and management packs in use, deployments outside the entity or territory scope, and certified numbers with no supporting evidence. These are the errors that move money, so they get the attention.
Measure independently, isolate Oracle workloads before the measurement point, read the cloud and scope language in your own contract, account for option usage honestly, and evidence every number with server lists, tool output, and a written methodology. Most errors are cheap to fix before submission and expensive to discover afterward.
No. Some errors cost the customer by undercounting legitimate deployments and surrendering permanent entitlement, while others create exposure by overcounting without evidence. A good review corrects both, capturing what you are entitled to and removing what you cannot defend.