Oracle's BI and analytics products are deployed across thousands of enterprises as the analytics layer between Oracle databases and business users. The licensing seems straightforward. But BI platforms are designed to distribute data broadly, and every shared dashboard, published report, or analytics portal changes the licensing equation. Compliance exposure routinely reaches $1M to $5M+ for deployments the organisation considers "small." This guide covers the complete licensing framework for every Oracle BI product.
This guide covers the full Oracle BI product family. For product-specific deep dives, see: Oracle Analytics Server Licensing | Oracle BI Suite Foundation Edition Licensing | Oracle Licence Metrics & Definitions
Oracle's BI and analytics products (OBIEE, OAS, BI Publisher, Essbase) are licensed under the same Processor or Named User Plus metrics used for Oracle Database and middleware. But BI licensing creates unique compliance risks that organisations routinely underestimate.
The fundamental problem is that BI platforms are designed to distribute data broadly. A single dashboard published to 500 employees means 500 NUP licences are required, not just the 20 analysts who created it. A BI Publisher report embedded in an internal portal and emailed to the entire sales team means every recipient who interacts with the BI system requires a licence. When web portals, APIs, or middleware serve BI content to thousands of users through a single connection pool, Oracle's multiplexing rules require every end user to be counted.
| BI Product | Licence Metrics | NUP Minimum | Most Common Compliance Risk | Typical Audit Finding |
|---|---|---|---|---|
| OBIEE (legacy) | Processor or NUP | 10 NUP/processor | Dashboard sprawl: reports shared beyond licensed user group | $200K to $2M+ |
| Oracle Analytics Server (OAS) | Processor or NUP | 10 NUP/processor | Virtualisation: OAS VM on VMware cluster requiring full-cluster licensing | $500K to $5M+ |
| BI Publisher (standalone) | Processor or NUP | 10 NUP/processor | Embedded reporting: reports served to unlicensed users via portals | $100K to $1M+ |
| BI Publisher (bundled) | Included with OBIEE/OAS | N/A | Standalone use outside the OBIEE/OAS environment without separate licence | $100K to $500K |
| Essbase | Processor or NUP | Product-specific | Using Essbase without bundle entitlement; not licensed separately | $200K to $2M+ |
| Oracle Analytics Cloud (OAC) | Subscription (per user/OCPU) | N/A | Hybrid: on-prem BI not decommissioned after cloud migration | $100K to $500K duplicate costs |
OBIEE (Oracle Business Intelligence Enterprise Edition). Oracle's legacy full-suite enterprise BI platform providing dashboards, ad-hoc analysis, scorecards, and reporting. Includes the BI Server, Presentation Services, and BI Publisher as integrated components. Still widely deployed on-premises. Licensing: Processor or NUP, with BI Publisher included.
Oracle Analytics Server (OAS). The modern on-premises successor to OBIEE 12c with updated interface, integrated data visualisation, augmented analytics, and machine learning capabilities. Oracle generally allows OBIEE customers with active support to migrate to OAS under existing entitlement. Bundles BI Publisher and data visualisation. Licensing: identical to OBIEE. For a detailed OAS deep dive, see our Oracle Analytics Server Licensing Guide.
BI Publisher. Oracle's pixel-perfect reporting engine for generating formatted documents (PDFs, spreadsheets, Word). Bundled with OBIEE and OAS at no additional cost when used within those environments. If deployed standalone (for EBS, PeopleSoft, or custom applications), requires its own Processor or NUP licence.
Essbase. Oracle's multidimensional OLAP engine for financial modelling, planning, forecasting, and scenario analysis. May be included in certain BI bundles (legacy BI Foundation Suite) but is not automatically included with standalone OBIEE or OAS.
Oracle Analytics Cloud (OAC). Oracle's cloud-managed analytics service. Replaces the perpetual licence + support model with a consumption-based subscription (per user or per OCPU).
| Product | Role | Licence Metrics | Bundled With | Standalone Licence? |
|---|---|---|---|---|
| OBIEE | Full enterprise BI suite | Processor or NUP | Includes BI Publisher | Yes, standalone product |
| Oracle Analytics Server | Modern OBIEE successor (BI + viz + ML) | Processor or NUP | Includes BI Publisher + Data Viz | Yes, or upgrade from OBIEE |
| BI Publisher | Pixel-perfect reporting engine | Processor or NUP (if standalone) | Included with OBIEE/OAS | Yes, if used outside OBIEE/OAS |
| Essbase | Multidimensional OLAP / planning | Processor or NUP | BI Foundation Suite (legacy) | Yes, if not in entitled bundle |
| OAC | Cloud-managed analytics | Subscription (user/OCPU) | Complete cloud service | N/A, subscription model |
Processor licensing is the server-based model: you licence the BI software based on the physical processing capacity of the servers it runs on. Once processor licences are in place, unlimited users can access the BI system. This model is preferred for large-scale BI deployments, external-facing analytics portals, and scenarios where the user population is large or unpredictable.
The calculation follows standard Oracle processor counting rules: count all physical cores on the server, multiply by Oracle's core factor for that processor type (0.5 for Intel/AMD), and round up to the next whole number. For BI middleware products, the same core factor table applies as for Oracle Database.
When processor licensing is the right choice. Choose it when the BI deployment serves a broad audience (100+ users), when external users or partners access analytics, when the user count is unpredictable or growing, when multiplexing (web portals, APIs, embedded analytics) makes NUP counting impractical, or when virtualisation constraints make NUP minimums expensive anyway.
Non-production environments. Oracle requires licensing for every environment where the BI software is installed: production, development, test, staging, UAT, and disaster recovery. If your OBIEE/OAS installation exists on a DR server that is "normally offline," Oracle allows limited failover use (typically up to 10 days per year) without a separate licence. Beyond that, full licensing is required. See our Oracle DR licensing guide.
Named User Plus (NUP) licensing counts each distinct person or device that accesses the BI software. It can be more cost-effective than processor licensing for small, controlled deployments, but BI environments have unique characteristics that make NUP counting treacherous.
| Server Configuration | Processor Licences | NUP Minimum (10x) | Actual BI Users | NUP Licences Required |
|---|---|---|---|---|
| 2-socket Intel, 8 cores/socket | 8 | 80 | 25 analysts | 80 (minimum overrides actual) |
| 2-socket Intel, 8 cores/socket | 8 | 80 | 150 users | 150 (actual exceeds minimum) |
| VMware cluster: 4 hosts (soft partitioning) | 64 | 640 | 50 analysts | 640 (minimum on full cluster) |
The viewer trap. Oracle makes no distinction between a BI power user (report creator, analyst) and a read-only viewer. If a person logs into the BI system to view a dashboard, they require a NUP licence. If they receive a report via BI Publisher and interact with it through a portal, they require a licence. The only exception is a completely static report (a PDF emailed with no system interaction), but even this is debatable if the recipient can refresh or drill into data.
System and service accounts. Non-human access counts toward NUP licensing. Service accounts that connect to the BI system for automated report generation, data extraction, or API integration each require a NUP licence. Organisations frequently overlook these accounts, which can add 10 to 50+ unlicensed "users" to the count.
The breakeven calculation. Compare total NUP cost against processor licence cost for the same server. When NUP cost approaches or exceeds processor cost, switch to processor licensing. For OBIEE/OAS, the breakeven is typically around 100 to 200 users on a moderately sized server. For NUP counting rules, see our NUP vs Processor guide and NUP minimum requirements guide.
BI Publisher is one of the most frequently mis-licensed Oracle BI components because its licensing depends entirely on how it is deployed and used.
| BI Publisher Deployment | Licence Requirement | User Counting | Common Mistake |
|---|---|---|---|
| Integrated with OBIEE/OAS | Included, no separate licence | Covered by OBIEE/OAS licence | None: simplest scenario |
| Standalone server (outside OBIEE/OAS) | Requires own Processor or NUP licence | All users accessing reports must be licensed | Assuming OBIEE licence covers BIP on separate server |
| Embedded in custom application/portal | Requires licence for BIP server + all users | Every portal user who views/interacts with BIP reports | Counting only "BI users" not all report recipients |
| Reporting from EBS/PeopleSoft | Separate BIP licence required | All ERP users receiving BIP reports | Assuming EBS licence includes BIP usage |
| Included in Oracle SaaS (Fusion Apps) | Covered by SaaS subscription | No separate licence needed | Extending SaaS BIP to custom data sources |
The most common BI Publisher compliance risk occurs when reports are embedded in applications or portals that serve a large user population. If BI Publisher generates a report served through an internal portal to 2,000 employees, all 2,000 who interact with the BI Publisher system require licences. When in doubt, use processor licensing to cover unlimited users.
Essbase is frequently deployed alongside OBIEE/OAS but is not automatically included in a standard OBIEE or OAS licence. This distinction is the source of significant compliance risk.
| Scenario | Essbase Licence Required? | Licence Metric | Key Verification |
|---|---|---|---|
| Purchased BI Foundation Suite | No, included in bundle | Same as bundle | Ordering document must list "BI Foundation Suite" |
| Purchased OBIEE standalone + Essbase deployed | Yes, separate licence required | Processor or NUP | "OBIEE" alone does not include Essbase |
| Essbase via Smart View (finance team) | Depends on entitlement | NUP for each Smart View user or Processor | Count all Smart View users connecting to Essbase |
| Essbase used as OBIEE/OAS data source | Yes, OBIEE/OAS licence does not cover Essbase | Separate Essbase licence | BI licence does not equal Essbase licence |
| Included in Hyperion Planning suite | May be included, check bundle | Part of Hyperion entitlement | Verify Hyperion ordering document |
For small finance teams (10 to 30 users) accessing Essbase cubes, NUP licensing is typically more cost-effective. For broad Essbase access (100+ users or integration with enterprise dashboards), processor licensing provides unlimited user coverage.
| OAC Licence Model | How It Works | Best For | Cost Behaviour |
|---|---|---|---|
| Per User (Named User) | Monthly fee per named user with access to OAC | Defined user groups with predictable audience | Scales linearly with user count |
| Per OCPU (Compute Capacity) | Fee based on Oracle Cloud Processing Units allocated | Large or unpredictable user bases; analytics-intensive workloads | Scales with compute, not users (unlimited users) |
| Enterprise (ELA/cloud commitment) | Negotiated enterprise commitment with credits or fixed capacity | Large enterprises with significant OCI commitment | Volume discounts; consumption-based drawdown |
Hybrid deployment. Many organisations operate hybrid BI environments: some analytics on-premises (OAS/OBIEE) and some in OAC. The critical rule: on-premises components follow perpetual licence rules, while cloud components follow subscription rules. There is no cross-licensing. The most common hybrid mistake is migrating some workloads to OAC but not decommissioning the on-premises BI servers, resulting in duplicate costs.
BYOL to OCI. If you run Oracle Analytics Server on OCI as a self-managed instance (not OAC's managed service), you can use existing on-premises processor licences under BYOL. Standard conversion: 2 OCI vCPUs = 1 processor licence. NUP minimums still apply. See our Oracle BYOL guide.
Embedded analytics in Oracle SaaS. Oracle's SaaS applications (Fusion ERP, HCM Cloud, CX Cloud) include embedded analytics (OTBI). This is included in your SaaS subscription. However, you cannot use the embedded BI tools beyond the SaaS application's data. Connecting OTBI to external data sources requires separate licensing.
| Compliance Trap | How It Happens | Typical Exposure | Prevention |
|---|---|---|---|
| 1. Dashboard sprawl | Reports and dashboards created for one team are shared with broader audience. NUP count does not increase to match. | $200K to $2M+ | Access controls. Quarterly user audits. Switch to Processor if audience grows. |
| 2. Virtualisation scope expansion | OBIEE/OAS VM on VMware cluster. Oracle requires licensing all physical cores across all hosts. | $1M to $5M+ | Use Oracle VM (hard partitioning). Isolate BI on dedicated physical hosts. |
| 3. BI Publisher embedded in portals | BIP reports served through portals. All portal users require licences, not just "BI users." | $100K to $1M+ | Processor licensing for portal-facing BIP. Or restrict portal access. |
| 4. Unlicensed Essbase usage | Essbase deployed alongside OBIEE but not included in entitlement bundle. | $200K to $2M+ | Verify bundle entitlement. Licence Essbase separately if needed. |
| 5. Service account and API access | Automated processes, ETL jobs, and APIs access BI system but are not counted as licensed users. | $50K to $500K | Include service accounts in NUP count. Or use Processor licensing. |
| 6. DR and non-production environments | Test, staging, or DR servers running BI software without licences. | $100K to $1M+ | Licence all environments. Use DR failover allowance correctly (max 10 days/year). |
Virtualisation is the single most expensive Oracle BI licensing risk. Because BI servers are often considered "small" workloads, organisations routinely deploy OBIEE or OAS as VMs on shared VMware infrastructure. Oracle's soft partitioning policy then requires licensing every physical core across the entire cluster.
| Deployment | VM Config | Cluster Config | Oracle Licence Requirement |
|---|---|---|---|
| OAS on VMware (typical) | 1 VM, 8 vCPUs | 6-host cluster, 192 total cores | 96 processor licences (all hosts). Expected 4 procs; actual 96. |
| OAS on dedicated physical | Bare metal | 1 server, 32 cores | 16 processor licences. No gap. |
| OAS on Oracle VM (hard partitioning) | 1 VM, 8 vCPUs assigned | Same 6-host cluster | 4 processor licences (partition only). Hard partitioning honoured. |
Mitigation strategies. Deploy BI servers on dedicated physical hardware to limit licensing to specific server cores. Use Oracle-approved hard partitioning technologies (Oracle VM, Solaris Zones, IBM LPAR). If VMware is required, create a dedicated VMware cluster for Oracle workloads with minimum hosts and strict DRS affinity rules. Or accept the full-cluster requirement but negotiate aggressively on pricing, or include BI licensing in a broader ULA. For full virtualisation guidance, see our Oracle Licensing in Virtualised Environments guide.
1. Inventory all Oracle BI products installed across all environments: OBIEE, OAS, BI Publisher, Essbase, production, dev, test, staging, DR. Complete BI estate visibility.
2. Verify entitlement coverage for each product. Check ordering documents for bundle inclusions (BI Publisher with OBIEE/OAS; Essbase with BI Foundation Suite).
3. Map all BI users: named individuals, viewers, report recipients, service accounts, and API consumers accessing any BI system. Quarterly.
4. Assess virtualisation exposure. Identify all VMware/Hyper-V/KVM clusters hosting Oracle BI VMs. Calculate licence requirement under soft partitioning rules.
5. Evaluate Processor vs NUP for each deployment. Calculate breakeven. Switch to Processor if user count exceeds threshold or multiplexing applies.
6. Audit BI Publisher deployment. Confirm bundled vs standalone usage. Verify that standalone BIP servers have their own licences. Count all report recipients.
7. Verify Essbase entitlement. Check whether Essbase is included in your bundle or requires separate licensing. Count all Smart View and integration users.
8. Monitor dashboard sharing and access controls. Enforce security settings that restrict BI content to licensed user groups. Flag any audience expansion.
9. Track cloud analytics costs vs on-premises. If using OAC alongside on-prem BI, verify no duplicate costs. Decommission on-prem if fully migrated.
10. Conduct annual BI-specific compliance review. Simulate Oracle's audit methodology for BI products. Remediate gaps before Oracle finds them.
Oracle BI middleware products (OBIEE, OAS, BI Publisher, Essbase) require a minimum of 10 Named User Plus licences per processor, lower than the 25 NUP/processor minimum for Oracle Database Enterprise Edition. The "processor" is calculated using Oracle's core factor table. A 16-core Intel server requires 8 processor licences, so the NUP minimum is 80, regardless of how many users actually access the BI system.
Yes, BI Publisher is included at no additional cost when used as part of an OBIEE or Oracle Analytics Server installation. You do not need a separate licence for BI Publisher's integrated reporting capabilities. However, if BI Publisher is deployed on a standalone server, outside the OBIEE/OAS environment, it requires its own Processor or NUP licence.
Not automatically. Essbase was included in Oracle's legacy BI Foundation Suite bundle, but it is not included in a standalone OBIEE or OAS licence. Check your ordering documents: if they list "Oracle Business Intelligence Foundation Suite," Essbase is covered. If they list only "Oracle Business Intelligence Enterprise Edition," Essbase requires a separate licence.
Oracle treats VMware, Hyper-V, KVM, and other common hypervisors as "soft partitioning," requiring you to license all physical cores across every host in the cluster where the Oracle BI VM could potentially run. A single OAS VM with 8 vCPUs on a 6-host VMware cluster (192 total cores) may require 96 processor licences. This is typically the largest BI licensing risk. See our Oracle Partitioning Policy guide.
Yes. Oracle makes no distinction between BI power users and read-only viewers. Any person who logs into the BI system to view a dashboard, run a report, or interact with analytics requires a Named User Plus licence. The only potential exception is receiving a completely static report (a PDF email attachment) with no system interaction.
Use Processor licensing when the BI deployment serves more than 100 to 200 users, when external users or partners access analytics, when the user count is unpredictable, when multiplexing (web portals, APIs, embedded analytics) makes NUP counting impractical, or when virtualisation constraints make NUP minimums expensive. Processor licensing eliminates user counting entirely.
OAC uses subscription-based licensing: either per named user per month or per OCPU (Oracle Cloud Processing Unit). There are no processor or NUP licence purchases. The subscription covers the complete analytics platform. OAC licensing is separate from on-premises licensing. Your existing OBIEE/OAS licences do not offset OAC subscription costs.
Yes, if you run Oracle Analytics Server on OCI as a self-managed instance (not OAC's managed service). Standard BYOL conversion: 2 OCI vCPUs = 1 processor licence. NUP minimums still apply in cloud environments. This gives you cloud infrastructure flexibility while using existing licences, but you manage the BI software yourself.
Yes. Every non-human connection to the BI system (service accounts, automated ETL processes, API integrations, batch reporting jobs) requires a NUP licence or must be covered under processor licensing. Organisations frequently overlook 10 to 50+ service accounts, creating an unlicensed user gap that Oracle identifies during audits.
In a hybrid deployment, on-premises BI components (OAS/OBIEE) follow perpetual licence rules (Processor or NUP), while cloud components (OAC) follow subscription rules. There is no cross-licensing. The most common mistake is migrating some workloads to OAC but not decommissioning on-premises BI servers, resulting in duplicate costs (on-prem support fees + cloud subscription).
Our Oracle advisory team regularly uncovers BI compliance gaps and equally often finds organisations are over-licensed. An independent review can save you from audit exposure or unnecessary spend. Typical savings: $200K to $2M+. Independent. Fixed-fee. No Oracle bias.
Oracle Advisory ServicesIndependent Oracle BI licensing advisory. OBIEE, OAS, BI Publisher, Essbase, OAC. Fixed-fee. Vendor-independent.