When you submit an Oracle ULA certification, Oracle reconciles your declared count against what it knows about your estate and tests whether each deployment is in scope and meets the contract conditions. A number backed by a clean evidence file survives that review. A number without support invites questions.
By the Meridian advisory team, former Oracle LMS and GLAS licensing analysts. Updated 4 June 2026.
Oracle approaches a certification as a reconciliation. It compares the count you declare against the picture it already holds of your environment, built from your support records, your past orders, any prior measurement, and the named products in your agreement. It tests whether the deployments you count sit inside the customer definition and the territory clause, whether cloud and virtualized deployments meet the specific conditions in your contract, and, where the agreement requires measurement scripts, whether that requirement was met. The review is not a rubber stamp and it is not, by default, an audit. It is a check that the number you are asking Oracle to convert to perpetual licenses is consistent and supportable.
Oracle reviews for consistency and scope. A count that matches the evidence and respects the clauses passes quickly. A count that jumps without explanation, or rests on deployments the contract does not clearly cover, draws questions and delay.
Oracle has a partial view of your estate before you submit anything. A certified count that is wildly different from that view, in either direction, invites scrutiny. A higher number is legitimate when growth and proper counting explain it, but the explanation needs to be ready. A lower number can suggest deployments were missed or moved. The job before submission is to understand how your number relates to Oracle's likely picture, so that any gap is one you can account for rather than one you have to discover under questioning.
The reviewer checks that the deployments behind your count belong to entities the agreement covers and sit in territories the agreement reaches. Deployments in an acquired company outside the customer definition, or in a country outside the territory clause, are the classic points of dispute, especially after corporate change during the term. These are decided by the exact wording of your agreement, which is why scope is read and resolved before the letter is written, not argued at the review.
Where your count includes public cloud, the reviewer tests it against the cloud clause: the named providers, any requirement that a deployment run for 365 continuous days, and any baseline cut off. Where your count includes virtualized estates, partitioning is in play, because Oracle treats soft partitioning as not limiting the scope of a deployment. Both areas are contract specific and evidence heavy, and both are places where a count can be questioned if the supporting documentation does not match the claim.
If your contract requires Oracle LMS scripts, the reviewer expects to see that measurement. If it does not, you are entitled to certify on your own methodology, and the reviewer will look at how the number was produced. A documented, repeatable method that explains how processors were counted, how core factors were applied, and how non production and disaster recovery instances were treated stands up far better than a bare number. The method is part of the evidence.
Oracle can question a count and ask for evidence, and it can dispute specific deployments it believes fall outside scope or fail the cloud and virtualization conditions. What it cannot do is convert a number you have not declared, which is why the count you submit matters so much. The practical reality is that a count backed by a clean evidence file and a defensible methodology is hard to move, while a count submitted without support is an invitation to negotiate it down. The asymmetry favours the prepared. This is the same evidence discipline that protects you in the audit window after certification, where the file behind your number is your defense.
| Stage | What Oracle does | What protects you |
|---|---|---|
| Submission | Receives the certification letter and count | A complete, signed declaration |
| Reconciliation | Compares the count to its own records | An explanation for any gap |
| Scope test | Checks entities, territory, cloud, virtualization | Clauses read and resolved beforehand |
| Questions | Asks for evidence on specific deployments | The evidence file, ready to produce |
| Close | Confirms the perpetual entitlement | A documented, defensible position |
The exact sequence and intensity depend on your agreement, your products, and your history with Oracle, so treat this as the shape of a review rather than a fixed procedure.
The review is won before it starts. The work is to understand your own number, to resolve scope questions inside the term, and to assemble the evidence that supports every deployment you count, so that when Oracle asks, the answer is already on the page. We set out how to build that file in preparing the certification data room, and how to bring the whole exit to a clean close in the certification closing checklist. The full process sits in our pillar, the Oracle ULA certification guide.
Oracle reviews a certification to confirm the number is consistent with what it knows and supportable under your clauses. It can question deployments and ask for evidence, so the count you submit should already carry its proof. Understand your number against Oracle's likely view, resolve scope before you write the letter, and have the evidence ready. A prepared certification passes review. An unprepared one becomes a negotiation you did not plan to have.
Oracle reviews whether the certified count is consistent with what it knows about your estate, whether the deployments are in scope under the customer and territory clauses, and whether cloud and virtualized deployments meet the contract conditions. Where a contract requires LMS measurement, it checks that too. The review is a reconciliation, not a rubber stamp.
Oracle can question a certified count and ask for evidence, and it can dispute deployments it believes fall outside the contract scope or conditions. A number backed by a clean evidence file and a defensible methodology is far harder to challenge than one submitted without support, which is why the evidence is prepared before the letter goes in.
Book a confidential assessment and we will build the count and the evidence behind it before Oracle ever sees the letter.