Oracle Unlimited license agreement

Oracle ULA Certification FAQs

Oracle ULA Certification FAQs

Oracle ULA Certification FAQs

Q41: What is Oracle ULA certification?

A: Certification is the required process at the end of a ULA term. You formally declare to Oracle the quantity of each product you have deployed under the ULA so that you can convert those deployments into perpetual licenses. Essentially, it’s how you “exit” the ULA.

On the Certification Date (usually the day the ULA expires or shortly after), you must provide Oracle a certification letter, signed by a C-level executive, that lists the counts of each unlimited product deployed (often measured in standard license metrics like processor counts or user counts).

Oracle will then review and validate those numbers (they might have their LMS team audit or verify the figures). Once Oracle accepts them, those numbers become your fixed license entitlements in the future, documented in an amendment or confirmation. The ULA agreement typically contains a certification clause spelling out this requirement.

The certification must encompass all deployments as of the end date of the ULA. It’s a one-time opportunity to capture everything you’ve deployed.

Think of it like this:

  • During the ULA, you filled up a bucket with deployments.
  • Certification is when you pour that bucket out, count everything in it, and put tags on them saying “these are now our perpetual licenses.”

If done correctly, you walk away with licenses to cover your current usage (and you continue paying support on those). If done incorrectly (missed some, counted wrong), you might not have enough licenses, or Oracle may dispute it.

Certification is critical—it’s an audit, and purchasing true-up is rolled into one final step. Once certified, the ULA ends; you no longer have unlimited rights but those perpetual licenses.

Oracle ULA certification is not automatic – you must actively perform it and comply with the contractual procedure.

Read Oracle ULA Renewal FAQs – Money and Control.


Q42: How do we prepare for ULA certification?

A: Start early and be thorough. Ideally, begin preparations at least 6-12 months before the ULA expiration.

Key preparation steps:

Inventory All Deployments – Conduct a comprehensive scan of your environment for ULA-covered products. Document every installation, instance, and where it’s running (which servers, how many cores, etc.). Use software asset management tools and consider Oracle’s measurement tools (but possibly run them yourself first).

Verify Metrics – Understand how each product is licensed (Processor, Named User Plus, etc.) and gather the necessary data. Example:

  • For processor-based licensing, note CPU core counts and processor types (for Oracle’s core factor if applicable).

Consolidate and clean up – Uninstall any unnecessary deployments before the end date.

  • Strategy: Many firms remove unused instances to lower counts while simultaneously deploying needed software to maximize certified numbers.

Internal Audit – Cross-check findings by location and with different teams.

  • Why? Some departments might have stood up Oracle instances without centralized tracking.
  • Include development/test environments (as Oracle often requires licensing for them unless using special free licenses).

Documentation – Keep a detailed record of how you arrived at the numbers. This helps if Oracle asks questions later.

Engage Teams – Ensure all relevant IT teams know the ULA is ending.

  • Freeze changes around the end date so you have a stable count.

Consider Professional Help – If unsure, engage an Oracle licensing expert. They can:

  • Run scripts to verify you didn’t miss anything.
  • Ensure you interpret Oracle’s rules correctly (especially for tricky areas like virtualization).

A 12-month lead time is ideal, but if you have a few months, you can still get things in order.

Essentially, treat preparation as if you were going to be audited on the last day of the ULA – because that’s what certification is.

Read Oracle ULA Negotiations FAQs.


Q43: What are the steps in the ULA certification process?

A: The process can be broken down into five key steps:

1️⃣ Review Contractual Obligations

  • Know your contract terms (when and how to certify).
  • Typically, you must certify within 30 days after the ULA term ends.
  • A C-level exec must sign the certification letter verifying deployment counts.

2️⃣ Data Collection

  • Gather deployment data (inventory of all instances).
  • Run Oracle LMS scripts or internal tools to get accurate counts.
  • Fill out Oracle’s Global Deployment Report template, listing each product and license counts.

3️⃣ Submission of Certification Letter

  • Submit the certification letter signed by a C-level executive (CFO, CIO, etc.).
  • The letter typically states:” We certify that as of [date], we have X processors of Oracle Database Enterprise Edition deployed, Y processors of WebLogic Server deployed, etc.”

4️⃣ Oracle’s Verification

  • Oracle’s LMS team may audit or validate reported figures.
  • They may request logs, scripts, or sample server data for verification.

5️⃣ Certification Acceptance and License Grant

  • Once Oracle is satisfied, they will formally accept the certification.
  • Oracle will issue a confirmation letter listing the final perpetual licenses.
  • At this point, the ULA ends, and those licenses are now your fixed entitlements.

Q44: When exactly do we need to certify?

A: Certification is typically required at the end of the ULA term, with a 30-day grace period for submission.

  • The contract often states:”On the Certification Date (the end date of the Unlimited Deployment Period), you shall furnish Oracle with a certification…”
  • Early certification is generally not recommended because:
    ✅ You want to maximize deployments before the end date.
    ✅ The certification must reflect deployments as of the last day of the ULA.

Q45: What information does Oracle require in the certification?

Oracle will require:

  • Quantities of each Unlimited Deployment Program installed at the ULA end date.
  • Breakdown by standard license metrics (e.g., processors, Named User Plus).
  • Possibly, breakdown by location (if required in the contract).
  • C-level executive signature, verifying the accuracy of the data.

Q46: Who needs to sign the ULA certification?

A: A C-level executive (typically the CFO, CEO, or CIO).

Oracle requires a high-ranking officer’s signature to confirm the legality and accuracy of the certification.


Q47: What are common mistakes to avoid during ULA certification?

🚨 Top mistakes that can lead to licensing issues:

  • Under-counting deployments – Missing instances means being under-licensed post-certification.
  • Rushing the process – Certification should be thoroughly validated before submission.
  • Relying solely on Oracle’s scripts – Oracle’s LMS tool might detect non-ULA products that could cause compliance issues.
  • Including incorrect data – Reporting non-ULA products or duplicating counts can complicate certification.
  • Missing the deadline – Failing to submit the certification letter on time could mean losing your unlimited rights.

Q48: How can we track Oracle deployments throughout the ULA term?

Implement Software Asset Management (SAM) practices.
Regularly run Oracle’s LMS tools or internal tracking scripts.
Conduct internal audits every 6 months.
Ensure IT teams track all new deployments.
Perform a test-run certification before the ULA ends.


Q49: What role does Oracle LMS play in certification?

  • Oracle LMS will likely engage 3-6 months before ULA expiration.
  • They may offer to run scripts, but remember: their goal is Oracle’s interest, not yours.
  • Many companies hire third-party Oracle licensing experts to verify LMS findings.

Q50: What should we do after we’ve certified our ULA?

  • Obtain formal certification documentation from Oracle.
  • Ensure support contracts reflect new perpetual licenses.
  • Educate IT teams that unlimited deployment is over.
  • Plan for future growth and compliance.

Do you want to know more about our Oracle ULA Optimization Service?

Please enable JavaScript in your browser to complete this form.
Author
  • Fredrik Filipsson has 20 years of experience in Oracle license management, including nine years working at Oracle and 11 years as a consultant, assisting major global clients with complex Oracle licensing issues. Before his work in Oracle licensing, he gained valuable expertise in IBM, SAP, and Salesforce licensing through his time at IBM. In addition, Fredrik has played a leading role in AI initiatives and is a successful entrepreneur, co-founding Redress Compliance and several other companies.

    View all posts