Few estates arrive at the certification window with perfect records. Patchy histories do not have to cost you entitlement, provided you rebuild the picture from the right sources, in the right order, before time runs out.
By Daniel Voss · Ex Oracle LMS · 4 June 2026
Incomplete records do not prevent a ULA certification, but they change the work and the timeline. You rebuild a deployment picture from the sources that do exist, such as discovery tools, configuration databases, virtualisation exports, backups, and procurement records, then reconcile it to your contract and assemble an evidence file. The goal is a count that is both complete and defensible. The earlier you start, the more you can recover and the more legitimate deployment you can still count before the window closes.
It is easy to imagine that other organisations arrive at certification with a tidy, complete inventory of every Oracle instance, neatly dated and fully evidenced. They do not. Across multi year terms, teams change, tools are replaced, estates migrate, and the documentation that once existed scatters or disappears. The realistic starting point for most certifications is partial. The question is never whether your records are perfect. It is whether you can rebuild a complete and defensible picture from what remains, and whether you start early enough to do it well.
This matters because the consequences of an incomplete count cut both ways. Deployment you cannot find is entitlement you fail to certify and lose forever. Deployment you certify but cannot evidence is exposure that can surface in a later audit. A patchy record does not just risk leaving value uncaptured. It risks both undercounting what you own and overclaiming what you cannot prove. The remedy for both is the same disciplined reconstruction, and it is entirely achievable with the sources most estates still hold.
You triangulate. No single source survives a long term intact, but several partial sources together can reconstruct a reliable picture. The method is to gather every source that touches the Oracle estate, cross reference them to resolve gaps and conflicts, and document the basis for each conclusion so the result is defensible. The sources below are the ones most organisations can still draw on even when the formal inventory is gone.
A gap in your records is a gap in your evidence, and an unevidenced number is a weak number whether it is too high or too low. Rebuild from multiple sources, document the basis of every figure, and you replace a fragile guess with a position you can defend.
Order matters when records are incomplete, because each step narrows the uncertainty for the next. The sequence below is indicative and would be tailored to the estate, but it shows the logic of moving from what you know to what you can defend.
| Step | Source | What it establishes |
|---|---|---|
| 1 · Anchor | Current discovery scan | What runs now |
| 2 · Extend | Virtualisation and CMDB | Where it sits and how it is structured |
| 3 · Confirm history | Backups and monitoring | That systems ran within the term |
| 4 · Date it | Procurement and change | When deployment occurred |
| 5 · Reconcile | The contract | What is in scope and countable |
Indicative sequence. Which sources are available and how much each contributes depends on the estate. What counts within the term and within scope depends on your specific agreement.
Reconstruction takes time, and time is the one input you cannot manufacture once the window is open. Consider an anonymized logistics operator that approached its certification with fragmented records after several infrastructure migrations. Because it began the reconstruction many months ahead, it was able to recover backup catalogues, correlate them with procurement records, and evidence deployments that a last minute scramble would have missed entirely. The same work attempted in the final weeks would have yielded a thinner, less defensible count, and the difference would have been permanent.
Early reconstruction also preserves your options. When you find legitimate deployment that your contract does not currently count, perhaps because of where it runs, you may still have time to move it so that it does. When you find exposure, you have time to address it deliberately rather than discover it in the certification exchange. The estates that handle incomplete records best are not the ones with the best documentation. They are the ones that started the rebuild while there was still room to act on what they found.
Incomplete records are a workload, not a verdict, and the work is most productive when there is time to do it properly. Set the foundation with our Oracle ULA certification guide, get the declaration right with what the certification letter must contain, and avoid the errors that compound later in the certification mistakes that haunt you later.
Book a ULA assessment and we will reconstruct your deployment from the sources you still hold, reconcile it to your contract, and build the evidence behind every figure.