Editorial photograph of a contract and signature pad on a boardroom desk, representing the Oracle ULA certification process
Article · Oracle · ULA Certification

Oracle ULA Certification. The 90 day window that decides the next decade.

The ULA certification window converts unlimited deployment rights into a fixed, perpetual entitlement. This article maps the certification math, the evidence pack, and the seven exit levers.

Read the Framework Oracle Hub
90 daysCertification window
a leading industry analyst firmRecognized
Industry Recognized
500+ Enterprise Clients
$2B+ Under Advisory
11 Vendor Practices
100% Buyer Side Independent

An Oracle ULA (Unlimited License Agreement) is a fixed term contract that grants unlimited deployment rights on a defined product list for a 3 or 5 year term. At the end of the term, the customer either renews the ULA or certifies.

Certification converts the unlimited deployment quantity at the end of the term into a fixed, perpetual entitlement on each product in scope.

The 90 day certification window is the single most important decision point in an Oracle ULA. The certified quantity locks the customer entitlement for the next decade or longer.

Read this alongside the Oracle hub, the ULA negotiation guide, the audit help guide, and the Vendor Shield subscription.

Key Takeaways

What every Oracle ULA owner needs to know about certification

  • Certification converts unlimited to fixed. The peak deployment quantity at the end of the term locks as perpetual entitlement.
  • The 90 day window is contractual. The customer has 30 days to declare intent and 60 more days to deliver the evidence pack.
  • Evidence is granular. Per host, per processor, per option. The pack is the same data an LMS audit script would produce.
  • Pre certification deployment is the lever. Deploy maximum legitimate workload before the certification date.
  • Cloud counts in some ULAs, not others. Read the cloud carve out clause. AWS, Azure, OCI treatment varies by contract generation.
  • Diagnostics and Tuning are licensed by option. Every option on the ULA product list certifies separately by processor.
  • Renewal beats re ULA on most estates. Certify, then negotiate a fresh ULA against the certified quantity baseline.

How Oracle ULA certification works

The ULA contract defines a fixed term, a product list, and a set of entities granted unlimited deployment rights. At the end of the term, the customer must either certify or renew.

The certification mechanic, step by step

  1. Notice of intent. Inside 30 days of the term end, the customer declares intent to certify or renew.
  2. Deployment freeze. No new ULA product installation after the term end date.
  3. Evidence collection. Per host, per processor, per option, every ULA product in every entity.
  4. Certification letter. Inside 60 days of the notice, deliver the certified quantities to Oracle in writing.
  5. Oracle acceptance. Oracle reviews and accepts. Disputes resolved through the contract clause.
  6. Perpetual entitlement. The certified quantity becomes the customer's perpetual entitlement going forward.

Why customers certify versus renew

  • Certify when growth has plateaued. The estate is mature, deployment is stable, and a fixed entitlement covers forward needs.
  • Renew when growth continues. A second ULA term covers the next growth phase at a known unit cost.
  • Certify then ULA fresh. The hybrid play. Certify the existing ULA, then negotiate a new ULA on a fresh product list using the certified base as evidence.

The 90 day certification timeline

The certification window is structured. Every day inside the window carries a different lever and a different risk.

Day by day certification timeline

WindowActivityBuyer side priority
T minus 12 monthsPre certification planningInventory, deployment plan, evidence framework
T minus 6 monthsMaximum legitimate deploymentBuild out every covered workload before the meter freezes
T minus 3 monthsMock certification runRun the evidence pack internally, surface gaps
Term endDeployment freezeNo new ULA product installation
Day 1 to 30Notice of intentDeclare certification path in writing
Day 31 to 90Evidence pack and letterDeliver the certified quantities to Oracle
Day 91 onwardOracle reviewManage challenges and disputes through contract terms

The deployment evidence pack

The certification letter is supported by a deployment evidence pack. The pack mirrors what an Oracle LMS audit script would produce.

Evidence pack content, by product

  • Oracle Database. Per host, per processor, per option (Partitioning, Advanced Compression, Diagnostics, Tuning, RAC, Active Data Guard).
  • WebLogic. Per host, per processor, per edition (Standard, Enterprise, Suite).
  • Middleware suite. SOA, BPM, Coherence, OBIEE, OEM by product, by edition, by processor.
  • Applications. E Business Suite, PeopleSoft, JD Edwards by user count and module.

