Oracle ULA True Up Process.

What the true up actually is.

The Oracle Unlimited License Agreement true up is the contractually defined process by which the unlimited deployment under the ULA is converted into a fixed perpetual entitlement at the end of the ULA term. The conversion is one way and the certified quantity is the entitlement that the customer carries forward into the post ULA world. Annual support continues on the certified quantity at the rate fixed in the original ULA contract, subject to the standard Oracle support uplift. There is no opportunity to revisit the certified quantity once the certification is filed and accepted.

The terminology around the process varies. Oracle calls it certification. Procurement teams call it true up. The contract calls it certification of usage. The underlying mechanic is the same. The customer measures the deployed quantity of each in scope product at the certification date and submits a signed declaration to Oracle. Oracle reviews the declaration and either accepts it or challenges it. Once accepted, the certified quantity becomes the perpetual entitlement.

The certification timing.

The certification timing is fixed in the ULA contract. Most ULAs require the certification to be filed within thirty days of the ULA expiry date. Some ULAs permit certification at any point in a window that opens ninety days before expiry. Customers planning to certify out should know the exact certification window before the ULA enters its final year. The certification timing also has tax and accounting implications. The perpetual entitlement is recognised on the balance sheet at the certified quantity and the support stream continues from the certification date forward.

The counting methodology.

The counting methodology is product specific. Database is counted by processor under the Oracle Processor Core Factor Table that applies at the date the deployment was made. Application licenses are counted by named user or by application user metric. Middleware is counted by processor. Each product has its own specific counting rule and the rules interact in ways that are not always obvious. A WebLogic deployment on a database cluster, for example, may need to be counted under both the WebLogic processor rules and the database processor rules.

The Oracle script.

Oracle provides a discovery script that is run on the customer environment as part of the certification. The script collects deployment data and produces a report. The script is run by the customer, not by Oracle, but Oracle reviews the output. The script is not the contract. The contract defines the certifiable quantity. The script is a measurement tool. There is a structural difference between what the script reports and what the contract permits to be certified. Buyer side preparation includes reconciling the script output against the contract definition of certifiable quantity. Discrepancies are documented and resolved before submission.

The negotiation opportunities.

The true up creates several negotiation opportunities. The first is the negotiation of the certifiable quantity itself. The Oracle position is the script output. The buyer side position is the contract definition. The reconciliation is a negotiation. The second is the negotiation of the support stream. The certified quantity carries forward at the ULA support rate. The Oracle position may be to apply a refresh of the support rate at certification. The buyer side position is that the support rate is fixed in the original ULA contract and continues forward unchanged. The third opportunity is the negotiation of the post ULA contract structure. The certification can be paired with a follow on agreement that restructures the perpetual entitlement or extends the unlimited deployment.

The buyer side rehearsal.

The buyer side rehearsal is the most important step in the true up process. The rehearsal runs the Oracle discovery script in a controlled environment and produces a draft certification output. The draft is reviewed against the contract, against the deployment inventory, and against the cloud provider attestations. Discrepancies are categorised as script artefacts, contract interpretation differences, or deployment data errors. Each category has its own resolution path. Script artefacts are resolved by rerunning the script with corrected parameters. Contract interpretation differences are resolved by buyer side legal review. Deployment data errors are resolved by environment correction. The rehearsal is repeated until the buyer side reconciled quantity matches the contract definition of certifiable quantity.

The post certification discipline.

The post certification discipline is the second most important step. The certified quantity becomes the entitlement and the deployment must be managed to stay within the certified quantity. Deployments above the certified quantity are out of compliance and create audit exposure. The post certification discipline includes a deployment inventory, a change control process for new deployments, and a periodic reconciliation against the certified quantity. The discipline is not optional. The first Oracle audit after certification is typically scheduled within twenty four months of the certification date.

Related resources.

• ULA Negotiation pillar guide
• ULA Negotiation service
• ULA deal type page
• Oracle Database product page
• The ULA Exit Framework 49 page reference paper.
• Oracle ULA Cloud Deploy Rights Explained related sub article.
• Oracle ULA Hidden Clauses to Watch related sub article.