Oracle’s analytics offerings, including Oracle Business Intelligence Enterprise Edition (OBIEE), Oracle Analytics Server (OAS), and Oracle Analytics Cloud (OAC), have their own licensing models that combine traditional on-premises licenses with modern subscription licensing.
In this section, we outline how OBIEE/OAS is licensed (Processor vs. Named User Plus metrics), the differences between on-premises and cloud analytics licensing, and special considerations such as whether you need to license underlying databases used by these BI tools.
OBIEE and Oracle Analytics Server (On-Premises)
OBIEE (Oracle Business Intelligence Enterprise Edition) was Oracle’s legacy on-prem BI platform (the last major version was 12c).
Oracle Analytics Server (OAS) is its successor, essentially an update of OBIEE’s capabilities rebranded for on-premises use by current customers.
Both OBIEE and OAS are licensed under the traditional Oracle model:
- Processor Licensing: You can license the BI server per processor. This is recommended when BI is accessed by a large or unknown number of users, such as in enterprise-wide dashboards or extranet scenarios. Under Processor licensing, you count the CPU cores of the servers hosting OBIEE/OAS, applying the core factor. This allows unlimited users access to the BI system. For example, an OBIEE server on eight cores (0.5 factor) = 4 processor licenses, and then any number of employees or external users can use the dashboards.
- Named User Plus Licensing: Alternatively, you can license OBIEE/OAS by Named User Plus. Oracle requires a minimum of 10 Named Users per processor for OBIEE【51†L172-L180】. So even a small OBIEE deployment triggers at least 20 NUP if the server is equivalent to 2 processors, for instance. NUP licensing is viable if you have a controlled, small user base, such as an analytics tool for a specific team. For example, a department with 30 analysts could license 30 NUP (which exceeds the 20 minimum for, say, 2 procs). If you had only 5 users, you would still need to license 10 (the minimum for one processor) or potentially 20, depending on the core count, which may require a minimum of 2 processors.
- Pricing Example: According to a recent reference, Oracle Analytics Server was priced around $2,000 per Named User Plus and $221,250 per processor (list prices). This steep processor price indicates Oracle expects many customers to use NUP if possible, or migrate to the cloud, where subscription pricing is different. The high processor price also reflects that one processor license covers a lot of users (unlimited, in fact), so it’s targeted at big deployments.
BI Publisher: Oracle BI Publisher is a reporting tool that often comes integrated with OBIEE. OBIEE’s license includes rights to BI Publisher when used within OBIEE’s context. That means if you’ve licensed OBIEE, you can use BI Publisher on that OBIEE server to create reports without needing a separate BI Publisher license.
If BI Publisher is used standalone, it requires a license. But most OBIEE/OAS customers just leverage the bundled BI Publisher and do not pay extra for it.
Oracle Analytics Server vs OBIEE licensing: Oracle has indicated that existing OBIEE customers with active support can transition to OAS without buying new licenses – OAS is effectively a continuation.
For new customers, OAS would be purchased using the same metrics. Oracle’s price list for OAS is similar, as noted above. So OBIEE and OAS licensing can be considered equivalent in the model (NUP or Processor).
Oracle Analytics Cloud (Subscription Model)
Oracle Analytics Cloud (OAC) is Oracle’s cloud-based analytics platform, offering similar capabilities to OBIEE/OAS but delivered as a cloud service. Licensing for OAC is subscription-based, not perpetual.
The metrics are typically:
- Per-user subscription: e.g., $X per month per named user (often with different tiers, such as Viewer vs. Creator). Oracle Analytics Cloud may have a minimum number of users. This model is straightforward for organizations that know how many people will use the analytics service.
- Per CPU (OCPU) Subscription: Sometimes, Oracle offers an OAC subscription by OCPU (Oracle Cloud CPU) to allow unlimited users on a certain amount of compute. For example, 1 OCPU might be priced at $Y per hour or per month, and that can handle many users. This is analogous to processor licensing, but on a cloud consumption model.
Oracle Analytics Cloud includes the necessary Oracle cloud infrastructure, and you do not separately license the underlying database or WebLogic – it’s all included in the service price.
In other words, if you use OAC, Oracle manages the environment, and your cost is just the subscription fee.
Flexibility: Some customers use their OBIEE/OAS licenses in Oracle Cloud (BYOL model), or trade them in via Oracle’s license mobility to get a discount on OAC.
Oracle’s cloud programs can be complex, but the key is that on-prem licenses don’t directly convert to OAC named user subscriptions; rather, Oracle might give you credit or allow you to run Analytics Server on an Oracle cloud VM using your licenses.
Special Considerations: Underlying Databases and Data Sources
A common question is: if OBIEE/OAS uses an Oracle Database as its repository or as a data source, do you need to license that database separately?
The answer:
- Repository Database: OBIEE/OAS requires a repository to store metadata, including RPD definitions, usage logs, schedules, etc. This repository can be an Oracle Database (or SQL Server, etc.) in OBIEE 12c. Oracle does not provide a “free” Oracle Database license for OBIEE’s repository in general. In the past, some Oracle products had restricted-use database rights for repositories. Still, modern OBIEE licensing requires you to use an existing Oracle DB license or a free edition, such as Oracle Database XE, if it’s sufficient. If you don’t have an Oracle DB license, you either:
- Use Oracle Database Express Edition (XE) for the repository (free, but limited size and CPU – adequate for small BI deployments).
- Purchase a Standard Edition 2 or EE license for the repository database, or use an existing licensed Oracle database server in your environment.
- Use a non-Oracle database for the repository, which would require its license from the vendor. OBIEE supports other RDBMS for metadata.
- Data Warehouse/Data Sources: OBIEE/OAS often connects to data warehouses or other databases to fetch data for reports. Those databases must be licensed separately. If your data warehouse is an Oracle Database, you need to license it according to its usage. Some people mistakenly think that an Oracle DB used only for OBIEE data is covered by OBIEE – it is not. The rule of thumb: OBIEE’s license covers only the BI application itself; all data sources (Oracle or otherwise) require proper licensing outside of OBIEE.
- Bundled BI Apps: Oracle offered products like Oracle BI Applications, which were pre-built analytics solutions for ERP and CRM. Those often included restricted-use database licenses for the ETL repository (Informatica) or required certain DB options. If you use these, please consult their specific licensing terms. But those are legacy; Oracle Analytics is more standalone nowadays.
Example: A company runs Oracle Analytics Server on two 8-core servers in a cluster. They use an Oracle Database 19c as the OBIEE repository, and the data source is a separate Oracle Database that houses a data mart.
How do they license?
- For OAS, they decide to use Processor licensing since the user base is 500+ across the enterprise (too many for NUP). 8 cores × 0.5 = 4 processors per server, and 2 servers = 8 processor licenses for OAS. This covers unlimited users【51†L152-L160】. They purchase 8 OAS processor licenses (or use existing OBIEE licenses).
- For the repository DB: It’s a small schema, could run on Oracle XE, possibly. If not, they might install it on their data mart DB as a separate schema. The data mart DB is already licensed for full use, so adding the repository schema there doesn’t change the licensing, since that DB is already fully licensed. If they choose to run a dedicated Oracle database for the repo, they would need to license it. Since only OAS is using it, they might opt for Named User Plus if the access is limited to the BI service accounts. However, a minimum of 25 NUP per processor would still apply for an EE database. Many clients avoid this by using an existing licensed database for the repository.
- For the data mart Oracle DB, it must be licensed for Oracle Database EE (or SE2) in the normal way (by cores or users). OBIEE querying it doesn’t magically cover it. They might already have that as part of their DW environment. If not, they need to take it into account.
On-Prem vs Cloud Summary
On-Prem (OBIEE/OAS): Perpetual licenses (plus annual support), metrics of Processor or NUP. You maintain infrastructure. High upfront cost, but then only support renewals ongoing.
Cloud (OAC): Subscription (OpEx). Simpler in that Oracle manages the stack; you just pay per user or per CPU monthly. It may include certain features that on-prem required options (e.g., maybe Data Visualization is included whereas on-prem it was an add-on).
One thing to note: Oracle Analytics Cloud and Server often include capabilities that used to be separate (like Data Visualization). Oracle had a product Data Visualization Desktop (DVD) which was user-based. Now, OAS includes DV at no extra cost. But if you wanted to use DVD standalone on-prem, you might need to license users for that.
Recommendations
- Choose the Right Licensing Model: Assess the number of users for your BI deployment. If it’s a small, known group (e.g., 30 finance analysts), Named User Plus licensing can save money【51†L172-L180】. Just ensure you meet minimums (10 per processor) and don’t exceed the count. If it’s enterprise-wide or customer-facing (unpredictable users), go with Processor licensing for OBIEE/OAS to avoid compliance risk and administrative overhead of counting users.
- Monitor User Counts if NUP: If you do license by Named Users, implement controls so that only authorized (licensed) users have access. OBIEE/OAS typically has an authentication mechanism; integrate it with your user directory and ensure a process to add a user includes verifying a license. Also, periodically review the actual user login counts vs. licenses. Oracle can audit OBIEE by asking for user lists or usage logs, so your records should reconcile with purchased NUP licenses.
- Leverage Existing Database Licenses: If you have to use an Oracle Database for OBIEE’s repository or data warehouse, try to use an already-licensed Oracle DB environment instead of spinning up a new one just for OBIEE. For instance, host the OBIEE schemas on an existing Oracle database server that has spare capacity. Ensure, however, that usage of that DB server by OBIEE doesn’t violate any restricted-use terms; usually, as long as it’s a full-use licensed DB, it’s fine to add schemas. This way you avoid needing a separate DB license purely for OBIEE metadata【54†L199-L207】【54†L209-L218】.
- Know What’s Included: Remember that OBIEE/OAS license includes BI Publisher and certain middleware:
- The OBIEE/OAS software includes WebLogic Server Standard Edition for running the OBIEE application, so you do not need to separately license WebLogic for it (unless you re-purpose that WebLogic for other apps, which you shouldn’t)【54†L145-L153】.
- BI Publisher is included for reporting as long as it’s used within the OBIEE/OAS environment【54†L150-L158】. No separate BI Publisher user or processor licenses needed if you’re just using it with OBIEE.
- If you have Oracle BI Applications (prebuilt analytics for ERP), note those often require Oracle Data Integrator or Informatica licensing and maybe database options. Make sure those components are accounted for. This gets complex, so consult Oracle’s BI Apps licensing guide specifically.
- Plan for Analytics Cloud if Appropriate: If you’re moving to cloud generally or find Oracle’s on-prem licensing too rigid, consider Oracle Analytics Cloud. It can simplify budgeting (you pay per month) and includes the platform fully managed. However, compare costs carefully – sometimes keeping existing on-prem licenses can be cheaper in the long run if you already paid for them. Oracle does have programs to let you trade in on-prem licenses for cloud credits (BYOL to PaaS). For instance, Oracle might let you apply your OBIEE processor licenses to get a reduced rate on OAC CPU usage【52†L101-L109】. Work with Oracle on these programs if interested.
- Audit Your Feature Usage: Oracle BI suite has various components (Mobile, Scorecard, etc.). If you enable a component that Oracle sells separately or as an option, ensure it’s covered. In current packaging, most features are included with OBIEE/OAS, but older OBIEE had optional modules like Oracle BI Mobile App Designer (though later included). Oracle Analytics Server now bundles Data Visualization which used to be separate. Keep an eye on license documents to know if anything you turn on (e.g., if you deploy Essbase as part of BI Foundation Suite) needs extra licensing. (Oracle’s BI Foundation Suite was a bundle of OBIEE + Essbase. If you only have OBIEE licenses, you can’t start using Essbase unless you have that bundle or separate Essbase licenses.)
- External Use: If you expose OBIEE analytics to external customers (not employees), you cannot use Named User Plus (since those users are not readily countable or could be thousands). Use Processor licensing in that scenario【51†L156-L163】. Also, consider if you need an Oracle Internet Application Server EE license for enabling things like SSO for external users – typically OBIEE includes its web server, so that’s fine, but ensure compliance with any Oracle middleware if integrated.
- Keep Proof of Licensing Terms: Retain Oracle’s documentation that states the minimums (like the Oracle Analytics Server licensing guide stating $2k per NUP, $221k per proc, etc., or the 10 NUP minimum rule)【51†L172-L180】. Also, Oracle’s Software Investment Guide or price list notes can be cited if Oracle audit personnel are unclear. Having the Oracle-published rules handy can expedite any discussions in your favor.
By understanding these BI licensing nuances, you can ensure your OBIEE/OAS deployment (or migration to OAS/OAC) is compliant and cost-optimized, and avoid nasty surprises (like an audit finding you under-counted users or used an unlicensed DB for your repository). Oracle BI tools are powerful – just align the licensing to how you deploy and use them.
