Oracle ULA Certification Countdown
Your Oracle Unlimited Licence Agreement has a fixed end date. After certification, you're locked in to whatever you deployed. This tool helps you track your deadline and maximise every deployment before it's too late.
Your ULA Timeline
Your Results
| Milestone | Date | Days Away |
|---|
Enter your ULA dates and click "Calculate My ULA Timeline" to see your results.
What Happens at Oracle ULA Certification
A ULA (Unlimited Licence Agreement) allows deployment of specific Oracle products with no per-unit licence count during the term — typically 3 years. This flexibility makes ULAs valuable during rapid deployment phases, digital transformation, or technology migrations where final architecture isn't yet determined.
At the end of the ULA term, Oracle runs a certification process using GLAS (Global Licensing Advisory Services) scripts to count your actual deployments. This is not a simple measurement — it's a comprehensive audit where Oracle's tooling scans your environment for every instance of every in-scope product.
Whatever count Oracle measures at certification becomes your perpetual licence entitlement. You must purchase licences for exactly that count. This is permanent. If you've under-deployed relative to what you needed, you lose the ULA benefit — you're locked in forever at a potentially insufficient licence count.
If Oracle's GLAS scripts find deployments you didn't count, Oracle may claim additional licence fees and back-maintenance. The certification is not a routine measurement — it's a high-stakes negotiation where Oracle's agenda is to maximise their post-ULA revenue. Without expert preparation and independent verification, most organisations either under-deploy (leaving value on the table) or face surprise additional costs.
ULA Deployment Maximisation Checklist
- Audit your entire infrastructure — find every Oracle deployment across dev, test, production, and DR environments. Include on-premises and cloud. Most organisations discover 30-40% more deployments during this audit than they initially estimated.
- Include virtual machine deployments — ULA covers virtualised instances of in-scope products. A single VM host can run multiple Oracle instances, all covered by ULA.
- Deploy to new data centres if planned — ULA gives you unlimited deployment rights. If you've planned a new DC, build it before certification.
- Enable licensed options in scope — if Diagnostics Pack is in your ULA, ensure it's enabled everywhere it's needed. You paid for it through the ULA; use it.
- Consolidate RAC deployments before certification — RAC counts differently to standalone DB. Oracle's counting methodology favours larger consolidated clusters.
- Check subsidiary coverage — most ULAs cover named entities only. If you have subsidiaries, confirm whether they're included. If not, you may be able to add them before certification.
- Run a pre-certification GLAS simulation — understand what Oracle will measure. Many organisations are surprised by the GLAS count. Running simulation early gives you time to remediate if needed.
- Challenge Oracle's Core Factor calculations — errors in processor equivalency are common. Verify factors against current Oracle documentation.
- Document everything independently before submitting to Oracle — your own measurement protects you in disputes. If Oracle's GLAS count differs materially from yours, you have grounds to challenge.
- Engage expert advisors — our team has certified 40+ ULAs with zero failed certifications. Expert guidance eliminates costly mistakes.
Oracle ULA certification is one of the most consequential Oracle events your organisation will face. Our ULA Advisory service has delivered zero failed certifications across 40+ ULA engagements.
The Five Mistakes That Destroy ULA Value
1. Under-deploying before certification
Leaving value on the table permanently. If you deploy only 50 processors before certification, you're locked in at 50 forever — even if you planned for 200. This is a multi-million-dollar cost.
2. Missing subsidiary deployments
Units outside the named entities in your ULA aren't covered in certification. Many organisations discover months after certification that subsidiary deployments should have been included.
3. Trusting Oracle's GLAS count without verification
Errors favour Oracle. If GLAS counts 100 processors and you measured 80 independently, you have grounds to challenge. Without independent measurement, you can't defend your position.
4. Not certifying at all
Automatic rollover or default Oracle position can be worse than an agreed certification. The status quo becomes Oracle's interpretation of your entitlement.
5. Certifying too early
Rushing certification before all planned deployments are counted. You can't go back. Once certified, the count is permanent.
Real-World Certification Success
A major global manufacturer successfully certified their Oracle ULA covering Database Enterprise Edition, Real Application Clusters, and Partitioning across 47 legal entities. Through comprehensive infrastructure audit and independent GLAS simulation, we identified and documented 38 additional processor cores across subsidiary operations and development data centres that had not been counted in the initial Oracle scope proposal.
The certification captured $4.2M in additional deployment value above Oracle's initial certification count. This reflects the real-world impact of expert preparation. Read the full case study.
Explore Our Other Tools
Oracle Audit Risk Assessment
Assess your exposure to Oracle audit and compliance risks. Understand your vulnerability profile and identify immediate remediation priorities.
Use Tool →Oracle License Savings Estimator
Estimate potential licence cost reduction through consolidation, cloud migration, or re-architecture strategies specific to your environment.
Use Tool →Oracle Processor Factor Calculator
Calculate accurate Oracle processor factors for your infrastructure. Verify license counts against current Oracle documentation.
Use Tool →Go Deeper: Our Oracle ULA Certification Handbook
Download our Oracle ULA Certification Handbook — the definitive guide to counting methodology, GLAS script defence, subsidiary coverage, and how to maximise your ULA value before certification.
Download White Paper (PDF)