What is Oracle Analytics Server?
Oracle Analytics Server is Oracle's on premise enterprise analytics platform and the direct successor to Oracle Business Intelligence Enterprise Edition. It packages the same core capabilities, a semantic modelling layer, ad hoc analysis, interactive dashboards, pixel perfect reporting and self service data visualisation, into a single installable suite that runs in the customer's own data centre or private cloud rather than as an Oracle managed subscription.
For licensing purposes the most important fact about Oracle Analytics Server is its continuity with the product it replaced. OAS is licensed by either Processor or Named User Plus, exactly as OBIEE was, and the entitlements transfer rather than reset. A customer who understands the rules covered in the Oracle BI and analytics pillar already understands the foundations of OAS, because the rename did not change the metrics, the minimums or the audit surface.
Is OAS licensed per user or per processor?
Oracle Analytics Server can be licensed under either metric, and the correct choice is an arithmetic one rather than a preference. The Processor metric counts physical cores multiplied by the Oracle core factor and is indifferent to the number of users, which makes it efficient for broad or anonymous audiences such as a customer facing portal. Named User Plus counts authorised individuals subject to a minimum of ten per processor, which favours small, well defined communities.
The Analytics Server metric you should hold is the one the arithmetic chooses against today's hardware and today's user count, not the one inherited unexamined from an OBIEE order placed years ago.
The per processor minimum is the decisive variable, exactly as it is for the BI Server beneath the suite. A small analyst community on large hardware can owe more under Named User Plus minimums than the headcount implies, because the hardware footprint sets the floor at ten times the processor count. Modelling both metrics against the real topology is the only reliable way to choose, and the calculation should be repeated whenever the user population or the server estate changes.
The OBIEE to Analytics Server upgrade path
The transition from OBIEE to Oracle Analytics Server is, contractually, an upgrade rather than a repurchase. A customer with active support is entitled to deploy OAS under the existing OBIEE licences, and the Processor or Named User Plus counts carry forward unchanged. This is the single most valuable feature of the support stream, because it converts a maintained perpetual estate into the current product without a new licence transaction.
The corollary is that lapsed support forecloses the upgrade. A customer who dropped support to save money is frozen on the OBIEE version, loses the right to OAS, and faces back support fees plus reinstatement penalties to recover the entitlement. The continuity detailed in the OBIEE licensing guide only holds while support is maintained, which is why we treat the support decision as strategic rather than a discretionary line item.
What the Analytics Server licence bundles
Oracle Analytics Server bundles the BI Server semantic layer, the classic analysis and dashboard tooling, modern self service data visualisation, and a constrained use of BI Publisher for reporting. The grants are real but bounded, and the boundaries are precise, contractual, and easy to overstep without noticing.
| Component | Bundled use | Where the grant ends |
|---|---|---|
| BI Server | Semantic layer for the suite | Feeding non Oracle visualisation tools |
| Analyses and dashboards | Interactive analysis within the suite | Embedding in external applications |
| Data Visualization | Self service authoring within OAS | Standalone desktop distribution at scale |
| BI Publisher | Reporting within OAS | High volume or external document generation |
The BI Publisher boundary is the most frequently crossed. Generating high volumes of external facing documents from the embedded engine can exceed the constrained grant and require a standalone BI Publisher licence. The BI Server boundary matters too: pointing the semantic layer at a non Oracle front end to avoid licensing more OAS users can itself constitute use beyond the grant.
Analytics Server on virtualised infrastructure
Oracle Analytics Server deployed on a VMware cluster invites the same soft partitioning argument Oracle applies to the database. Oracle's partitioning policy treats VMware as soft partitioning, meaning Oracle may assert that the licensable footprint is the entire cluster the workload could theoretically migrate to, not merely the hosts where OAS runs. On a large virtualised estate this can multiply the processor count several fold.
Containing the argument requires either hard partitioning, using a technology Oracle recognises as limiting the licensable boundary, or contractual language that fixes the footprint. The structure of the dispute is identical to the database virtualisation debate, and the buyer side defence is the same: document the actual deployment, establish the partitioning boundary with evidence, and refuse to concede the whole cluster on the strength of a policy document that is not part of the contract.
Bringing OAS licences to the cloud
Active Oracle Analytics Server licences can be brought to Oracle Analytics Cloud under Bring Your Own Licence, subject to a conversion ratio between the perpetual metric and the cloud subscription unit. The option preserves the value of a maintained estate while moving the workload to Oracle managed infrastructure, and it is frequently cheaper than buying a fresh OAC subscription outright.
The decision should be modelled rather than defaulted. A perpetual OAS estate with paid up support can be cheaper to run than an equivalent Oracle Analytics Cloud subscription for a stable workload, while a growing or seasonal workload can favour consumption based cloud pricing. Stranding perpetual value in a hasty migration is a common and avoidable error.
Development, test and disaster recovery
A production Analytics Server platform is rarely alone. Development, test, staging, training and disaster recovery environments accompany it, and Oracle's default position is that every environment where OAS is installed and running requires licensing under the same metric as production. The assumption that non production environments are free is one of the most expensive analytics misconceptions.
| Environment | Typical state | Licensing position |
|---|---|---|
| Production | Running | Fully licensed |
| Development / test | Running | Licensed unless contractually exempt |
| Cold DR standby | Installed, not running | May avoid requirement |
| Warm / active DR | Running | Licensed; failover window limited |
Disaster recovery is governed by Oracle's failover policy, which permits a limited window, commonly cited as up to ten days per calendar year, during which a single designated failover node can run unlicensed. The conditions are precise and easily breached by a DR test that overruns or a standby kept warm for fast recovery. Choosing a cold standby where the recovery objective permits can materially reduce the licensable footprint.
Containing Analytics Server audit exposure
A defensible OAS position rests on knowing the bundle boundaries cold, modelling the metric honestly, fixing the virtualisation boundary in advance, and accounting for every environment. Performing this independent measurement before an audit reaches the contractual interpretation first and frames the conversation on the buyer's terms. It is the same discipline our practice applies across every Oracle product line, and it reproduces on the buyer's behalf the analysis an LMS review would otherwise impose.
An Analytics Server self assessment checklist
A buyer can establish a defensible position with a structured self assessment. First, an environment inventory: every OAS and residual OBIEE instance, classified by operational state, with non production and DR confirmed as licensed or genuinely exempt. Second, a component review: which bundled capabilities are in use, and whether any, particularly BI Publisher for external documents, exceed their embedded grants. Third, a metric reconciliation against current hardware and the real multiplexed user population, including the per processor minimum. Fourth, a virtualisation review that establishes the partitioning boundary with evidence before Oracle asserts the whole cluster. Completed together, these steps reproduce the conclusions an LMS review would reach, which is precisely the point.
Oracle Analytics Server licensing: a summary
The practical core of Oracle Analytics Server licensing is continuity with OBIEE. The metrics, Processor and Named User Plus, are unchanged, the entitlements convert under active support, and the audit surface, virtualisation, non production environments and embedded BI Publisher, is identical. The rename did not reset the rules; it preserved them.
The decisions with the largest cost consequence are metric selection, which must be re modelled against current hardware and the per processor minimum, and the cloud question, where active licences can move to OAC under BYOL but perpetual value can be stranded by a hasty migration. A buyer who maps the components to their grants, models the metric honestly, fixes the virtualisation boundary in advance and protects the support stream will hold a defensible OAS position rather than discovering one under audit.
The buyer side view
Oracle Analytics Server rewards buyers who treat it as OBIEE under a new name rather than a new product. The entitlements carry forward, so the priority is protecting the support stream that underpins the upgrade and the BYOL path, then re modelling the metric and fixing the virtualisation boundary before any audit. Begin with the BI and analytics pillar for the metric foundations, then audit your own component boundaries one by one.
Oracle Analytics Server is the renamed and re engineered on premise successor to OBIEE. The licensing metrics, Processor and Named User Plus, carry forward unchanged, and existing OBIEE entitlements convert to OAS under active support. The continuity is set out in the OBIEE licensing guide. No. With active support an OBIEE customer is entitled to deploy Oracle Analytics Server under the existing licences and metrics. The upgrade is a version entitlement, not a new purchase, which is why lapsed support is so costly. Active OAS licences with the right metric can be brought to Oracle Analytics Cloud under Bring Your Own Licence, subject to a conversion ratio. Model the economics before committing because perpetual value can be stranded. Oracle treats VMware as soft partitioning and may assert that the whole cluster the workload could migrate to is licensable. Containing this requires hard partitioning evidence or contractual language, the same debate covered in the database licensing guide.Oracle Analytics Server licensing: frequently asked questions
Is Oracle Analytics Server the same as OBIEE?
Do I need new licences to upgrade from OBIEE to OAS?
Can I move Oracle Analytics Server licences to the cloud?
How is Oracle Analytics Server counted on VMware?
Related analysis in this cluster: Oracle OBIEE licensing, Oracle Analytics Cloud licensing.