Independent. Fixed-fee. 500+ Oracle engagements globally.
Your Oracle Unlimited Licence Agreement gives you the right to deploy Oracle products without limit during the term. When the term ends, the count you certify becomes your permanent perpetual entitlement. Oracle knows this. That is why Oracle's certification scripts, account managers, and standard advice systematically under-count deployable licences. Organisations that go through ULA certification without independent support regularly leave millions of pounds of licence value on the table permanently. This page explains how Redress Compliance's Oracle ULA certification service maximises that count — and protects it.
An Oracle Unlimited Licence Agreement allows you to deploy specified Oracle products without restriction during a fixed term — typically three to five years. At the end of that term, you must certify: declare the number of processor licences or Named User Plus licences deployed at a specific point in time. That certified count becomes your perpetual licence entitlement going forward.
The certification count is permanent. If you under-certify, you are under-licensed for every day after the ULA expires, and Oracle will use your own certification submission as the baseline for any future audit. If you over-certify, Oracle may challenge the submission. The process of getting this number right is not straightforward, and Oracle does not have an incentive to help you get it right.
Most organisations make three common mistakes in ULA certification. First, they rely on Oracle's own scripts to count their deployments — scripts that are designed to identify licenceable units in the way most favourable to Oracle, not necessarily most favourable to the client. Second, they certify only what is currently deployed rather than maximising deployments during the certification window for products they intend to use. Third, they do not challenge Oracle's methodology when Oracle disputes the submission.
Additionally, the ULA expiry decision itself — whether to certify and exit, or renew the ULA for another term — is a financially significant choice that most organisations make without modelling the long-term licence economics. Independent advice on this decision alone consistently delivers material value.
Related reading: our Oracle ULA strategy and exit guide covers the full ULA lifecycle, from agreement structure through to post-certification management.
We begin with a complete audit of your ULA agreement: which products are covered, which environments are in scope, and which deployment scenarios Oracle's LMS team would count versus challenge. Many ULA holders are not deploying the full range of products covered by the agreement. We identify every product that could be deployed before certification that would add to the certified count at no additional licence cost. On a recent engagement with a global insurance group, this discovery phase identified three Oracle products within the ULA that had not been deployed and added 14% to the final certified count.
We conduct an independent deployment analysis to establish the maximum defensible certified count. This includes reviewing virtualisation environments to ensure Oracle's processor counting methodology is applied correctly, identifying all Named User Plus users with access to Oracle systems, and capturing any deployments in subsidiary entities or geographies that fall within the ULA's geographic scope. We then compare our independent count to Oracle's own script output and identify every discrepancy worth challenging.
We model the financial case for certifying and exiting versus renewing the ULA for another term. This is a decision most organisations get wrong because they compare Oracle's renewal quote to the certified count without modelling future licence requirements, growth trajectories, or the cost of remaining on Oracle support for the certified estate. We produce a documented financial model that supports the decision and can be presented to a CFO or board. We then prepare the certification submission in the format most likely to withstand Oracle's review, with supporting deployment evidence.
Oracle frequently disputes certification submissions, particularly around virtualised environments. We manage every exchange with Oracle's LMS and account teams during this review process, presenting the technical and contractual basis for each element of the certified count Oracle challenges. We have successfully defended certification submissions that Oracle initially disputed by 30–40% of the total count, preserving the full value of the ULA for our clients going forward.
See also: our Oracle PULA exit strategy guide for organisations evaluating the Perpetual ULA option.
Clients typically certify 30–50% more Oracle licences than their initial unadvised count would have produced, through deployment maximisation, virtualisation methodology challenge, and subsidiary scope confirmation.
Average financial value of the additional certified licences delivered across Redress ULA certification engagements. For large enterprise ULAs, this figure runs materially higher — up to £15M on complex multi-product agreements.
Recommended lead time for engaging Redress before ULA expiry. Organisations that engage 12 months in advance consistently achieve better certification outcomes than those who engage at six months or less.
Oracle ULA certification is the process of declaring your Oracle software deployments at the end of an Unlimited Licence Agreement. The count you certify becomes your permanent perpetual entitlement. Under-certifying reduces your licence entitlement permanently. Over-certifying without documentation invites Oracle to dispute the submission. Independent advice on both the count and the process consistently produces materially better outcomes.
Redress engages on a fixed-fee basis for Oracle ULA certification. Most clients certify 30–50% more licences than they would without independent advice, with an average financial impact of £2–5M on the certified licence estate. The advisory fee is a small fraction of the value delivered.
Twelve months before expiry is the optimal engagement point. This allows time to identify deployable products, expand deployments where commercially beneficial, resolve compliance issues, prepare documentation, and model the renew versus exit decision before Oracle's account team begins its renewal push.
You will need your Oracle ULA agreement, the list of licenced products, current deployment inventory data, and any correspondence with Oracle about certification. We advise on what additional deployment evidence to gather and how to structure the submission to withstand Oracle's review process.
Yes. Mid-term ULA strategy includes deployment maximisation, monitoring ULA product scope for products not being fully used, and modelling the renew versus exit economics before Oracle begins the renewal conversation. Mid-term engagement consistently produces better certification outcomes than engaging at expiry alone.
Oracle frequently challenges certification submissions. Redress manages the dispute process: presenting the technical and contractual case for your certified count, challenging Oracle's counter-analysis, and negotiating the final agreed position. For ongoing coverage, consider our Oracle managed service which includes post-certification monitoring and dispute management.
If your ULA expires within 18 months, the decisions you make in the next 90 days will define your Oracle licence position for the next decade. Book a free 30-minute consultation to discuss your ULA, or download our Oracle ULA Exit Checklist to assess where you stand before we speak.