Per host evidence requirements

  1. Hostname and operating system version.
  2. Physical CPU count and core count.
  3. Virtualization layer. Type 1 hypervisor, partitioning, container, bare metal.
  4. Oracle product, edition, and version installed.
  5. Options installed and used. A query of DBA_FEATURE_USAGE_STATISTICS captures the usage history.
  6. Legal entity ownership of the host.

Certified quantity math

The certified quantity is the peak deployment quantity at the end of the term, calculated per Oracle's processor licensing rules.

Processor calculation rules

  • Core factor. Apply the Oracle Processor Core Factor Table to the physical core count.
  • Sub capacity not granted. A ULA typically licenses to the full physical capacity of the host, not the virtual partition.
  • Hard partition exception. Approved hard partitioning technology (Solaris zones, IBM LPAR with capping, Oracle VM with pinning) limits the count.
  • Options layered. Each option certifies at its own processor count, often lower than the base Database.

The two common counting errors

  • VMware over count. The estate runs Oracle on 200 VMware hosts in a cluster. The audit position counts all 200. The buyer side documents cluster pinning and counts only the pinned hosts.
  • Diagnostics under count. Diagnostics Pack runs on 80 hosts, but every host with the Diagnostics Pack option enabled certifies. The DBA_FEATURE_USAGE_STATISTICS query catches the usage trail.

Worked example. 5,000 processor estate certification

A regional bank ran a five year ULA on Database Enterprise Edition with Partitioning, Advanced Compression, Diagnostics, Tuning, and RAC. The estate grew from 1,800 to 4,200 deployed processors over the term, against a list of 5,000 budgeted.

Pre certification optimization

  • Documented deployment plan. 600 additional processors slated for a planned data center migration in the final 90 days.
  • Cluster pinning audit. 240 over counted processors on a VMware cluster pulled out of the certification count through documented pinning.
  • Options usage audit. Diagnostics Pack enabled on 180 hosts, but only used on 80. Disable on non production hosts before certification.

Certified quantity, line by line

Product / OptionPre cert deploymentOptimization adjustmentCertified quantity
Database Enterprise Edition4,200 processorplus 600, minus 2404,560 processor
Partitioning3,800 processorplus 6004,400 processor
Advanced Compression2,100 processorplus 2002,300 processor
Diagnostics Pack180 processorminus 10080 processor
Tuning Pack180 processorminus 10080 processor
Real Application Clusters1,400 processorplus 1001,500 processor

Forward value of the certified base

  • 4,560 processor Database Enterprise Edition at 47,500 USD list per processor represents 216 million USD list entitlement.
  • Support obligation. 22 percent annual support on net acquisition cost, capped at the ULA support amount unless renegotiated.
  • Forward leverage. The certified base is the entry point for a new ULA, a cloud commit, or a support reset conversation.

Seven levers in any ULA certification

The seven levers procurement carries into the 90 day window

  1. Pre certification deployment plan. Document and execute legitimate growth before the term end.
  2. Cluster pinning evidence. Hard partitioning, VMware affinity rules, documented topology.
  3. Options usage audit. Disable unused options on non production hosts before the freeze.
  4. Cloud carve out reading. Confirm AWS, Azure, OCI treatment under the contract generation.
  5. Evidence pack quality. Customer owned, counsel reviewed, delivered in defensible format.
  6. Renewal lever. Trade the certified base for a fresh ULA on the next product set, often at a discount on the certified value.
  7. Support reset lever. Convert the certified base into a support reset conversation, often pairing with a cloud migration commitment.

What to do next

The eight step checklist takes an Oracle ULA from 12 months out to a certified entitlement.

  1. Open the planning window 12 months out. Inventory, deployment plan, growth roadmap.
  2. Build the deployment evidence framework 6 months out.
  3. Execute legitimate maximum deployment 3 to 6 months out.
  4. Run a mock certification 90 days out to surface gaps.
  5. Deliver the notice of intent inside 30 days of term end.
  6. Compile the evidence pack under counsel direction.
  7. Submit the certification letter inside the 90 day window.
  8. Open the forward ULA, support, or cloud conversation against the certified base.

Frequently asked questions

What happens if we miss the 90 day certification window?

The contract typically converts the ULA into an audit position. Oracle has the right to run a full LMS audit, count every deployed processor, and bill at list price for any gap. The buyer side outcome ranges from a sharp commercial settlement to a multi million dollar shortfall.

Set calendar reminders 6 and 3 months out. Engage advisor and counsel 12 months out for any ULA over 1,000 processors.

Can cloud deployment count in the certified quantity?

