We certify 30–50% more Oracle licenses than Oracle's own process produces — and deliver an average of £2–5M in added perpetual entitlement per engagement. Your ULA expires once. The count you certify is permanent. Make it count.
We have no commercial relationship with Oracle. We do not resell Oracle software. We do not participate in Oracle's partner programme. We have never received a referral fee from Oracle. Our only obligation is to the enterprise that hires us.
Talk to a former Oracle insider who has managed 500+ ULA engagements. No commitment. No sales pitch.
No commitment. No sales pitch. 30 minutes with a former Oracle insider who has managed 500+ enterprise ULA engagements.
An Oracle Unlimited License Agreement lets you deploy as many licenses as you need during the term. At expiry, you must formally certify your deployment count — a number that becomes your permanent perpetual entitlement. Everything you certify, you own outright. Everything you fail to certify, you must repurchase at Oracle list price. Oracle's certification process is designed to produce the lowest defensible count. Your independent process needs to produce the highest justifiable one.
The problem is asymmetric information. Oracle's certification team has managed thousands of these conversations. Your in-house team has managed one — or none. Oracle knows which deployment configurations can be legitimately included and which it would prefer not to count. It knows how to interpret virtualization rules, subsidiary scope, and product classification in its own favour. And it knows that most enterprises, under time pressure and without specialist knowledge, will accept the first number they are given.
What gets missed is substantial. Processors deployed in partially virtualised environments. Products deployed across subsidiaries that were acquired during the ULA term. Metrics that changed mid-agreement where the original terms are more favourable than Oracle's current guidance. Deployment evidence that was collected but never formally submitted. These are not edge cases — they appear in the majority of the 500+ ULA engagements we have managed. The average uplift from independent certification preparation is 30–50% above Oracle's uncontested position. At Oracle list prices, that gap typically represents £2–5M in perpetual entitlement.
There is no second chance. Once Oracle countersigns the certification, the count is locked permanently. Future deployments above that count require new licence purchases at full Oracle list price, plus 22% annual support from day one. The financial consequences of an understated certification compound every year thereafter — not just in licence cost but through Oracle's 8% annual support increase, applied automatically to whatever support baseline the certification establishes.
These are real engagement outcomes — fully anonymised. The pattern is consistent across industries and geographies: enterprises that certify without independent preparation leave millions of perpetual licences on the table permanently.
Three undisclosed product categories and a subsidiary acquired mid-term were identified through independent deployment discovery. Certified count increased by 38% versus Oracle's initial guidance. £3.4M in future licence purchases avoided. Perpetual entitlement now accurately reflects the organisation's actual deployment footprint.
Oracle challenged the virtualisation methodology applied to a major datacentre consolidation completed in Year 2 of the ULA. Redress defended the submission with full technical documentation and contractual precedent. Oracle's counter-claim was reduced from 30% to 6% of the submitted count. $2.1M in contested licence purchases eliminated.
Independent financial modelling demonstrated that renewal was not commercially justified given the institution's cloud migration timeline and declining Oracle footprint. Exited ULA with maximum certified count. Annual Oracle support saving of £1.8M achieved in Year 1, compounding as Oracle workloads continue to move to cloud alternatives.
Mid-term review identified an undisclosed Oracle deployment expansion triggering an automatic support uplift outside the ULA's agreed terms. Redress engaged Oracle's account team before the uplift was formalised. The support schedule was renegotiated and corrected. £620K in annual support cost avoided. ULA deployment strategy realigned with actual growth plan.
In one engagement, a Scandinavian financial services group entered ULA certification having deployed Oracle Database across 12 cloud and on-premise environments. Their internal team identified 6,400 processor licences. Our certification team identified 9,200 — a 44% increase. The additional deployments were legitimately covered under the ULA. Certifying more meant lower per-unit costs at renewal and stronger leverage in the subsequent commercial negotiation.
View the full range of Oracle case studies, including Oracle ULA advisory engagements across financial services, manufacturing, healthcare, and public sector organisations globally.
A well-run ULA certification engagement has a clear, defined sequence. The further in advance you engage, the more options are available at each stage. The minimum effective lead time is 90 days. Twelve months is optimal.
We map every Oracle product deployment across all environments, datacentres, cloud instances, and subsidiaries covered by the ULA. We review the original agreement, all amendments, and any Oracle correspondence about scope. We identify products deployed but not yet formally inventoried, and subsidiaries acquired or reorganised during the ULA term that may be in scope. The output is a complete, evidence-backed deployment record — independent of Oracle's view of it.
Using the deployment discovery data, we build your independent certification position. This means applying Oracle's licensing rules — processor core factors, virtualisation policies, named user minimums, product metric choices — in your favour, not Oracle's. We identify every legitimate basis for a higher count: undisclosed processor configurations, alternative metric interpretations where the agreement permits, and geographic or subsidiary scope you are entitled to include. Every position is documented with contractual and technical evidence before submission.
Before any submission to Oracle, we model three scenarios: exit to perpetual licences at your maximum certified count, renew the ULA for a further term, or transition to a PULA (Perpetual Unlimited License Agreement). The model accounts for your certified count, Oracle's 8% annual support increase, your cloud migration plan, and the replacement cost of Oracle products you may no longer need. We do not have a preferred outcome. We present the numbers and advise on which path delivers better long-term value for your organisation specifically.
We prepare the certification submission documentation and manage the Oracle negotiation directly. Oracle challenges a material proportion of independent certifications — particularly where the count is significantly higher than their internal expectation. We respond to every challenge with technical documentation and contractual evidence. Where Oracle's challenge has merit, we concede precisely the minimum. Where it does not, we hold the position. Across 500+ ULA engagements, we have never had a client forced into an unacceptable certification outcome.
Certification is the beginning of the post-ULA compliance cycle, not the end. Oracle returns. We implement the deployment monitoring and compliance controls that prevent the next audit notice from landing unexpectedly. We also review the certification agreement for clauses that create future risk — Oracle occasionally inserts provisions into post-certification documents that restrict how certified licences can be deployed going forward. We review and, where necessary, negotiate the final terms before you sign.
Everything you need to know before certifying your Oracle ULA — deployment maximisation, renewal vs exit modelling, and the 12 questions Oracle hopes you do not ask.
There is no shortage of Oracle advisors. Most work with Oracle as well as against it. Redress does not. Here is what that means in practice for a ULA certification engagement.
We do not work for Oracle. We do not receive Oracle referral fees. We do not resell Oracle licences or cloud services. Many advisory firms market themselves as independent while maintaining Oracle partner status — which means Oracle can see their client list and their advice is commercially constrained by that relationship. Ours is not. Our independence is absolute, documented, and guaranteed in every engagement letter. When we challenge Oracle's certification position, there is no conflict of interest softening that challenge.
Our senior advisors have worked inside Oracle LMS and Oracle's licencing organisations. They know how Oracle builds certification challenges, which arguments land and which do not, and where Oracle's own rules can be legitimately interpreted in the enterprise's favour. This is not theoretical knowledge — it is the same methodology Oracle uses, applied to serve the buyer. When Oracle challenges your certification submission, our team has had that conversation from the other side of the table.
We do not say we "add value" or "improve outcomes." We certify 30–50% more licences than Oracle's uncontested process produces. We deliver an average of £2–5M in added perpetual entitlement per engagement. We have defended certifications where Oracle challenged 30–40% of the submitted count and reduced the concession to under 6%. These are actual numbers from actual engagements — available in fully anonymised case studies, not marketing estimates.
The advisor you speak with in the briefing is the same advisor who manages your engagement. We do not hand off to junior analysts or project managers after the contract is signed. Oracle ULA certification is a high-stakes, technically complex process. Every decision — every position we take in a certification submission, every challenge we choose to defend — is made by the same senior advisor with 20+ years of Oracle licencing experience. Not a team lead reviewing junior work. The senior person directly involved at every point.
Redress is Gartner-recognised as an independent Oracle advisory firm. We have completed 500+ Oracle engagements across 40+ countries, covering ULA certification and strategy, Oracle audit defence, contract negotiation, licence management, and third-party support transition. Our full case study library documents specific outcomes — with £/$ numbers — across every engagement type.
Oracle ULA certification is not a single conversation. It involves multiple technical and commercial dimensions, each of which can materially affect the final certified count and the post-certification support baseline. We address all of them in every engagement.
Processor core count maximisation. Oracle's processor licencing rules — including the core factor table — determine how physical and virtual processor deployments translate into licence requirements. We examine every deployment configuration to identify where Oracle's proposed processor count is lower than what the agreement and Oracle's own published policies permit you to certify.
Virtualisation methodology challenges. Oracle's virtualisation policies are among the most disputed areas in ULA certification. We analyse the virtualisation technology in use across all environments — VMware, Oracle VM, cloud-based virtualisation, hard partitioning configurations — and apply Oracle's published policies accurately rather than conservatively. Oracle's interpretation of virtualisation rules during certification consistently favours Oracle. Ours does not.
Subsidiary and geographic scope. Many ULAs cover subsidiaries, affiliates, and entities acquired during the term. Oracle routinely challenges the inclusion of newly acquired entities or overseas subsidiaries. We establish the contractual scope precisely and include every entity you are entitled to certify, with supporting documentation from the ULA agreement and any applicable amendments.
Product classification and metric optimisation. Oracle products are licensed under different metrics — processor, named user plus, employee, application user. Where the agreement permits metric choice, we select the metric that produces the most favourable perpetual entitlement. Where Oracle has applied the wrong product classification to a deployment, we identify and correct it before submission.
Support fee negotiation and error correction. The post-certification support fee is calculated at 22% of net licence value and then increases by 8% every year. We negotiate the support baseline and, where possible, any support credits available during the certification process. We also identify and correct administrative errors in Oracle's post-certification support schedule — errors that appear in a meaningful proportion of certifications and consistently, and not coincidentally, favour Oracle.
Renewal, exit, and PULA financial modelling. For every engagement, we model the financial consequences of all three post-ULA paths. The renewal-versus-exit decision is one of the highest-value choices an enterprise can make in its Oracle relationship. We make it with complete financial transparency — including the compounding effect of Oracle's 8% annual support increase over the following 5–10 years. Read more in our Oracle knowledge hub and our detailed ULA certification strategy guide.
The count you certify this year is the count you carry for the lifetime of your Oracle relationship. Every licence you fail to certify must be repurchased at Oracle list price — and then supported at 8% annual increase forever after. This is the highest-value decision in your Oracle relationship. Make it with former Oracle insiders who have done this 500+ times.
No commitment. No sales pitch. 30 minutes with a former Oracle insider who has managed 500+ enterprise ULA engagements across 40+ countries.