What the certification letter must contain.

The document that ends the term

A short letter with permanent consequences

At the close of a ULA, the unlimited deployment right ends and is replaced by a fixed quantity of perpetual licences. The certification letter is how that replacement is declared. It is usually a short document, a page or two, but it carries the weight of the entire agreement. The numbers it states become the licences you own forever. Anything you deployed but did not declare is lost. Anything you declared but cannot support later becomes exposure. The brevity of the letter is deceptive, because nothing else in the ULA lifecycle has such a direct and lasting effect on what you hold.

Because the letter is a contractual instrument, its required form is not a matter of convention. Your agreement contains a certification clause that specifies what the letter must say, when it must be delivered, and who must sign it. That clause is the authority, not any template Oracle or anyone else circulates. The first task in any certification is to read that clause closely and build the letter to satisfy it precisely, because a letter that misses a contractual requirement can be rejected or reopened.

What does the Oracle ULA certification letter need to include?

While the exact requirements are contract specific, certification letters share a common backbone. Read your clause first, then expect to provide each of the following elements in the form your agreement requires.

• Identification of the agreement. The letter references the specific ULA by its contract number and effective dates, so there is no ambiguity about which agreement is being certified.
• The certifying entity. It names the customer entity certifying, which must align with the customer definition in the agreement. This is where scope provisions quietly enter the letter.
• Each product being certified. Every product within the unlimited grant is listed by its licensed name, so the entitlement that results is unambiguous.
• The deployed quantity per product. For each product, the number of processor licences or Named User Plus licences deployed as of the certification date. This is the core of the letter and the figure that becomes perpetual entitlement.
• The effective certification date. The date the counts are measured against, which the contract usually ties to the end of the term.
• An authorised signature. The signature of an officer with the authority the clause requires, commonly a C level executive, attesting that the declared figures are accurate.

Why the signature level matters

Most ULAs require the letter to be signed by a senior officer of the customer, frequently a C level executive such as the chief financial officer or chief information officer. This is not a formality. The signature is an attestation that the declared numbers are accurate, and it is made by someone whose authority binds the organisation. That is precisely why the figures must be settled before the letter reaches the signer. An executive should never be asked to attest to a number that has not been independently measured and reconciled, because the attestation, not the spreadsheet behind it, is what Oracle relies on and what an auditor will later test.

In practice this means the certification letter is the visible tip of a much larger body of work. Behind the single figure for each product sits a deployment measurement, a reconciliation to the contract scope, and an evidence file that can stand up to scrutiny. The signer is entitled to assurance that all of this exists and holds together. Providing that assurance, rather than simply producing a letter to a deadline, is the difference between a clean certification and one that returns as an audit finding.

A simple anatomy, indicative

The table below shows the typical structure of the declaration at the heart of the letter, using indicative figures for an anonymized example. The real format follows your contract, and the numbers are yours to measure and defend.

Indicative only. Options and packs are certified on their own deployment, which is often lower than the database itself, so each line is measured separately rather than assumed to match.

The next step

The certification letter is the closing act of a process that begins long before it is written, and the quality of the letter reflects the quality of the count behind it. Start with the full picture in our Oracle ULA certification guide, learn what Oracle probes before it accepts the letter in the questions Oracle asks at certification, and understand the errors to avoid in the certification mistakes that haunt you later.