Cloud carve out language varies by ULA generation. Most pre 2020 ULAs do not count AWS and Azure deployments in the certified quantity. Most post 2020 ULAs allow AWS and Azure under authorized cloud environment terms.

The OCI exception is universal. Oracle Cloud deployments under the ULA count in the certified quantity and benefit from BYOL conversion mechanics at the end of the term.

What is the difference between a ULA and a PULA?

A ULA is a 3 or 5 year unlimited deployment contract that ends in certification or renewal. A PULA (Perpetual ULA) is a perpetual unlimited deployment contract with no certification event. PULAs are priced 3 to 6 times higher than equivalent ULAs and lock the customer into Oracle for the duration of the contract.

Most enterprise estates do better with a 3 to 5 year ULA cycle, certifying and re ULAing as growth and product mix evolves.

How does Oracle audit a certified quantity?

Once certified, the customer enters a standard license audit posture. The certified quantity is the entitlement, the LMS scripts measure deployment, and the gap (if any) becomes the audit position. Documented certification math is the buyer side defense.

Most certified estates run an internal compliance check 6 months after certification to confirm the position is defensible against an LMS letter.

Can we exit Oracle Database during a ULA?

The ULA grants unlimited deployment on the contracted products. It does not preclude exit to PostgreSQL, Aurora, or other alternatives during the term. The exit reduces the certified quantity at term end, which lowers the forward perpetual entitlement.

Exit projects often pair with ULA certification at a lower certified base, plus a forward year support reduction. The trade off is forward flexibility versus support cost.

How does Redress engage on Oracle ULA certifications?

Redress runs Oracle ULA advisory inside the Vendor Shield subscription, the audit defense services, and on engagement basis 12 months out from term end. Every engagement is led by a former Oracle commercial professional on the buyer side.

The output is a deployment plan, an evidence framework, a mock certification run, a certified quantity memo, and a forward ULA, support, or cloud commit position memo.

How Redress engages on Oracle ULA certifications

Redress runs Oracle ULA advisory inside the Vendor Shield subscription, the audit defense services, the Software Spend Assessment, and the Renewal Program.

Read the related Oracle hub, the Oracle services page, the ULA negotiation guide, the Oracle PULA reference, the PULA versus ULA explainer, the PULA exit playbook, the audit help guide, the benchmarking page, the about us page, and the contact page.

Score your Oracle ULA readiness in under five minutes.
Open the Checklist →
White Paper · Oracle

Download the Oracle ULA Decision Framework.

Buyer side reference on Oracle ULA certification. The 90 day window, the evidence pack, certified quantity math, cloud carve out reading, and the seven levers procurement carries to the exit.

Independent. Buyer side. Written for CIOs, CFOs, procurement leaders, and licensing professionals carrying an active ULA approaching the certification window. No Oracle kickback. No conflict on the table.

Oracle ULA Decision Framework

Open the white paper in your browser. Corporate email only.

Open the Paper →
90 days
Certification window
3 to 5 yr
Standard ULA term
500+
Enterprise Clients
$2B+
Under advisory
100%
Buyer side

The Oracle ULA certification is won in the 12 months before term end, not the 90 days after. Customers who wait for the notice to start work surrender 30 to 50 percent of the achievable certified quantity.

Director, IT Vendor Management
European retail group, 4,500 processor ULA
More Reading

More from this practice.

Oracle Hub →
Oracle ULA Negotiation Guide
Oracle · Article
Oracle ULA Negotiation Guide
Master reference on ULA structure and exit.
18 min read
PULA versus ULA
Oracle · Article
PULA versus ULA
When the perpetual ULA pays for itself.
14 min read
Oracle PULA Exit Playbook
Oracle · Playbook
Oracle PULA Exit Playbook
Exit the perpetual ULA without losing entitlement.
20 min read
Oracle Audit Help
Oracle · Article
Oracle Audit Help
What to do in the first 72 hours after the LMS letter.
16 min read
Oracle Knowledge Hub
Oracle · Hub
Oracle Knowledge Hub
Master Oracle licensing reference.
22 min read
Editorial photograph of enterprise contract negotiation strategy

Certify the Oracle ULA at the right base. Independent advisors, end to end.

We have run 500+ enterprise clients across 11 publishers. Every engagement starts with one conversation.

Oracle ULA intelligence, monthly.

Certification math, deployment plan patterns, evidence pack templates, cloud carve out reads, and ULA settlement plays from every Oracle engagement we run on the buyer side.