Contents
Key takeawaysHow OAS is licensedWhich metric is cheaperOBIEE upgrade rightsBundled WebLogic limitsVMware and processor countsWhat we have seenAccount team lines and termsWhat to do nextFAQOAS lists at $221,250 per processor or $2,000 per Named User Plus. Most of the cost risk sits elsewhere: in the cores Oracle counts, the restricted WebLogic inside the install, and an OBIEE upgrade right that depends on unbroken support.
- Two metrics, one breakeven. One processor license costs the same as about 111 named users, so low density deployments usually belong on Named User Plus.
- The floor follows the hardware. A 16 core Intel host carries an 80 user minimum even if a dozen people use it, so size the host before choosing the metric.
- OBIEE support usually covers OAS. Customers current on support for the OBI suites are entitled to OAS, so check the support chain before accepting any new license quote.
- A lapse ends the right. Customers who let OBIEE support lapse are treated as new buyers of OAS, and reinstating support costs 150 percent of the last annual fee.
- The bundled WebLogic cannot cluster. High availability OAS needs WebLogic Server Enterprise Edition or WebLogic Suite, which the bundle does not include.
- VMware placement drives the count. A small OAS VM in a shared cluster can be counted at the size of every host in that cluster unless you document the boundary.
How is Oracle Analytics Server licensed?
Oracle Analytics Server (OAS), the on premises successor to OBIEE, is sold on two metrics. Processor lists at $221,250 per processor and Named User Plus (NUP) at $2,000 per user. Annual support on Oracle's price list is $48,675 per processor and $440 per user, which is 22 percent of the license fee.
The prices are rarely where the money goes wrong. The exposure comes from how many cores Oracle counts, what the bundled WebLogic Server permits, and whether an old OBIEE support contract already covers you.
| Item | List price | How it is counted |
|---|---|---|
| Processor | $221,250 per processor | Physical cores times the core factor, on every core the deployment can use |
| Named User Plus | $2,000 per user | Every authorized user, with a floor of 10 users per licensed processor set by the hardware |
| Breakeven | Roughly 111 users per licensed processor | Below that density NUP is cheaper, above it Processor is, and the floor distorts small deployments |
| Administrator allowance | One NUP for the Analytics Server Administrator included | Every additional modeler working in the semantic layer tool is licensed separately |
Where does the 111 user breakeven come from?
$221,250 divided by $2,000 is 110.6, so one processor license costs the same as about 111 named users. If you expect fewer than 111 users for each processor you would license, NUP is the cheaper metric. Above that density, Processor wins and you stop counting people.
How does the 10 user per processor minimum work?
The NUP minimum is priced off the hardware, whatever the login count. A single 16 core Intel host is 8 processors at the 0.5 core factor, and 8 processors at 10 users each is an 80 user floor. That is $160,000 at list for a dashboard server that twelve people use.
You buy the higher of your real user count and the floor. The floor rules are covered in more detail in our guide to Named User Plus minimums.
Who counts as a Named User Plus on OAS?
Anyone authorized to use the software counts, whether they log in daily or once a quarter. People who receive content through a portal or another application in front of OAS count too, because Oracle counts users at the front end of any multiplexing layer. Partner and customer portals are the usual surprise, as our note on external OBIEE users explains.
The license includes one NUP for the Analytics Server Administrator. Every other developer who changes the semantic model in the Model Administration Tool needs a license. Oracle lists Analytics Server Administrator separately at $5,800 per NUP, so three extra modelers on that item add $17,400 at list. Agree which item covers modelers before you add them.
How to Prepare for Your Oracle SaaS Negotiation
Which OAS metric is cheaper for your deployment?
For most departmental deployments NUP is cheaper, and the host size matters more than the metric. The table below runs a hypothetical company through four scenarios on Intel hardware at list prices, applying the floor where it bites.
| Host and users | Processors | NUP cost | Processor cost | Cheaper metric |
|---|---|---|---|---|
| 16 cores, 12 users | 8 | $160,000 (80 user floor) | $1,770,000 | NUP |
| 16 cores, 400 users | 8 | $800,000 | $1,770,000 | NUP |
| 16 cores, 1,200 users | 8 | $2,400,000 | $1,770,000 | Processor |
| 8 cores, 12 users | 4 | $80,000 (40 user floor) | $885,000 | NUP |
On the 16 core host the crossover sits at 885 users, which is 8 processors times 110.6 users. Support follows the license: the 80 user floor carries $35,200 a year at list, while 8 processors carry $389,400.
Why should you size the host before you choose the metric?
Halving the host halves both the floor and the processor count. Moving from 16 cores to 8 cut the minimum NUP spend from $160,000 to $80,000 in the example, before any discount was discussed. OAS workloads are often modest, so check CPU use on the current OBIEE servers before you sign for new hardware.
Should you license OAS by Processor so you never have to count users?
Many buyers are told Processor licensing is the safe choice because it ends user counting. We usually disagree for OAS. At 12 users it costs 11 times the NUP route and at 400 users more than twice as much. The core count also sets the NUP floor, so moving to Processor does not take the counting risk away.
Take NUP where the density is low and keep a clean user list. Revisit the metric if usage grows past the breakeven.
Oracle Analytics Licensing Guide
OAS and OBIEE entitlements, upgrade right evidence, WebLogic bundle limits and virtualization rules in one download.
Get the white paper →Do OBIEE customers need to buy new OAS licenses?
Usually not. Oracle's own OAS FAQ says customers current on support for OBI Standard Edition One, OBI Foundation Edition or OBI Extended Edition are entitled to OAS as part of that support. Most legacy OBIEE sites already hold the right to run the successor product.
Several companies in our reviews were still quoted net new OAS licenses, two of those quotes above $1 million at list, for software they already had the right to run. The quotes assumed the customer would not check its support history.
What evidence proves the upgrade right?
The proof is an unbroken support renewal chain from the original OBIEE purchase to today. Assemble it before any OAS conversation starts, because it turns a seven figure purchase into a zero dollar upgrade.
- Original order. The ordering document and license quantities for the OBIEE product and metric.
- Support history. Every annual renewal invoice under the same Customer Support Identifier (CSI), with no gap between end and start dates.
- Current CSI record. The My Oracle Support listing that shows the product lines still active.
- Metric match. Confirmation that the OAS deployment stays within the licensed metric and quantity, such as the same NUP count or the same processor count.
What does a support lapse do to the upgrade right?
A lapse of any length takes the right away. Oracle's FAQ says customers who own OBI but are not current on support are effectively new customers when they buy OAS. Under Oracle's support policies, unsupported programs also lose the right to download new releases, so any OAS release installed during a lapse sits outside your entitlement.
Getting back is expensive. Reinstatement costs 150 percent of the last annual support fee, prorated back to the lapse date, plus the next year of support, and Oracle does not promise in writing that it restores the OAS right. Ask for that confirmation before you pay.
- Before the lapse. You are entitled to OAS as part of support and can download current releases.
- During the lapse. Oracle treats you as a new OAS buyer and new releases are off limits.
- To return. Reinstatement fee plus a year of support, and a written OAS confirmation you should insist on.
Dropping support on unused Oracle products is a sound way to cut cost elsewhere. Fence the analytics product line off from it, and read our note on dropping Oracle support and reinstatement before any lapse touches the OBIEE lineage. The wider cost comparison is in our OBIEE end of life guide.
What does the OAS entitlement not include?
Oracle's FAQ states that Essbase is not part of OAS, although existing Essbase entitlements carry over. Customers who own only BI Publisher get the Analytics Publisher capabilities only. Oracle Analytics Desktop is included but limited to non production use. See our notes on Essbase licensing and BI Publisher licensing.
Can you cluster the WebLogic Server that ships with OAS?
No. OAS installs on WebLogic, and the bundle carries a restricted use license for WebLogic Server Standard Edition that covers running OAS itself. Oracle's OAS licensing manual states that clustering this edition is not allowed.
The standard high availability design, two or more OAS nodes behind a load balancer running as a WebLogic cluster, therefore needs full use WebLogic licensing that the bundle does not provide. In Oracle's WebLogic documentation, cluster support comes only with WebLogic Server Enterprise Edition and WebLogic Suite.
What does clustered OAS cost in WebLogic licenses?
Say you run two OAS nodes, each on a dedicated 8 core Intel host. That is 4 processors per node and 8 in total. WebLogic Server Enterprise Edition lists at $25,000 per processor, so the cluster adds $200,000 in license fees and $44,000 a year in support, on top of OAS itself.
The edition rules and price steps are the same ones worked through in our WebLogic licensing guide. Here they arrive through a side door that the original OAS quote rarely mentions. Our comparison of WebLogic editions covers when Suite is worth the extra cost.
Every highly available OAS deployment built on the bundled WebLogic is an audit finding waiting for someone to measure it.
How do you check whether your OAS deployment is clustered?
- WebLogic console. Open Environment, then Clusters, in the OAS domain and note any cluster with more than one managed server.
- Domain configuration. Read config.xml under the domain's config folder for cluster entries and the machines assigned to them.
- Load balancer. Check whether the load balancer pool for the analytics URL has more than one back end server.
- Entitlement. Match what you find against your WebLogic orders. If the only WebLogic you own came with OAS, the cluster is unlicensed.
The same check applies to the database that holds the OAS repository schemas. The OAS licensing manual grants restricted use rights for the JDK, WebLogic Server Standard Edition and Analytics Desktop, and none for a database, so that database needs its own license. Our note on the database under the OBIEE stack covers the older OBIEE bundles.
How does VMware placement change the OAS processor count?
Oracle treats VMware as soft partitioning and counts every physical core in the cluster where OAS can run, not the cores assigned to the virtual machine. Because OAS is small, it often lands as a modest VM inside a large general purpose cluster, and the whole cluster is then priced.
Take an instance pinned to eight vCPUs inside a six node VMware cluster of 32 core Intel hosts. The deployment plan counted 2 processors. Oracle's audit position counts all 192 cores in the cluster, which is 96 processor licenses at the 0.5 core factor. At list, that is $21,240,000 against the $442,500 the plan assumed.
What evidence holds up when Oracle counts the cluster?
The protections are the standard ones: dedicated hosts or a dedicated cluster for OAS, with the paper trail to match. Oracle's partitioning policy is not part of your license agreement, but arguing that point is harder without records of where OAS actually ran.
- Cluster membership and host core counts exported from vCenter, dated and kept.
- DRS rules and vMotion boundaries showing OAS VMs could not move outside the licensed hosts.
- vMotion and host event history for the audit period.
- Storage layout, since shared datastores can widen the scope Oracle argues for.
- A written record of who approved the placement and when.
Our virtualization licensing guide and the VMware evidence pack explain how to build the record.
What have we seen in recent OAS and OBIEE licensing reviews?
Across roughly 15 to 25 Oracle analytics reviews covering OAS and legacy OBIEE from 2024 to 2026, three findings drove most of the exposure. None of them was the headline price.
- Processor counts overstated by 20 to 50 percent. This happened on analytics hosts wherever the virtualization boundary had never been documented against Oracle policy, so the cluster was priced instead of the platform.
- Entitled customers quoted as new. Two net new OAS quotes above $1 million at list went to companies whose unbroken OBIEE support already carried the upgrade right.
- WebLogic entitlement never checked. Not one company had verified what the restricted WebLogic license permitted before building high availability on it.
The common thread is paperwork that no team owns: the support chain, the virtualization boundary and the bundle terms. Each sits unassigned until a review or an audit puts a price on it. If you are weighing the cloud version instead, its rules are in our Oracle Analytics Cloud guide.
What will Oracle's account team say about OAS, and how should you reply?
Expect four lines in an OAS conversation. Each has a factual reply, and each reply depends on having the documents in hand first.
| What you will hear | What to say back |
|---|---|
| "OAS is a new product, so your OBIEE licenses do not cover it." | Oracle's OAS FAQ entitles customers current on support for the OBI suites. Here is our unbroken support chain by CSI. Please requote the upgrade at zero license cost. |
| "WebLogic is included with OAS." | A restricted Standard Edition license is included, and the OAS licensing manual says it cannot be clustered. Show us which license covers our two node cluster, or quote Enterprise Edition for it now. |
| "The whole VMware cluster needs licensing." | Here is the host list, the DRS rules and the vMotion history for the OAS VMs. Count only the hosts where OAS could run. |
| "Move to Oracle Analytics Cloud and the compliance issue goes away." | Price the cloud service as its own decision. Resolve any finding on its facts first, so a cloud credit does not become the settlement for a count we dispute. |
Which contract terms should you ask for?
- Written upgrade confirmation. A statement mapping each OBIEE license, by CSI, to the OAS entitlement, so the right is on paper before any audit.
- WebLogic scope. The edition and quantity that covers any cluster, named in the same order as OAS, so high availability is licensed from day one.
- Price hold on added users. The same NUP discount for additional users over the next renewal cycle, so growth past the floor is not repriced at list.
- Support increase limit. A cap on annual support increases, since support at 22 percent of the net fee is the cost that runs for years.
- Hosts named in the order. The physical servers or cluster the licenses cover, which gives you a documented boundary if Oracle later counts a wider cluster.
Oracle will not agree to all of these. Each one you get is a question you do not have to argue about during an audit, and the Oracle audit defense services team can help you rank them.
What to do next
- Assemble the OBIEE support chain. Pull the original order and every renewal under each CSI before any OAS conversation. An unbroken chain is a zero dollar upgrade right.
- Protect the analytics support line. Exclude OBIEE and OAS from any support reduction plan, because a lapse of any length removes the upgrade right and access to new releases.
- Check WebLogic against the architecture. If OAS runs as a cluster, confirm you own Enterprise Edition or WebLogic Suite for those processors.
- Document the virtualization boundary. Put every analytics host on dedicated hosts or a dedicated cluster, and keep the vCenter records that prove it.
- Size the host, then pick the metric. Apply the 10 user floor and the 111 user breakeven to your real user list, after right sizing the hardware.
- Get the review done before Oracle does it. The Oracle practice runs this review with you and prepares the replies before the account team calls.
Want a second opinion on your Oracle position? Our Oracle licensing consultants are former Oracle insiders who now work only for buyers.
Frequently asked questions
How is Oracle Analytics Server licensed?
OAS is licensed per Processor at $221,250 list or per Named User Plus at $2,000 list. Processor counts physical cores times the core factor. Named User Plus counts every authorized user, with a minimum of 10 users per processor, which means an 8 processor host needs at least 80 user licenses.
Do we need to buy OAS if we have OBIEE?
Usually not. If your OBIEE support has run without a gap since the original purchase, the right to run OAS is part of that support. Answer a new license quote with the renewal invoices and CSI record rather than a counteroffer, since a zero dollar upgrade needs no discount.
What happens to the OAS right if OBIEE support lapses?
You lose the right to move to OAS and to download new releases, and Oracle treats you as a new buyer. Reinstatement brings back support at a steep fee but carries no written promise about OAS. If you are trimming Oracle support elsewhere, list the OBIEE support lines by CSI and exclude them explicitly.
Can we cluster the WebLogic that ships with OAS?
No. The OAS bundle includes WebLogic Server Standard Edition for running OAS only, and clustering it is not allowed. A multi node OAS setup needs WebLogic Server Enterprise Edition or WebLogic Suite licenses for the processors in the cluster, which is the cost most high availability designs miss.
How does VMware placement affect OAS licensing?
Oracle counts the physical cores of every host OAS could run on. An eight vCPU VM in a six node cluster of 32 core hosts goes from 2 processors on paper to 192 cores, or 96 processor licenses. Across our reviews, undocumented boundaries overstated analytics processor counts by 20 to 50 percent.
Are extra users included with an OAS license?
Only one Named User Plus comes with the license, for the Analytics Server Administrator. Any additional developer who edits the semantic model in the Model Administration Tool needs a license. Audits often find the whole BI development team working under that single included user.
Is Essbase included in Oracle Analytics Server?
No. Oracle states that Essbase is not part of OAS. Customers who already hold Essbase licenses keep them when they move from OBIEE, but a new Essbase deployment alongside OAS needs its own license and support.