Oracle Analytics Server, three quiet mechanics and a bill
OAS, the on premises successor to OBIEE, licenses by Processor at $221,250 or Named User Plus at $2,000, both list. The headline prices are not where estates get hurt: the exposure lives in the cores Oracle counts, the restricted use WebLogic buried in the install, and an OBIEE upgrade right that a support lapse silently destroys.
Prepared by Redress Compliance · August 6, 2026 · Oracle licensing advisory. Based on 15 to 25 analytics reviews covering OAS and legacy OBIEE.
Executive summary
The metric breakeven is arithmetic: 111 users per processor. $221,250 divided by $2,000 sets the crossover; below that density Named User Plus is cheaper, above it the Processor metric wins.
The NUP floor complicates the small estate: at 10 users per licensed processor minimum, a single 16 core Intel host is 8 processors and an 80 user floor however few people actually log in.
The bundled WebLogic cannot cluster. OAS ships with a restricted use WebLogic Server Standard Edition license, and Oracle's own documentation states clustering it is not allowed, which means every highly available OAS deployment needs a full use WebLogic license nobody quoted.
In our reviews, not one estate had checked what the bundled entitlement actually permitted before building HA on top of it.
The OBIEE upgrade right is real and fragile.
Active, unbroken OBIEE support carries the right to run OAS, so most legacy estates are already entitled, yet several in our reviews were quoted net new licenses, two of those quotes exceeding a million dollars at list, for software they already had the right to run.
The fragility cuts the other way too: a support lapse of any length breaks the upgrade right and leaves the deployment unlicensed.
The virtualization position is the multiplier.
An OAS instance pinned to eight vCPUs inside a six node VMware cluster of 32 core hosts is 2 processors on paper and 192 processors in Oracle's audit position.
And processor counts on analytics hosts were overstated 20 to 50 percent wherever the virtualization boundary was never documented against Oracle policy.
The platform is small; the cluster it sits in is what gets counted.
The two metrics, and the floors underneath
| Metric | List price | The counting note |
|---|---|---|
| Processor | $221,250 per processor | Cores times the core factor, on every core the deployment can use |
| Named User Plus | $2,000 per user | A 10 user per processor floor: the hardware sets the minimum regardless of logins |
| The breakeven | Roughly 111 users per licensed processor | Below the density NUP wins, above it Processor does, and the floor distorts small estates |
| The admin allowance | One NUP for the Analytics Server Administrator included | Every additional modeller in the semantic layer tool licenses separately |
The floor prices the hardware, not the humans. A 16 core host at the 0.5 core factor is 8 processors, and 8 processors at the 10 user minimum is 80 Named User Plus licenses, $160,000 at list, for a dashboard server twelve people use.
Right sizing the host underneath OAS is the cheapest licensing decision in the deployment, made before the metric conversation even starts.
The restricted WebLogic, high availability's hidden invoice
OAS installs on WebLogic, and the bundle includes a restricted use WebLogic Server Standard Edition entitlement scoped to running OAS itself.
The restriction that bites is clustering: Oracle's own manual states the bundled edition cannot be clustered, so the standard high availability architecture, two or more OAS nodes behind a load balancer, requires full use WebLogic licensing the bundle does not provide.
The edition mechanics and their price ladders are the same ones worked in the WebLogic licensing guide, arriving here through a side door nobody quoted.
The review question is mechanical: is OAS clustered, and if so, under what WebLogic entitlement? In our file the answer to the second half was silence, estates that had built HA on the bundled edition without anyone checking what it permitted.
Each one an audit finding waiting for a measurement to price it.
The Oracle analytics licensing playbook
The OAS and OBIEE entitlement mechanics, the upgrade right evidence pack, the WebLogic bundle boundaries, and the virtualization position for analytics hosts.
Get the white paper →The OBIEE upgrade right, entitled estates quoted as new
Active, unbroken support on OBIEE carries the right to run OAS, which makes most legacy analytics estates already entitled to the successor product.
The commercial consequence showed up repeatedly in our reviews: net new OAS quotes issued to entitled estates, two exceeding a million dollars at list, priced on the assumption nobody would check the support history.
The evidence is the support renewal chain, unbroken from the original OBIEE purchase, and it is worth assembling before any OAS conversation, because it converts a seven figure purchase into a zero dollar upgrade.
The fragility deserves equal weight: a support lapse of any length breaks the right, permanently, leaving the OAS deployment unlicensed from the lapse forward.
Estates managing support costs through selective lapses, a legitimate strategy elsewhere, need the analytics line fenced off from it, and the support drop mechanics read carefully before any lapse touches the OBIEE lineage.
- 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
The virtualization position, small platform, big cluster
Analytics workloads invite the trap: OAS is modest, so it lands as a small VM inside a large general purpose cluster, and Oracle's soft partitioning position counts the cluster.
The worked example from our file, eight pinned vCPUs inside a six node cluster of 32 core hosts, prices as 2 processors in the deployment plan and 192 in the audit position, a hundredfold gap produced entirely by placement.
Processor counts on analytics hosts were overstated 20 to 50 percent wherever the boundary was never documented, and the defenses are the standard ones, dedicated hosts or clusters with the paper trail to match, per the virtualization licensing guide and the partitioning policy analysis.
What we saw across analytics reviews, 2024 to 2026
Across roughly 15 to 25 Oracle analytics reviews covering OAS and legacy OBIEE, Fredrik Filipsson found three quiet mechanics, not the headline price, driving the exposure:
Analytics hosts counted through undocumented virtualization boundaries, the cluster priced instead of the platform.
Net new OAS quotes to estates whose unbroken OBIEE support already carried the upgrade right.
The third mechanic was the WebLogic bundle: not one estate had verified what the restricted entitlement permitted before architecting on it.
The pattern across all three is the same one the whole Oracle library teaches: the platform's licensing is decided by documents, the support chain, the virtualization boundary, the bundle terms, that nobody owns until a review or an audit assigns them a price.
The cloud sibling's mechanics sit in the Analytics Cloud guide.
Your first five moves
- Assemble the OBIEE support chain before any OAS conversation: unbroken renewals from original purchase equal a zero dollar upgrade right.
- Fence the analytics line off from support lapse strategies; one lapse of any length breaks the right permanently.
- Verify the WebLogic entitlement against the architecture: clustered OAS needs full use WebLogic the bundle does not carry.
- Document the virtualization boundary for every analytics host, dedicated clusters or affinity with the paper to match, before the 2 becomes 192.
- Run the metric math with the floors applied, and right size the host before choosing the metric. The Oracle audit defense services and the Oracle practice run the review with you.
Frequently asked questions
How is Oracle Analytics Server licensed?
By Processor at $221,250 list or Named User Plus at $2,000, with the breakeven at roughly 111 users per licensed processor. NUP carries a 10 user per processor floor, so the hardware sets a minimum regardless of actual logins: a single 16 core Intel host is 8 processors and an 80 user floor.
Do we need to buy OAS if we have OBIEE?
Usually not: active, unbroken OBIEE support carries the right to run OAS. Several estates in our reviews were nonetheless quoted net new licenses, two above a million dollars at list, for software they already had the right to run.
The unbroken support renewal chain is the evidence, assembled before the conversation.
What happens to the OAS right if OBIEE support lapses?
A lapse of any length breaks the upgrade right permanently, leaving the OAS deployment unlicensed from that point forward. Estates using selective support lapses as a cost strategy need the analytics lineage explicitly fenced off from it, because reinstatement does not resurrect the right.
Can we cluster the WebLogic that ships with OAS?
No. The bundled entitlement is restricted use WebLogic Server Standard Edition, and Oracle's own documentation states clustering it is not allowed.
Highly available OAS, multiple nodes behind a load balancer, requires full use WebLogic licensing, which is the hidden invoice in most HA analytics architectures.
How does VMware placement affect OAS licensing?
Decisively: under Oracle's soft partitioning position the cluster is counted, not the pinned VM, so eight vCPUs inside a six node cluster of 32 core hosts prices as 192 processors in the audit position against 2 on paper.
Analytics processor counts were overstated 20 to 50 percent wherever the boundary was undocumented.
Are extra users included with an OAS license?
Only one: a single Named User Plus for the Analytics Server Administrator ships with the license. Every additional modeller who opens the semantic layer tooling must be licensed separately, which is a routine finding in estates that assumed the development team rode along with the server.
