Oracle Analytics Server is the on premises successor to OBIEE, licensed on processor or named user plus metrics. The core factor and the user minimums decide the bill. Read the model before the next audit.
Oracle Analytics Server is the on premises analytics platform that succeeds OBIEE, licensed on processor or named user plus metrics. This guide covers the mechanics, the upgrade rights, the audit exposure, and the buyer side moves.
Oracle Analytics Server is on premises software on the technology price list, licensed by Processor or by Named User Plus. The metric choice depends on consumer counts and deployment footprint. Oracle documents the product on its Analytics Server pages.
Processor licensing counts cores adjusted by the core factor across the analytics hosts. It suits broad or unknown consumer populations such as dashboards published to all staff.
Named User Plus counts the individuals authorized to access the analytics, subject to per processor minimums. It suits a bounded analyst and report consumer population, within the minimums Oracle sets in its technology price list.
Processor licenses multiply physical cores by the Oracle core factor for the chip. Applying the wrong factor, or none, is a common source of overcounting on analytics estates.
Apply the exact multiplier from Oracle's processor core factor table for the precise chip, not a generic assumption.
Illustrative OAS processor calculation with core factor
| Server | Cores | Core factor | Processor licenses |
|---|---|---|---|
| Intel Xeon, 8 cores | 8 | 0.5 | 4 |
| Intel Xeon, 24 cores | 24 | 0.5 | 12 |
| Two node cluster, 48 cores | 48 | 0.5 | 24 |
Oracle Analytics Server is the on premises successor to OBIEE. In most cases existing OBIEE entitlements carry upgrade rights to OAS, so net new licenses are not required to move.
Customers with current support on OBIEE generally have the right to run OAS under the same entitlement. Confirm the mapping before accepting any net new license quote.
Some accounts are quoted fresh OAS licenses despite holding OBIEE entitlements. Check the upgrade path before buying analytics you already own.
White Paper · Oracle Analytics
OAC vs OAS, and the door that doesn't reopen. Read it free.
Oracle analytics audits focus on processor counts on virtual hosts and on user populations against minimums. OAS upgraded from OBIEE adds entitlement mapping complexity.
Soft partitioning rarely reduces processor counts on its own. Document the platform and isolate Oracle analytics workloads to defend a lower count. The Software Investment Guide frames the policy.
Report consumers count toward Named User Plus. Indirect access through embedded dashboards is a frequent finding, so count all consumers honestly.
The common advice is to buy fresh Oracle Analytics Server licenses when moving off OBIEE, treating OAS as a new product. We disagree. In most analytics estates Fredrik Filipsson reviewed, the existing OBIEE entitlements with active support already carried the right to run OAS, yet several clients were quoted net new licenses they did not need. The buyer side move is to confirm support status, map OBIEE entitlements to the OAS deployment, and challenge any net new quote before signing. Paying again for analytics you already own is the most common and most avoidable error on this platform.
Source: Redress Compliance advisory engagement file, 2024 to 2025.
Oracle Analytics Server is not always a new purchase. For most OBIEE customers it is a right they already hold and are about to pay for twice.
Oracle Analytics Server is sold on two metrics from the Technology Price List: Processor at $221,250 and Named User Plus at $2,000, both list and pre-discount. The metric you pick can swing the deal by seven figures, and the deciding variable is a single ratio: $221,250 ÷ $2,000 is about 111 named users per processor. Below that density NUP is cheaper; above it, Processor wins. Every count runs as cores × core factor (0.5 for x86), rounded up, and NUP carries a floor of 10 users per processor.
OAS metric comparison
Oracle Technology Price List (list / pre-discount). Most customers negotiate below list; use these as ceilings.
| Metric | License (list) | Annual support (22%) | Minimum |
|---|---|---|---|
| Named User Plus | $2,000 / user | $440 / user | 10 NUP per processor |
| Processor | $221,250 / processor | $48,675 / processor | 1 processor |
Breakeven: $221,250 ÷ $2,000 = ~111 named users per processor. Below that density, Named User Plus is cheaper; above it, Processor wins.
Worked at three sizes: a single 2-socket, 16-core Intel host is 16 × 0.5 = 8 processors. Processor list is 8 × $221,250 = $1.77M; the NUP floor is 80 users = $160,000, so NUP wins by roughly 11x for a bounded team. At 64 cores (32 processors) Processor list is $7.08M against $640,000 for a 300-user NUP deployment. Only when users are public, uncountable, or embedded in an external application — a 10,000-user portal, say — does Processor become mandatory regardless of cost.
Buyer move: do the density arithmetic before Oracle steers you to Processor "for simplicity." For most finance and BI teams under ~111 users per licensed processor, Named User Plus is dramatically cheaper.
Yes, with one condition that trips up audit targets. Customers current on maintenance and support for a legacy Oracle BI suite — BI Suite Enterprise Edition, EE Plus, or BI Foundation Suite — are entitled to install and run OAS at no new license cost. OAS is delivered as an upgrade, not a new product: existing Processor or NUP quantities carry over and the support contract date is not reset.
The trap is that entitlement is tied to continuous, active support on the original OBIEE licenses. If support lapsed — even briefly — and OAS was then deployed, the customer is technically unlicensed for OAS, because the upgrade right flows only through a live support stream. This is one of the most common analytics-audit findings: OAS binaries running on servers whose underlying OBIEE support was cancelled years earlier to save the 22 percent fee. A second gotcha: Essbase is not part of OAS, so a customer who held only BI Suite EE gains no Essbase right by moving across.
Buyer move: before any rollout, confirm the OBIEE support line has been unbroken and map each installed OAS instance to a specific supported entitlement. If support lapsed, reinstate or negotiate a fresh OAS agreement before Oracle finds the deployment.
This is where paper math collides with how Oracle counts in an audit. OAS uses the same processor rules as Oracle Database: you license every physical core where the software is installed or running, multiplied by the core factor. The dispute is rarely the factor (x86 is a flat 0.5); it is which cores Oracle insists are in scope. Oracle recognises only hard partitioning (for example Oracle Linux KVM with pinning, or capped Solaris Zones) as capacity-limiting. It does not accept VMware vSphere, vMotion, DRS clusters, or Hyper-V.
Core factor examples for common OAS host CPUs (Oracle Core Factor Table)
| Processor | Core factor | Example | Processor licenses |
|---|---|---|---|
| Intel Xeon / AMD EPYC (current x86) | 0.5 | 56-core Xeon × 0.5 | 28 |
| Oracle SPARC T4 / T5 | 0.5 | 16-core T5 × 0.5 | 8 |
| IBM POWER9 / POWER10 | 1.0 | 24-core POWER10 × 1.0 | 24 |
Formula: physical cores × core factor, rounded up to the next whole number.
The exposure is stark. OAS pinned to an 8-vCPU VM looks like 4 cores × 0.5 = 2 processors ($442,500 list). But if that VM lives in a six-node VMware cluster of 2-socket, 32-core hosts (384 cores), Oracle's audit position is 384 × 0.5 = 192 processors — over $42M list. That is the single largest silent liability on most OAS estates.
Buyer move: isolate OAS onto a dedicated cluster (ideally a physically separate vCenter) or an Oracle-approved hard-partitioning platform, and keep dated architecture diagrams and vMotion-boundary evidence. Document containment before an audit notice arrives; retrofitting the story afterward carries no weight.
Three divergent paths. Staying on OAS keeps perpetual licenses and pays 22 percent annual support ($48,675 per processor or $440 per NUP list) with rights to the newest releases and patches — best when the deployment is stable and right-sized. Moving to Oracle Analytics Cloud (OAC) converts to subscription (roughly $90 per user per month Professional, $140 Enterprise, list), but the lever most buyers miss is Bring Your Own License: existing OAS or OBIEE processors can be applied to OAC BYOL SKUs, cutting the cloud rate sharply versus license-included. Third-party support (Rimini Street, Spinnaker) runs about half of Oracle's 22 percent — roughly an 11-percent-of-license run rate — but forfeits rights to new OAS versions and Oracle patches.
Buyer move: sequence the decision. Right-size first (kill NUP shelfware, contain virtualization) so you are not migrating or supporting bloat, then compare: OAC BYOL for teams wanting managed and AI features; third-party support for stable, frozen estates chasing 50-percent-plus support savings; status quo only if you actively consume new OAS releases.
Yes — a minimum of 10 Named Users Plus per licensed processor, calculated as cores × core factor (rounded up) × 10, regardless of how few people actually use the system. A single 2-socket, 16-core Intel host (8 processors after the 0.5 factor) carries an 80-NUP floor even if only 20 people log in.
No — the free OBIEE-to-OAS upgrade right flows only through a continuous, active support contract, so a lapse means you are unlicensed for OAS and must reinstate support with back-fees, or buy fresh OAS licenses, before Oracle discovers the deployment.
Oracle Analytics Server is on premises software licensed on the technology price list by Processor or by Named User Plus. The metric choice depends on consumer counts, deployment footprint, and per processor minimums.
Oracle Analytics Server is the on premises successor to OBIEE. It carries forward the analytics platform, and existing OBIEE entitlements with active support generally include the right to run OAS.
In most cases yes. Customers with current support on OBIEE generally have the right to run Oracle Analytics Server under the same entitlement, so net new licenses are usually not required to migrate.
The core factor is a multiplier applied to physical cores to calculate processor licenses. It is published in Oracle's processor core factor table and must be applied per exact chip model.
Named User Plus is cheaper when the consumer population is bounded and sits above the per processor minimum cost. For broad dashboard publishing to all staff, Processor is usually cheaper.
Not on its own. Oracle's partitioning policy treats most soft partitioning as non binding for license reduction, so documenting workload isolation is needed to defend a lower count.
Processor counts on virtual hosts, user populations against minimums, and indirect access through embedded dashboards are common triggers. OAS upgraded from OBIEE adds entitlement mapping complexity.
Confirm OBIEE support and the OAS upgrade rights it carries before buying anything. Most OBIEE estates are already entitled to run OAS, so challenge any net new quote first.
Oracle Analytics is sold two ways, a perpetual per-processor server and a per-OCPU cloud subscription, and the move between them does not reverse. The prices and the five-year model.
Used across more than five hundred enterprise engagements. Independent. Buyer side. Built for procurement leaders running the next renewal cycle.
Before buying Oracle Analytics Server, check what OBIEE already entitles you to. Most estates own the upgrade and are about to pay for it again.
500+ enterprise clients. 11 vendor practices. Industry recognized. One conversation can change what you pay for the next three years.
Oracle pricing shifts, audit patterns, and negotiation levers from live engagements. No vendor spin.
