Work through all 20 items. Mark each as ready (✓), gap (✗), or unknown (?). HIGH-risk items represent the most common causes of sub-optimal certification outcomes. Download our Oracle Audit Defence Kit for supporting templates.
Section 1
Contract Review and Scope Confirmation
01
You have retrieved and fully reviewed your ULA Ordering Document, the Oracle Master Agreement, and all amendments — not just the summary terms sheet — to confirm exactly which products and quantities are covered.
High
Expert note: The ULA contract defines the scope of certification: which products are unlimited, which are excluded, whether cloud deployments count, and what partitioning rules apply. Many organisations rely on account team summaries rather than the actual contract language. Certification disputes are resolved by the contract, not by verbal commitments. Retrieve the full OD and all amendments from Oracle's Contract Repository or your legal files before beginning any certification planning.
02
You know your ULA expiry date precisely — including any auto-renewal clauses — and have built a certification timeline that starts at least 9–12 months before that date.
High
Expert note: Oracle ULA certifications that begin fewer than 90 days before the expiry date almost always produce inferior outcomes. With 9–12 months of lead time, you can conduct multiple discovery rounds, remediate non-qualifying deployments, maximise qualifying usage, and enter the certification negotiation from a position of confidence. Organisations that start late are forced to certify on Oracle's timeline rather than their own — and Oracle's timeline is never favourable to the customer.
03
You have conducted an enterprise-wide deployment discovery — covering on-premises, cloud, DR sites, and test environments — to establish your current deployment baseline before certification planning begins.
High
Expert note: Certification counts what is deployed at the certification date. Without a baseline discovery run at the start of your planning window, you do not know whether your deployment has grown, declined, or shifted to non-qualifying environments. Use Oracle's OLCT collection scripts (in a controlled manner with specialist oversight) or a trusted third-party discovery tool to capture every Oracle Database and ULA-product deployment across your estate. Do not rely on spreadsheet-based inventories that have not been validated against actual server deployments.
04
You understand which specific deployment environments qualify for certification counting under your ULA — including whether on-premises, authorised cloud, and DR environments are explicitly included in your OD.
High
Expert note: ULA qualification criteria vary by agreement vintage and negotiated terms. Some ULAs explicitly count authorised cloud deployments (AWS, Azure, OCI); others exclude cloud entirely. Some count DR deployments; others require active deployment. Some ULAs include test and development environments in the count; others do not. The qualification criteria are defined in your Ordering Document — not by Oracle's general policy. Map every environment against the OD language before counting a single deployment.
05
You have identified all Oracle products deployed in your estate that are NOT covered by the ULA — and confirmed they have separate conventional licences in sufficient quantity.
High
Expert note: The most common ULA compliance error is deploying non-ULA products alongside ULA products under the assumption that the ULA's unlimited rights extend to everything Oracle. During certification, Oracle will audit both ULA-covered and non-ULA products. Non-ULA products deployed without conventional licences constitute separately reported compliance gaps that Oracle can use as negotiating leverage during the certification conversation. Identify and document every non-ULA Oracle product in your estate before certification begins.
ULA expiring within 18 months?
Independent certification strategy and deployment maximisation. Buyer-side only.
Section 2
Deployment Discovery and Environment Qualification
06
Deployments of ULA-covered products on VMware ESXi clusters have been assessed against Oracle's partitioning policy — and you have determined whether VMware deployments qualify for certification counting under your specific ULA terms.
High
Expert note: VMware is classified as soft partitioning by Oracle. In most ULA agreements, VMware-hosted Oracle deployments must count the full physical capacity of the host cluster — not just the assigned vCPUs. This means a small Oracle VM on a large VMware cluster generates a very large certified count. Some ULAs include specific language permitting or restricting VMware deployments in the certification count. Review your OD for VMware-specific language and seek specialist advice on how Oracle will treat your VMware deployments during certification.
07
Cloud deployments of ULA-covered products on authorised public cloud platforms (AWS, Azure, OCI) have been confirmed as qualifying for certification counting — or explicitly excluded — under your OD.
High
Expert note: Cloud deployment qualification during ULA certification depends entirely on the specific language in your Ordering Document. Newer ULAs (post-2020) increasingly include authorised cloud deployments in the certification count, often averaged over 6–12 months of cloud usage. Older ULAs may exclude cloud entirely. If your ULA allows cloud deployments to count, they may represent significant incremental certified quantity — but you must have deployment records (e.g., AWS CloudTrail, Azure Monitor) that evidence the usage period and scale.
08
You have a plan to maximise qualifying deployment immediately before the certification date — through controlled deployment of ULA-covered products that will be needed in the post-certification estate.
High
Expert note: ULA certification is a one-time event that freezes your Oracle licence position. Any ULA-covered deployment that exists at the certification date becomes a perpetual licence at zero incremental cost. Organisations that plan ahead deploy the maximum useful quantity of ULA-covered products before certification — in production, DR, and cloud environments — to maximise the certified quantity and reduce future licence acquisition costs. This is not gaming the system: it is exercising the unlimited deployment rights for which you have paid.
09
You have modelled the post-certification licence position — the specific products, metrics, and quantities that would result from certification at current deployment levels versus maximised deployment levels.
Medium
Expert note: Post-certification, your Oracle licence position is fixed. The certified quantity determines your future flexibility: if you certify too few licences, any subsequent deployment requires new licence purchases at full list price. Model two scenarios: certification at current deployment (conservative) and certification after a controlled deployment maximisation programme (optimised). The difference in post-certification licence value — and the associated future flexibility — typically justifies the investment in deployment maximisation.
10
You have assessed the annual support cost implication of certification: the support fee for the certified licence count versus the current ULA support fee — to confirm certification is financially advantageous.
High
Expert note: Certification converts your ULA support fee (typically a fixed annual amount) into a support fee calculated as 22% of the certified licence value. If the certified licence value is high (because you have deployed extensively), the post-certification support fee may be significantly higher than the current ULA fee. Conversely, if the ULA support fee was high relative to actual deployment, certification may reduce support costs. Model both scenarios before committing to a certification date — in some cases, ULA renewal is financially superior to certification.
Section 3
Submission Preparation and Oracle Negotiation
11
Your certification deployment data has been prepared in a format consistent with Oracle's certification submission requirements — including evidence of deployments, processor details, and core factor calculations.
High
Expert note: Oracle's certification process requires a specific submission format. The deployment census must include: product name, version, deployment location, hardware type, processor model, physical core count, core factor, and calculated licence quantity. Evidence must be provided for each deployment — typically OLCT output or equivalent. A certification submission that does not match Oracle's required format will be returned for revision, losing valuable time close to the expiry date. Prepare the submission format 3 months before certification to allow time for Oracle's review.
12
You have conducted at least two independent discovery runs — separated by at least 30 days — to confirm that the deployment census is stable and reproducible before submission.
Medium
Expert note: A single discovery run may miss deployments on hosts that were offline or miss time-varying cloud deployments. Two independent discovery runs confirm the census is complete and reproducible. If the two runs differ significantly, investigate the discrepancy before submitting — Oracle will use its own discovery data to validate your submission and will highlight any gaps between your count and theirs. Reproducible, consistent discovery data is your primary defence against Oracle's post-submission challenges.
13
You have identified and remediated any non-qualifying deployments in non-authorised environments before the certification date — rather than including them in the submission and risking a dispute.
Medium
Expert note: If discovery reveals Oracle deployments in environments that do not qualify for certification counting under your OD — unauthorised cloud providers, non-approved partitioning technologies, excluded product versions — these must be remediated (decommissioned or migrated to qualifying environments) before certification. Including non-qualifying deployments in a certification submission creates post-certification compliance exposure. Oracle will identify them during its validation review and treat them as unlicensed deployments outside the certification scope.
14
Your legal team has reviewed the certification submission process — including Oracle's right to audit the certified quantities, post-certification audit provisions, and the deadline for raising disputes about Oracle's counter-assessment.
Medium
Expert note: Oracle's certification process includes a review period during which Oracle may challenge the submitted deployment count. Most ULAs include a 30–60 day window for Oracle to raise objections. After that window, the certified count is typically accepted. Confirm this timeline from your OD and prepare your dispute response materials (evidence packages for challenged deployments) in advance. Once the certification window closes, any Oracle challenge to the certified quantity is much harder to sustain.
15
You have engaged independent Oracle licensing specialists — with specific ULA certification experience — to validate your deployment census and support the certification negotiation with Oracle.
High
Expert note: ULA certification is a commercial negotiation with significant long-term implications. Oracle's LMS team brings specialist expertise to every certification engagement; the customer frequently does not. Independent Oracle specialists with ULA certification experience will validate your deployment census, identify deployments that Oracle is likely to challenge, prepare dispute responses, and represent your interests in the certification negotiation. At Redress, we have managed ULA certifications across every product line and industry — maximising certified quantities and minimising post-certification support costs in every engagement.
Section 4
Post-Certification Planning and Optimisation
16
You have assessed whether Oracle product options (Database Partitioning, Active Data Guard, RAC) deployed on ULA-covered Database instances are themselves covered by the ULA or require separate conventional licences.
High
Expert note: Oracle Database Enterprise Edition may be covered by your ULA, but the options and packs (Partitioning, Advanced Security, Diagnostic Pack, Active Data Guard, RAC) are separate products that require separate coverage. If these options are not explicitly listed in your ULA Ordering Document as unlimited products, each enabled option requires a separate conventional licence at the full processor licence rate. Run an options audit across every Oracle Database instance in scope before certification to identify any options that are outside ULA coverage.
17
You have documented a post-certification Oracle licence management process that will maintain compliance in the post-ULA environment — where any new deployment requires a new conventional licence purchase.
Medium
Expert note: Post-certification, the unlimited deployment rights expire. Every new Oracle deployment requires a conventional licence purchase. Many organisations that manage Oracle well during the ULA term fail to transition their governance to the post-certification environment — and inadvertently create new compliance gaps within 12–18 months of certification. Establish a post-certification licence management process before the certification date: a deployment approval gate, a licence inventory system, and a purchase process for new Oracle requirements.
18
You have explored whether ULA renewal (extending the unlimited period) is preferable to certification — particularly if deployment is expected to grow significantly in the 18–24 months following certification.
Medium
Expert note: Certification is not always the optimal outcome. If your Oracle deployment is expected to grow materially post-certification — through M&A, new application deployments, or cloud expansion — a ULA renewal at negotiated pricing may deliver lower total cost than certifying now and purchasing conventional licences for future growth. Model the expected post-certification licence purchases at renewal rates and compare the 3-year total cost of certification versus ULA renewal. This analysis should be completed before any communication to Oracle about certification intent.
19
Your certification date has been coordinated with your broader IT strategy — including cloud migration plans, hardware refresh cycles, and application decommissioning — to maximise the qualified deployment count at the optimal moment.
Medium
Expert note: The certified deployment count is a snapshot at the certification date. Organisations with active cloud migration programmes, application decommissioning schedules, or hardware refresh cycles must coordinate the certification date with these activities to avoid certifying at a deployment trough. If a cloud migration will decommission 40% of your on-premises Oracle estate over the following 12 months, certifying before that migration begins captures the maximum on-premises deployment in the certified quantity. Timing is the single largest driver of certification value.
20
You have prepared a certification negotiation strategy — including your walk-away position, acceptable certified quantity range, and post-certification commercial asks — before initiating the certification conversation with Oracle.
High
Expert note: Oracle's certification team is experienced in commercial negotiation. Customers who approach certification without a defined negotiation strategy typically accept Oracle's counter-assessment without meaningful challenge. Prepare your negotiation position: minimum acceptable certified quantity, maximum concessions you will make on disputed deployments, and any post-certification commercial requests (support discount, OCI credits, extended payment terms). Enter the negotiation with this strategy confirmed by your internal stakeholders and independent advisers before the first Oracle meeting.
"The difference between a well-managed ULA certification and a reactive one is measured in millions of post-certification licence costs. Every month of preparation before the certification date is worth more than any negotiation tactic at the table." — Morten Andersen, Redress Compliance
Interpreting Your Assessment Score
Count fully compliant items. Unknown answers should be treated as gaps for scoring purposes.
17–20
Strong Position
Controls mature. Schedule annual review to maintain as your estate evolves.
12–16
Moderate Exposure
Material gaps identified. Prioritise HIGH-risk items immediately and commission an independent review within 90 days.
0–11
High Exposure
Significant risk present. Do not engage Oracle commercially until independent specialists have assessed your position. Contact Redress immediately.
Oracle ULA Certification in 2026: Maximise, Then Exit
Oracle ULA certification is simultaneously the conclusion of your unlimited licence period and the beginning of your conventional licence estate. The quantity certified at the end of the ULA determines your Oracle licence position for years — potentially decades. Organisations that approach certification with a structured deployment maximisation strategy, a comprehensive discovery programme, and an independent negotiating team routinely achieve certified quantities 30–60% higher than those that certify reactively at current deployment levels.
Redress Compliance has managed ULA certifications across financial services, manufacturing, retail, and energy. Our role is to maximise the certified deployment count, challenge Oracle's counter-assessments with evidence-based dispute responses, and secure post-certification commercial terms that reduce long-term Oracle cost. We operate exclusively on the buyer side.