OBIEE 12c Extended Support closed in August 2025, so every day on Sustaining Support costs 22% of license fees for a product Oracle will never patch again
The deadline is behind you, not ahead of you. A 20-processor BI Foundation Suite estate at the 2017 published rate is paying roughly $1.4 million a year in support for a product that receives no new security fixes, no new certifications, and no critical patch updates. That number, not the technical merits of Oracle Analytics Server, is what should drive the next twelve months of decisions.
Prepared by Redress Compliance · August 22, 2026 · Oracle advisory. OBIEE and Oracle Analytics renewal and audit engagements, 2024 to 2026.
Executive summary
OBIEE 12c passed Extended Support in August 2025, and there is no 14c OBIEE release, so the only Oracle-supported forward paths are Oracle Analytics Server on-premises or Oracle Analytics Cloud.
Teams that tracked the broader Fusion Middleware 12.2.1.4 dates rather than OBIEE's own component dates found themselves out of support a year or more before they had budgeted for it.
Sustaining Support is full-price maintenance at roughly 22% of net license fees with no new program updates, no security alerts, and no critical patch updates.
Oracle applied the identical mechanic to E-Business Suite 12.1 on January 1, 2022, and the pattern is consistent: the invoice does not fall, the delivered value does.
OAS 2026 (26.01.0.0.0, GA March 2026) is not a patch-level upgrade; it moves the stack to Fusion Middleware 14c and JDK 21, which means WebLogic, JDK, and full re-certification work.
Budget it as a platform project, and check Oracle's published "What's Desupported in OAS 2026" list before you scope, because desupported features get no bug fixes and cannot be raised in a service request.
The AI and LLM layer that Oracle bundles free into Oracle Analytics Cloud is absent from OAS 2026, which makes the on-premises product a deliberate trailing copy of the cloud one.
That gap is Oracle's principal commercial lever in the OAS-versus-OAC conversation, and you should price it as a subscription conversion argument rather than a feature comparison.
On any path, the licensing minimums bite: 25 Named User Plus or 4 Processor licenses per product, and external-facing dashboards cannot be NUP-licensed at all.
A single customer portal exposed through OBIEE converts an entire deployment to Processor metric, and at the 2017 published rate of $324,000 per processor with $71,280 annual support, that is not a rounding error.
The three paths and what each one actually costs
There are three options on the table and only one of them changes your contractual position with Oracle.
Path one is doing nothing: you stay on OBIEE 12c, you keep paying support at 22% of net license fees, and Oracle keeps taking the money while building no new fixes, no security alerts, and no critical patch updates.
Path two is Oracle Analytics Server 2026 (26.01.0.0.0), which went GA in March 2026 on Fusion Middleware 14c and JDK 21, meaning WebLogic, JDK, and full certification re-work rather than a patch-level upgrade.
Path three is exit: either to Oracle Analytics Cloud subscription (still Oracle, but the perpetual asset is gone) or to a third-party BI platform, where the perpetual licenses can be terminated and, in our experience negotiating these exits.
Independent third-party support typically runs at roughly half the Oracle rate while you wind down.
Use the on-premise BI licensing baseline to establish what you actually own before you cost any of these.
| Path | License implication | Annual run cost | One-time cost | Residual risk |
|---|---|---|---|---|
| Stay on OBIEE 12c, Sustaining Support | Perpetual licenses unchanged, same CSI | 22% of net license (20-proc BI Foundation Suite at 2017 list: circa $1.4M) | Zero | No security fixes, no new certifications, no CPUs; audit exposure unchanged |
| Migrate to OAS 2026 on-prem | Same perpetual licenses, same support contract, no new license event unless cores change | Identical 22% stream | FMW 14c and JDK 21 re-platform, RPD and catalog regression, desupported feature remediation | Core-count drift on new hardware triggers a true-up; no AI layer |
| Move to Oracle Analytics Cloud | Perpetual licenses surrendered or shelved; subscription replaces support | Subscription, re-verify against the Aug 2026 Global Price List | Migration plus data residency and integration rework | Annual uplift risk, no perpetual fallback |
| Exit to third-party BI | Perpetual licenses terminable; support cancellable | Third-party support at circa half Oracle rate during wind-down, then zero | Rebuild of RPD logic and reports | Loss of Oracle bug-fix rights is permanent; no re-entry without repurchase |
The table hides the most important structural fact: Sustaining Support and an OAS migration are not competing options. OAS runs on the same perpetual BI Foundation Suite or BI Suite EE Plus licenses, under the same CSI, at the same 22% ratio.
Upgrading to OAS 2026 does not reduce your annual bill by a single dollar. It converts an unsupported product into a supported one at identical cost, which is worth doing, but it is a technical remedy, not a commercial one.
Why the deadline you tracked was probably the wrong one
Most estates we review tracked the wrong date. Teams monitored Fusion Middleware 12c (12.2.1.4) as a release line, whose Premier and Extended dates run further out, and assumed OBIEE inherited that runway. It did not.
OBIEE 12c was the most time-sensitive component in the stack, its Extended Support closed in August 2025, and there is no 14c release for OBIEE at all.
If your governance calendar carried one row labeled "FMW 12c," you have been out of support for over a year without a change-control event to flag it.
Oracle's Lifetime Support Policy runs three phases: Premier Support, then Extended Support (paid, narrower scope, typically no new certifications and limited patching), then Sustaining Support, which is best-effort with no new fixes. The second trap sits inside that structure.
Per Doc ID 1664916.1, Lifetime Support dates are published against the terminal patch set only, and Oracle creates new interim patches against the current release and the immediately previous patch set for a one-year grace period.
A team sitting two patch sets back was outside error-correction coverage well before the headline date, regardless of what the policy PDF said.
Re-audit every Fusion Middleware component individually, not as a stack. Pull the version string for each installed component, map each to its own Premier, Extended, and Sustaining dates, and record the patch set level against the terminal release.
Then check whether your support renewal quote still charges full rate for components already in Sustaining, which is a live negotiation lever covered in our Oracle support cost optimization assessment. The date you failed to track is Oracle's evidence, not yours.
Oracle Analytics Server licensing, decoded for buyers
A buyer-side walk-through of Processor and Named User Plus metrics, the breakeven that decides which one you buy, and the virtualization rules that turn two processors into two hun
Get the white paper →Oracle Analytics Server 2026 is a platform project dressed as an upgrade
Oracle announced OAS 2026 (version 26.01.0.0.0) on 9 March 2026, with general availability the following day, and the marketing frame is continuity: same RPD, same catalog, same skills, over one hundred new capabilities. The technical reality is a stack replacement.
OAS 2026 runs on Fusion Middleware 14c and JDK 21, which means a new WebLogic domain, a new Java runtime, and a fresh certification pass against your database versions, LDAP or SSO provider, load balancer, and every downstream consumer of BI content.
That is not a maintenance window applied on a Saturday night.
In our client work, the estates that treat it as one are the ones that discover in week three that a custom security initialization block, a Java host extension, or an ODBC driver combination was never certified on the new runtime and has no supported equivalent.
The capability list is genuine and Oracle will lead the business case with it: a Workbook Email Scheduler that delivers workbook visualizations as XLSX, PDF, or PNG on a recurring basis, a Redwood-style console refresh.
And OAuth2 support for Microsoft SMTP (which solves a real problem for anyone whose mail relay has already moved to modern auth).
Price the counterweight honestly before you sign the internal business case. You are re-testing the full RPD, the complete presentation catalog, every agent and delivery profile, usage tracking, write-back, and each integration point into ERP, EPM, or a warehouse.
You also need to validate the estate against Oracle's published What's Desupported in OAS 2026 list: once a feature is desupported, Oracle stops fixing bugs against it, may remove the code entirely, and will not accept a service request on it.
Budget it as a 6 to 12 month program with its own line item, staffed with a BI developer, a middleware administrator, and named business testers per subject area, not as a patch absorbed by the existing team.
The upgrade also touches your license position, because moving to new hardware or a new virtualization host changes your processor count. Read the metric comparison at your user scale before the infrastructure design is frozen, not after.
The AI gap is a pricing strategy, not a roadmap accident
Independent observers who track both releases describe OAS 2026 as very close to Oracle Analytics Cloud's January 2026 build with one category removed: the AI and LLM layer.
The January 2026 OAC update shipped Oracle Analytics AI Agents, AI Assistant capabilities for cluster and outlier analysis, feedback loops on AI-generated insights, and domain-specialized agents built on Retrieval Augmented Generation with custom instructions. None of that lands on-premises.
Oracle's own positioning is that OAS continues the strategy of aligning on-premises analytics with innovations introduced in OAC, which is a polite way of saying OAS is a deliberate trailing copy. The gap is not a certification lag or an engineering constraint.
GPU inference in a customer data center is a solved problem in 2026, and Oracle sells the infrastructure to do it.
Read the gap as a product boundary drawn where the money is. Oracle has a large installed base of perpetual BI Foundation Suite licenses that generate 22 percent support annually and nothing else.
That revenue stream is high margin but flat, and it is at its most vulnerable at exactly this moment, when Extended Support has already lapsed and the customer is forced to make a decision. A conversion funnel needs a reason for the customer to abandon a paid-for asset.
Feature parity on-premises removes that reason. A capability class that only exists in the subscription supplies it.
The word doing the heaviest lifting in Oracle's pitch is free. AI Agents are included in OAC at no additional line-item charge. That framing is a classic value transfer: the capability is not free, it is bundled into a metric you do not currently pay on.
You trade a perpetual license you own and a support fee you can dispute, benchmark, or reduce through a structured support cost review, for an OCPU-per-hour or user-per-month subscription that Oracle reprices at renewal and that you cannot walk away from without losing the platform entirely.
The correct accounting treatment is to price the AI layer as an option you are being sold, with a quantified business case per use case, rather than as a capability you are missing.
Most estates cannot yet quantify it. Ask the sponsoring business unit what a domain agent over the finance subject area is worth in hours saved, then ask who validates its output before it reaches a board pack.
In our experience across analytics negotiations, the honest answer in year one is a pilot for two or three teams, which is a small paid pilot on OAC, not a wholesale platform conversion.
The negotiation consequence is the part that costs real money. The moment your organization concedes internally that AI is a requirement rather than an option, you have conceded the metric change from perpetual processor to cloud subscription.
Everything after that is negotiated from a weaker base: term length, price hold, ramp, exit rights, and what happens to the perpetual licenses you still hold.
Oracle will offer to let you park them on reduced support or apply their value as a credit, and both mechanisms typically retire the asset permanently.
Hold the line by separating the two decisions. Decide the platform question (OAS on-premises, OAC, or exit) on total cost and operational fit over five years. Decide the AI question separately, later, with a business case and a bounded pilot.
Anyone who lets Oracle merge them into a single conversation has handed over the only leverage the situation still contains.
The licensing traps that surface when you touch the estate
The riskiest moment in an OBIEE estate is not the day support lapsed. It is the day you touch it.
Rebuilding servers, resizing VMs, standing up an OAS 2026 environment beside the old one, or opening a service request to ask about a migration path all create fresh evidence of deployment, and Oracle LMS reads that evidence against the entitlement you actually bought in 2013 or 2015.
Four mechanics do most of the damage. First, the minimums: 25 Named User Plus or 4 Processor licenses per product, and Oracle's price list puts the burden of maintaining those minimums on you, not on the reseller who sold the deal.
Second, the core factor arithmetic, where an eight-core server at a 0.5 factor equals four Processor licenses, which means a routine hardware refresh onto denser cores can silently double the count.
Third, the external-user rule: dashboards exposed to customers, dealers, or the public cannot be licensed under NUP at all, and a "customer portal" built after the original contract is one of the most common findings we see.
Fourth, entitlement misreadings on the bundled pieces, particularly BI Server Administrator and Essbase inside BI Foundation Suite.
Before any migration scoping, reconcile the deployed footprint against the ordering document, and if the metric itself looks wrong for today's headcount, work through the NUP versus Processor metric decision before you sign anything new.
| Trap | The rule as Oracle applies it | Where buyers get caught |
|---|---|---|
| Product minimums | 25 NUP or 4 Processor per licensed product | A 12-user departmental Essbase or BI Publisher deployment still owes 25 NUP |
| Core factor count | Cores multiplied by the Oracle core factor; 8 cores at 0.5 equals 4 Processor licenses | Refresh to denser cores or add a DR node and the required count rises with no new users |
| External-facing users | Named User Plus may not be used for external users; Processor is the only compliant metric | A partner or customer dashboard built after go-live converts the whole environment to Processor |
| BI Server Administrator | One NUP entitlement per license of BI Suite EE Plus or BI Foundation Suite, not per NUP and not per Processor | Teams assume the admin right scales with user count and staff three or four administrators |
| Essbase inside BI Foundation Suite | Bundled for use in support of BI Foundation, not as a general-purpose EPM engine | Finance builds standalone planning cubes on the bundled instance, creating separate Essbase liability |
| WebLogic Server SE restriction | The restricted-use WebLogic bundled with the analytics license covers Data Visualization only and permits no clustering | HA clustering built for uptime triggers a full WebLogic Suite requirement |
Two of these carry the largest dollar exposure in our experience. The BI Server Administrator entitlement is a single NUP per license of the suite, so a shop with three named administrators on one Foundation Suite license is short two, and Oracle prices that shortfall at list plus back support.
The bundled option packs inside BI Suite EE Plus behave the same way and are worth reading in detail in the bundled option pack audit trap guide, because the packs that surface in a migration discovery scan are almost never the ones the customer believed were in scope.
Assume every finding is priced at current list, not at your historic discount, and assume back support is claimed for the full period of unlicensed use.
What the price list and the field evidence actually show
The 2017 Victoria State Purchase Contract shows BI Foundation Suite at $324,000 per Processor with $71,280 support and $3,969 NUP with $873.18 support, both precisely 22%.
Oracle reduced the per-processor list from $450,000 to $300,000 on a price list dated 25 June 2013, which means long-tenured estates are paying support calculated off the higher pre-cut capitalized value.
The rest of the published evidence fills in the estate around the flagship SKU: BI Suite Enterprise Edition Plus at $238,950 per Processor with $52,569 support, BI Publisher at $49,680 per Processor, and BI Server Administrator at $6,264 NUP.
Any 2026 pricing claim should be checked against the Oracle Technology Global Price List, USA (Dollar) edition dated 3 August 2026, because that is the document Oracle's own reps will quote from. Three patterns recur across the engagements we run, and none of them appear in a price list.
The first is shelfware from headcount decline: NUP counts bought against a 2014 organization that has since shed 30 to 40% of its analyst population, with support still billed on the original quantity.
The second is support paid on Processor licenses attached to servers that were decommissioned years ago, because support follows what you own, not what you run, and nobody ever filed the termination notice.
The third is sequencing: Oracle consistently raises the OAS or OAC migration conversation in the weeks after the annual support renewal is signed, not before, which removes your only real piece of annual leverage from the table.
The 22% figure is not a rounding convention, it is a contractual multiplier applied to the license fee you originally capitalized, and it does not fall when the product stops receiving patches. That is the whole distortion.
A 20-processor Foundation Suite estate at the 2017 published rate carries roughly $1.4 million of annual support against a codebase Oracle has committed to never fix again.
The 2013 price cut makes it worse for older estates, because support was set against the $450,000 list and has been indexed upward ever since, so two customers running identical workloads can be paying materially different amounts for identically unpatched software.
The practical instruction: pull your last three renewal invoices, map each line to a live deployment, and identify every line where the support charge exceeds the value of the running system.
Do that reconciliation before Oracle opens the migration conversation, not after, because a renewal signed in ignorance of your own shelfware is the single most expensive document in this whole decision.
- Percentile standing for your exact deal size and industry, from real closed transactions
- Scenario simulation before the call: test alternative terms and see the financial impact of each
- A negotiation playbook, talking points, and a two page executive brief on day one
Your first five moves
- Pull the CSI and reconcile entitlement against deployment before Oracle asks, because the 25 Named User Plus or 4 Processor minimums, the core-factor arithmetic on every OBIEE server, and any external-facing dashboard that cannot legally sit on NUP will all surface during a migration scoping call if you have not found them first.
- Put every Fusion Middleware component's individual Lifetime Support Policy date on one page, since OBIEE 12c hit Sustaining Support in August 2025 while the broader FMW 12c line runs longer, and the terminal patch set rule (Doc ID 1664916.1) means your one-year interim patch grace clock may have expired on components you assumed were covered.
- Model all three paths on a five-year TCO with the 22% support ratio explicitly escalated, using the published $71,280 support figure per BI Foundation Suite processor as your anchor and testing what happens when Oracle applies its standard uplift each year against a product that receives no critical patch updates.
- Decide the AI question before Oracle frames it for you, because OAS 2026 is deliberately OAC minus the AI Agents and LLM layer, and if you have not written down whether generative analytics is a 2027 requirement or a nice-to-have, the sales team will assume it is a requirement and price the cloud subscription accordingly.
- Put support reduction or third-party support on the table before the OAS or OAC negotiation opens, using a documented support cost optimization assessment and the principle that support follows what you own, not what you run, so the cloud proposal competes against a costed alternative rather than against the status quo.
Frequently asked questions
When exactly did OBIEE 12c go out of support?
OBIEE 12c's Extended Support window closed in August 2025, and the product is now in Sustaining Support. There is no OBIEE 14c release. The only Oracle-supported forward paths are Oracle Analytics Server on-premises or Oracle Analytics Cloud.
Does Sustaining Support cost less than Premier Support?
No. Sustaining Support is billed at the same rate, typically around 22% of net license fees annually. What changes is what you receive: no new program updates, no new fixes, no security alerts, and no critical patch updates.
You retain access to fixes that already existed when you entered Sustaining Support.
Do I need to buy new licenses to move from OBIEE to Oracle Analytics Server?
No. OAS is the successor to OBIEE 12c and is licensed under the same legacy perpetual model, so existing BI Foundation Suite or BI Suite EE Plus entitlements carry across.
The cost is in the migration project, not the license, because OAS 2026 sits on Fusion Middleware 14c and JDK 21 and requires re-certification of the stack.
What is the difference between OAS 2026 and Oracle Analytics Cloud?
Functionally they are close, but OAS 2026 does not include the AI, LLM, and AI Agents layer that Oracle bundles into OAC at no additional charge. Oracle's stated strategy is to align on-premises capabilities with innovations introduced in the cloud, which by definition makes OAS a trailing copy.
Treat the AI gap as a commercial lever rather than a technical limitation.
Can I license external-facing dashboards under Named User Plus?
No. If analytics are exposed to external customers or partners rather than employees, Oracle requires Processor licensing. At the 2017 published rate that is $324,000 per processor for BI Foundation Suite with $71,280 annual support, subject to core factor.
A single external portal can therefore convert the metric for an entire deployment.
What are the minimum license quantities for Oracle BI products?
The minimums are 25 Named User Plus licenses or 4 Processor licenses per product.
Oracle's price list places the responsibility on the customer to maintain named-user-plus-per-processor minimums and to license all actual users, which means a small pilot deployment still carries a floor cost regardless of headcount.
Is third-party support a realistic option for an OBIEE estate?
It is, and it is strongest precisely when a product is already in Sustaining Support, because Oracle is no longer producing new fixes for you to lose.
The trade-off is that you forfeit the right to upgrade to OAS while off Oracle support, so the decision should be made alongside a firm view on whether you intend to re-platform at all.
