An Oracle ULA exit is a cross functional program, not an IT task. A complete certification needs IT asset management, infrastructure, procurement, legal, finance, and a C level executive to sign the letter. Naming these owners early, usually twelve to eighteen months before expiry, is what keeps the count complete and defensible.
By the Meridian advisory team · Ex Oracle licensing analysts · Updated June 2026
Six owners, working to one timeline. IT asset management holds the deployment data and the evidence file. Infrastructure and the virtualization team decide how Oracle workloads are placed, which directly drives the count. Procurement owns the Oracle relationship and any commercial exchange. Legal reads the contract that defines scope, entities, and territory. Finance owns the support line and the budget case. And a senior executive, usually at C level, signs the certification letter that turns deployment into permanent entitlement. Leave any one of these out and the certification tends to land short, late, or exposed.
The certification letter carries one signature, but the number behind it is built by a team. Treat the exit as a governed program with named owners, and you protect both the value you capture and the position you will have to defend afterward.
This is the spine of the program. The IT asset manager assembles the deployment inventory across databases, options, and management packs, gathers the tool output and server lists, and owns the methodology that turns raw data into a count. They are the people who know where the gaps are and who can chase the evidence that supports each number. When this role is weak or unassigned, the count is built on assumptions, and assumptions are exactly what fall apart in a later audit.
Where Oracle runs decides what gets counted. Under Oracle's partitioning stance, soft partitioning does not limit scope, so a virtualization team that spreads Oracle freely across a shared cluster can pull far more hardware into the count than the business actually uses. The same team, briefed early, can isolate Oracle onto dedicated hosts and document the boundary. This role needs to be engaged long before the exit window, because cluster design cannot be unwound in the final weeks.
Procurement owns the Oracle relationship and any renewal conversation that runs in parallel with the certification. They manage the commercial tempo, hold the line on timelines, and make sure the firm is not negotiating against itself. If a renewal quote appears, procurement is the function that treats it as an opening position rather than a fixed price, because renewal quotes typically move by twenty to forty percent once the firm shows it has a credible certification path.
The contract decides almost everything that matters at exit. Legal reads the customer definition, the entity list, the territory clause, and the cloud language, and tells the team what counts and what creates exposure. After a merger or acquisition, this reading becomes critical, because deployments inside an entity or territory outside scope can trigger a remediation demand rather than add to the count. Legal also owns the wording of the certification letter itself.
Finance owns the number that surprises people most: support. Support fees continue at the ULA level after certification regardless of how many licenses you certify, so a higher certified count is free value rather than a higher bill. Finance needs to understand this clearly, because the fear that certifying more raises support is a myth, and acting on that myth leaves entitlement uncaptured. Finance also frames the certify against renew business case in terms the board will recognise.
The certification letter is a formal declaration, and the contract typically requires a senior executive to sign it. That person is accepting personal and corporate responsibility for the numbers, so they need a count that is complete, reconciled to the contract, and supported by evidence. The signer should never be handed a letter cold. Their confidence is the output of everyone else's work, and a rushed signature on a thin count is how firms both lose value and inherit audit risk.
Timing matters as much as membership. The table below shows an indicative sequence for a ULA inside its final two years. Treat the months as a guide, not a rule, because the right lead time depends on the size of the estate and the complexity of the contract.
| Stakeholder | Bring in by | Owns |
|---|---|---|
| IT asset management | 18 months out | Deployment inventory and evidence |
| Infrastructure and virtualization | 18 months out | Where Oracle runs and how it is isolated |
| Legal and contracts | 12 months out | Scope, entities, territory, cloud terms |
| Procurement | 12 months out | Oracle relationship and commercial tempo |
| Finance | 9 months out | Support line and the certify versus renew case |
| Executive sponsor | Engaged early, signs at the end | The certification letter |
Figures are indicative and depend on the size of the estate and the specific contract.
The failure patterns are consistent. Without infrastructure engaged early, a shared cluster sweeps in hardware the business never needed, and the certified count is inflated in the wrong direction or, worse, the firm cannot defend it later. Without legal, a deployment in an out of scope subsidiary slips into the count and becomes a remediation demand at the table. Without finance, the support myth goes unchallenged and the team certifies a conservative number to avoid a cost increase that was never going to happen. Without procurement, a renewal quote is treated as a fixed price. And without an informed executive, the signature either stalls the program or rubber stamps a count nobody verified.
Consider an anonymized example. A large manufacturer treated its ULA exit as an IT project and assembled the count three months before expiry. The virtualization team had spread Oracle across a shared estate during the term, legal had never read the entity list against a recent acquisition, and finance assumed certifying more would raise support. The result was a count that was both incomplete on the products that mattered and exposed on an entity that should never have been in play. A second firm in the same sector ran the same exit as a governed program with the six owners named eighteen months out. It certified a complete, evidenced position and went into the next two years with nothing to remediate. The agreements were comparable. The governance was not.
If you are still mapping the basics, start with what an Oracle ULA is and how it works, then read what unlimited really means in a ULA so the team shares one understanding of what the exit converts. When you are ready to turn governance into a plan for your own estate, our Oracle ULA certification guide is the pillar that walks through the certification window in full.
A senior executive, usually at C level, signs the certification letter, because the letter is a formal declaration of deployed quantities that becomes your perpetual entitlement. That signer needs a complete, evidenced count in front of them, which is why the technical and commercial work has to finish well before the signature is asked for.
Name the owners twelve to eighteen months before expiry. The deployment, evidence, and contract review work all take time, and a virtualization or procurement decision made late can cost real count. Early formation is the single cheapest way to protect the value of the certification.
Rarely well. IT owns the deployment and the evidence, but procurement owns the Oracle relationship, legal owns the contract reading, finance owns the support and budget case, and an executive owns the signature. A count assembled without those roles tends to miss entitlement and create exposure.