Certification is not the end of audit risk. It is the start of the window where Oracle is most likely to check the count. We defend your certified position with the same evidence file that justified it, so a routine review never becomes a remediation bill.
Certification converts your deployed quantities into a fixed perpetual entitlement and ends the unlimited right. From that moment, any deployment beyond the certified count is unlicensed unless you buy more. Oracle knows this, which is why audit risk rises in the first two years after exit. The defense is not a clever argument made under pressure. It is the evidence file built during certification: the server lists, the tool output, and the methodology documentation that justify every number you declared.
A certified count is only as strong as the evidence behind it. We treat the audit as a documentation exercise you already won, not a negotiation you are forced to enter.
Three things decide whether a post certification audit closes cleanly. The first is the evidence file that maps each certified number to the deployments behind it. The second is scope control, so the audit examines the certified entitlement and the period that actually matters, not a fishing expedition across the whole estate. The third is a single point of contact, so Oracle receives one consistent narrative rather than fragments from engineers answering questions in isolation.
We reconstruct or maintain the file behind the certified count: inventory of servers and clusters, core counts with the applicable core factors, options and packs usage, and the methodology that produced each total. Where a certification was run without us, we rebuild this file before the audit reaches the count.
We define what is in scope, manage what data leaves the building, and ensure measurements are framed correctly before they reach Oracle. Soft partitioning, virtualization boundaries, and disaster recovery instances are handled with documentation rather than assumption, because an undocumented cluster is where exposure is manufactured.
One channel to Oracle keeps the narrative tight and the findings on your terms. We respond to LMS and GLAS requests, challenge unsupported claims, and keep the conversation anchored to the certified entitlement.
Real growth happens, and it is not the same as a measurement error. We separate the two. Where deployment genuinely exceeded the certified count, the answer is new licenses bought deliberately on the smallest defensible terms, not a panic renewal of the ULA that hands Oracle a fresh unlimited fee. Where the apparent gap is a counting artifact, soft partitioning swept too widely, or instances double counted, we resolve it with evidence and the gap closes without a purchase.
The figures below are indicative and illustrate the mechanics only.
| Item | Oracle initial position | Defended position |
|---|---|---|
| VMware cluster sweep | 96 processors claimed | 40 processors, isolation documented |
| Disaster recovery instances | Counted as extra | Within certified entitlement |
| Genuine growth | Bundled into the demand | 12 processors, licensed deliberately |
In an illustration like this, most of the apparent exposure dissolves under documentation, and only the genuine growth is purchased, on terms you choose rather than under a deadline.
Defense is strongest when certification was done well. See how the count is built and documented in the ULA exit strategy guide and the certification service. For the broader audit picture, read about Oracle audit defense across LMS and GLAS.
A certified number with no evidence behind it invites Oracle to set its own. The file you keep is the file that closes the audit.
Without documented isolation, an entire VMware cluster can be claimed. Dedicated hosts and clean records keep scope where it belongs.
Real growth bundled with measurement noise becomes a single large demand. Separating the two shrinks the bill to what is genuinely owed.
Certification converts deployed quantities into a fixed perpetual entitlement and ends the unlimited right. Oracle has a commercial interest in testing whether deployment grew beyond the certified count, so audit risk rises in the first two years after exit. The evidence file behind the certified number is the defense.
The evidence file: server lists, tool output, and methodology documentation that justify every certified number. With a documented baseline, scope control, and a single point of contact, the certified position holds and growth questions are answered on facts rather than assumption.
Growth beyond the certified count needs new licenses bought deliberately, not a panic renewal of the ULA. We quantify the true gap, separate genuine growth from measurement error, and resolve it on the smallest defensible terms.
Book a confidential assessment and we will review the certified position, rebuild the evidence file if needed, and take the conversation with Oracle off your desk.