Oracle Analytics Server (OAS) is the on-premises successor to OBIEE — and it carries the same expensive, audit-prone licensing model. This guide covers every metric, pricing detail, virtualisation trap, and negotiation lever you need to control OAS costs in 2025–2026.
Oracle Analytics Server 12.2.1.4 reached Extended Support end in November 2024 — meaning enterprises running OAS on-premises are now paying Oracle for extended support at premium rates, or facing unsupported production analytics infrastructure. For IT and procurement leaders evaluating their options, the licensing cost is only half the story.
For organisations that cannot or will not move their BI infrastructure to the cloud, OAS represents Oracle's strategic on-premises path. Oracle has committed to continuing OAS development and has released version 7 with AI-driven analytics features. However, Oracle's commercial strategy is unmistakable: OAS licensing is structured to make cloud migration financially attractive, and Oracle's sales teams will consistently push customers toward Oracle Analytics Cloud (OAC) at every renewal interaction.
Understanding OAS licensing in depth is essential for any organisation running OBIEE today, evaluating a migration from OBIEE to OAS, or negotiating a new OAS deployment. The licensing model is deceptively simple on the surface — two metrics, straightforward pricing — but the underlying rules around minimum user counts, virtualisation, database licensing, and support fees create significant financial exposure for organisations that don't manage their position carefully.
In one engagement, a European insurance group was running Oracle Analytics Server on three production servers with a Processor licence for each. Redress Compliance identified that two servers met the Named User Plus threshold — reducing annual support from $480,000 to $194,000. The engagement fee was less than 5% of the annual saving.
Oracle Analytics Server is licensed using two metrics that Oracle uses across most of its middleware portfolio: Named User Plus (NUP) and Processor. Understanding both — and choosing the right one for your deployment — is the first critical decision in OAS cost management.
A Named User Plus licence covers a single identified individual who accesses or uses OAS, regardless of how frequently or infrequently they connect. The list price is $2,000 per Named User Plus. This model works best for deployments with a well-defined, relatively small user base where you can identify every individual who needs access.
The critical constraint is the minimum of 10 NUP licences per processor on the server running OAS. Oracle determines processor count using its core factor table — for Intel and AMD processors (the vast majority of enterprise deployments), the core factor is 0.5, meaning an 8-core server counts as 4 processors. That 8-core server therefore requires a minimum of 40 NUP licences, regardless of whether you have 5 actual users or 40.
This minimum means NUP licensing for OAS is rarely as cheap as it first appears. An organisation with 15 actual users deploying OAS on a standard 2-socket, 16-core server (counting as 16 processors under Oracle's rules without core factor adjustments — or 8 processors with the 0.5 Intel factor) faces a minimum of 80 NUP licences. At $2,000 per NUP, that is $160,000 in licence fees before a single discount is applied.
A Processor licence covers the entire physical processor (calculated using Oracle's core factor table), allowing unlimited users and unlimited concurrent connections. The list price is $221,250 per Processor. This metric is typically more cost-effective when user numbers are large, user counts are difficult to track, or access is granted to external parties or unidentified individuals.
Processor count is calculated by multiplying total physical cores by the applicable core factor. For an Intel Xeon server with two 12-core processors (24 total cores), the calculation is 24 × 0.5 = 12 Processor licences required, at a list price of $2,655,000. Even at a 60% discount, that is over $1 million in licence fees for a standard 2-socket server.
This is why Processor licensing for OAS is typically reserved for large enterprise deployments, extranet use cases, or situations where user counts are genuinely unknown. For most mid-market deployments, the economics of NUP licensing are significantly better — provided the minimum requirements don't eat into the savings.
Use Redress Compliance's interactive tool to calculate your OAS licensing position under both NUP and Processor metrics — and identify the lower-cost option for your deployment.
Calculate Your OAS PositionOracle's published list prices for OAS are: $221,250 per Processor and $2,000 per Named User Plus. These are rarely what organisations actually pay — Oracle's standard discount range for OAS is 40–60% off list — but list price is the starting point for all negotiations and the basis for audit back-billing if undercompliance is found.
Annual support for OAS is charged at 22% of the net licence price (i.e., the price actually paid after discount, not list price). Support covers access to patches, bug fixes, security updates, and new software versions. It is mandatory if you want to remain eligible for software updates and maintain Oracle's upgrade rights.
What many OAS customers underestimate is how support costs compound over time. Oracle has historically increased support fees by 8% per year. An OAS deployment that costs $400,000 in support in year one will cost over $740,000 annually by year ten — even with no additional software purchased. Across a ten-year deployment lifecycle, support fees alone can exceed the original licence cost by a significant margin.
This compounding dynamic is one of Oracle's most powerful commercial mechanisms. Customers who signed OAS or OBIEE deals in the early 2010s are now paying support fees several times higher than their original commitments. Capping or freezing support escalation is one of the most valuable concessions Redress negotiates in Oracle renewals — but it requires early, well-prepared engagement with Oracle's commercial team.
OAS support (Oracle's Software Update Licence and Support, or SLUS) provides access to My Oracle Support, software patches and updates, new OAS versions, and technical support services. It does not provide implementation services, customisation support, or training. Critically, it also underpins your ability to upgrade OAS versions — lapse support and then attempt an upgrade, and Oracle will require reinstatement fees equal to all lapsed support plus an uplift penalty before allowing the upgrade.
For organisations still running OBIEE 11g or 12c, migration to OAS is now an operational necessity. Oracle ended Premier Support for OBIEE 12.2.1.4 (the final OBIEE version) in December 2023, and Extended Support concludes in December 2025. After that date, OBIEE customers will have no access to security patches or Oracle-supported fixes — a material risk for any organisation running regulated workloads or handling sensitive data.
Existing OBIEE customers with active support contracts are entitled to upgrade to OAS without purchasing new licences. Oracle treats OAS as the successor product, and your existing OBIEE Processor or NUP licences convert directly. This is a significant entitlement — OAS list prices are substantially higher than the prices many OBIEE customers originally paid — but it only applies while support is maintained.
Customers who allowed OBIEE support to lapse — a strategy some organisations pursued to reduce costs — have lost this upgrade right. If you are in this position, you face a choice between reinstating support (and paying back-support fees plus uplift) or purchasing OAS licences fresh. Before accepting Oracle's reinstatement terms, get independent advice — the reinstatement calculation methodology is often negotiable, and Oracle's initial demand is rarely the final position.
The technical migration from OBIEE to OAS is well-documented and Oracle provides a migration utility for converting existing OBIEE content, including RPDs (repository files), web catalogue objects, and security configurations. In-place upgrades preserve existing environments, while out-of-place upgrades build a clean OAS environment and migrate content across. Oracle recommends out-of-place upgrades for OBIEE 11g customers given the architecture differences.
What organisations often underestimate is the metadata and dashboard remediation required after migration. OBIEE content built over years frequently contains deprecated features, custom code, or deprecated connection methods that do not migrate cleanly. Budget for a minimum of 20–30% of migration project time for post-migration content remediation — more if your OBIEE environment contains significant custom development.
Oracle's virtualisation licensing policy — which Redress considers the single most significant source of unplanned licence exposure across the enterprise software estate — applies as forcefully to OAS as it does to Oracle Database. Understanding Oracle's position is not optional; the consequences of getting it wrong are financially severe.
Oracle does not recognise VMware ESXi, Microsoft Hyper-V, or KVM as "hard partitioning" technologies. Under Oracle's policy, these are classified as "soft partitioning" — and soft partitioning does not limit the licence requirement. If your OAS server is running as a VM on a VMware cluster, Oracle's position is that you must licence every physical server in the cluster, not just the servers the OAS VM currently runs on.
The practical impact is stark. An organisation that deploys OAS on a 4-node VMware cluster — each node with two 20-core processors — could face a licence requirement of 80 processors (4 nodes × 2 sockets × 20 cores × 0.5 core factor = 80 processors) at a list price of $17.7 million. If the organisation licensed only the 2 processors the OAS VM was actually allocated, it faces an $17.4 million compliance gap under Oracle's interpretation.
Oracle's LMS team is trained to identify exactly this situation. During an Oracle licence audit, auditors will request VMware configuration files and cluster topology maps. If OAS VMs are running on clusters that are not fully licensed, the financial exposure can dwarf the original licence investment.
The correct approach for organisations running OAS in virtualised environments is either to deploy OAS on Oracle VM (which Oracle does recognise as hard partitioning), isolate OAS VMs to dedicated hosts not participating in vMotion or DRS, or licence the full cluster. Each of these options has cost and operational implications that need to be modelled carefully before committing to an architecture.
If your OAS deployment runs on VMware, Hyper-V, or KVM, your licence position may be significantly under-licensed under Oracle's policy. Redress Compliance provides a confidential virtualisation licence review that quantifies your exposure and identifies remediation options — without alerting Oracle.
Request a Confidential ReviewEvery OAS renewal or new deployment now involves an implicit comparison with Oracle Analytics Cloud (OAC). Oracle's sales team will make this comparison explicit, presenting OAC as a modern, lower-risk alternative to on-premises OAS. The financial reality is more nuanced.
OAC pricing starts at $16/user/month for the Professional edition and $80/user/month for Enterprise, or $1.08/OCPU/hour and $2.15/OCPU/hour respectively for consumption-based billing. BYOL (Bring Your Own Licence) customers with existing OAS licences can access OAC at $0.32/OCPU/hour. For organisations already holding OAS licences with active support, BYOL OAC can be a cost-effective route to cloud analytics without additional licence investment.
However, OAC carries ongoing subscription costs that compound in a different way from OAS perpetual licences. An OAC Enterprise deployment for 500 users costs $40,000/month ($480,000/year). After five years, that organisation will have spent $2.4 million on OAC subscriptions — a figure that would have purchased substantial OAS perpetual licences with decades of use remaining.
The right answer depends on your organisation's strategic direction, data residency requirements, existing Oracle investment, and total cost of ownership horizon. Redress Compliance's OAS vs OAC analysis framework models both paths using actual licence positions and 10-year TCO, helping organisations make the decision on financial evidence rather than Oracle's marketing narrative.
Oracle Licence Management Services (LMS) — now renamed Oracle Software Security Assurance — audits OAS customers for the same categories of non-compliance it targets in database audits. Understanding these risk areas is essential for any organisation preparing for or responding to an Oracle audit.
The most frequent OAS compliance issues Redress encounters are: user counts exceeding licensed NUP quantities (especially common when OAS is connected to enterprise authentication systems that provision access broadly); Processor calculations that do not account for all physical cores in the server or virtualisation cluster; use of OAS components (such as Oracle BI Publisher, which is included in OAS) deployed independently on additional servers without corresponding licences; and OAS deployments on non-production environments that are mistakenly excluded from the licence count.
Oracle's LMS script for middleware collects server hardware configurations, installed software versions, JVM parameters, and connection log data. The collection process takes approximately 15 minutes but generates data that Oracle's analysts spend weeks reviewing. Any discrepancy between your declared licence position and the evidence in the LMS output will be raised as a compliance finding, with back-billing calculated at list price.
One frequently overlooked compliance risk: OAS requires a relational database for its metadata repository (the "RPD database"). If you use Oracle Database for this repository — the most common configuration — that Oracle Database instance must be separately licensed. OAS does not include a database licence. Organisations that deploy OAS and assume the metadata repository database is covered by the OAS licence are creating a compliance gap from day one.
Additionally, if OAS connects to Oracle Database data sources for analytics, those Oracle Database instances must also be independently licensed. The OAS licence covers the analytics server itself, not the data it analyses.
OAS negotiation requires the same structured preparation that Redress brings to all Oracle commercial engagements. Oracle's list prices are a starting point, not a floor — and the gap between list and achievable price is substantial.
The most effective OAS negotiation levers are: competitive alternatives (Microsoft Power BI at a fraction of the cost, Tableau, Qlik, or MicroStrategy all represent credible alternatives Oracle does not want to lose to); OAC migration leverage (expressing willingness to migrate to OAC in exchange for commercial improvements on OAS can unlock significant discounts Oracle wouldn't otherwise offer); Oracle fiscal year dynamics (Oracle's Q4, March through May, is when sales teams have maximum motivation to close — using this window strategically can yield additional concessions of 5–15% beyond standard pricing); and support cap negotiations (requesting a contractual cap on annual support increases is achievable at renewal time and saves exponentially increasing amounts over a 5–10 year horizon).
Bundling OAS renewals with other Oracle products — database, middleware, or application licences — also gives Oracle's account team more flexibility, as the larger deal value unlocks regional approval authority that a standalone OAS deal does not. Redress has negotiated OAS deals at 60–70% below list price when all available levers have been applied correctly and the organisation has maintained genuine alternatives credibility.
The single most damaging negotiation error is allowing Oracle to set the timeline. Oracle's sales team will create artificial urgency — special pricing windows that expire, deal registrations that lapse, approvals that must be renewed. Organisations that respond to Oracle's timeline rather than their own give up the majority of their negotiating leverage. Start the engagement six to nine months before any commitment is required, maintain credible walk-away options, and never allow Oracle to know how dependent you are on its platform.
Effective Oracle Analytics Server licence management is not a one-time exercise — it is an ongoing operational discipline. The organisations that avoid Oracle audit exposure and negotiate the best commercial outcomes are those that maintain structured, documented licence management processes throughout the deployment lifecycle, not just in the weeks before a renewal or audit notification.
The foundation of OAS compliance is knowing exactly where OAS is installed and on what hardware. Every OAS installation — including development, test, staging, and disaster recovery environments — must be inventoried against your licence entitlements. Oracle does not automatically exclude non-production environments from licensing obligations; under Oracle's standard licence terms, unless your contract explicitly carves out non-production instances, every installed copy requires a licence. Many organisations discover significant compliance gaps in test and development environments only during an audit, when it is too late to resolve the issue without financial penalty.
Maintain a live inventory that maps OAS installation locations to specific server hardware specifications (including core counts and processor types), the number of licensed Named User Plus users or Processors at each location, the contractual basis for each licence (purchase order, ULA, or ULA equivalent), and any specific contractual carve-outs for non-production environments.
Redress Compliance recommends that organisations with significant OAS deployments conduct an internal Oracle licence audit at least annually, using the same data sources Oracle's LMS team would collect — server hardware configurations, OAS installation logs, and user access records. This internal review gives you advance visibility of any compliance gaps before Oracle's auditors find them, and the time to remediate on your own terms rather than Oracle's.
Annual internal audits also produce an accurate picture of OAS usage patterns that is essential for renewal negotiations. If your actual user base is significantly smaller than your NUP licence count, that data supports a commercial case for right-sizing at renewal. If usage has grown beyond your Processor licence count, the internal audit gives you the opportunity to address the gap proactively — typically at a much lower cost than an audit-driven remediation.
Named User Plus compliance for OAS requires active management of user provisioning and de-provisioning. In enterprise environments with Active Directory or LDAP-based authentication, OAS access is often granted through group membership — and group membership frequently expands without formal licence review. A user provisioned into an OAS-enabled security group triggers a new NUP licence requirement, regardless of whether that user ever actually logs into OAS.
Establish a licence gate in your OAS user provisioning process: every new access request should trigger a licence availability check before access is granted. De-provisioning processes are equally important — users who leave the organisation or move to roles that do not require OAS access should be removed from the licence count promptly. Oracle allows NUP re-allocation to new users, but the total number of licensed users cannot be exceeded at any point.
Whether you're preparing for an Oracle audit, renewing OAS support, or evaluating a migration to OAC, Redress Compliance provides independent expert advice with zero Oracle commercial relationships.
Book a Free ConsultationA European financial services organisation operating OAS across a multi-node VMware cluster received an Oracle LMS audit notification. Initial internal assessment suggested a compliance gap of around €500,000 — manageable but uncomfortable. Oracle's preliminary findings, delivered six weeks into the audit, claimed €4.8 million in back-licence and support fees, based on Oracle's position that the entire VMware cluster required licensing.
Redress Compliance was engaged to review Oracle's findings and prepare a technical and commercial response. Our analysis identified three material errors in Oracle's calculation: incorrect core factor application for two server generations, double-counting of standby environments that were contractually excluded, and an overcount of active NUP users based on directory data rather than actual OAS logins.
After a structured challenge process — supported by independent technical evidence and a detailed counter-analysis — the final settlement was €620,000, an 87% reduction from Oracle's initial claim. The settlement also included a contractual cap on future support increases. See more Oracle audit case studies to understand how structured challenge changes outcomes.
Redress Compliance has managed Oracle Analytics Server and OBIEE licensing challenges across industries ranging from financial services and retail to healthcare and public sector. Our OAS advisory work spans licence position assessments, virtualisation architecture reviews, OBIEE-to-OAS migration planning, audit defence, and commercial negotiations.
What distinguishes Redress is independence: we have no commercial relationship with Oracle, no referral fees, and no incentive to recommend any particular outcome. Our advice is built entirely on what is financially and commercially optimal for our clients. We are Oracle licensing advisors, not Oracle channel partners.
Our co-founders have over 20 years of enterprise software licensing experience each, having advised organisations from FTSE 100 companies to mid-market enterprises on Oracle commercial strategy. That depth of experience means we recognise the patterns in Oracle's commercial behaviour that less experienced advisors miss — and we know exactly how to use them to our clients' advantage.
Expert guidance across the Oracle licensing landscape
Independent expertise. Zero Oracle commercial relationships.
Independent review of your OAS deployment against your contracted licence position — before Oracle's auditors do it for you.
Learn MoreExpert challenge of Oracle LMS findings across OAS, database, middleware, and applications — with a track record of 80%+ claim reductions.
Learn MoreStructured OAS and Oracle support renewal negotiation — achieving 40–60% off list price with support cost caps.
Learn MoreRedress Compliance's Vendor Shield programme provides ongoing Oracle licence management, audit readiness monitoring, and commercial intelligence — protecting your organisation before Oracle acts.
Continuous licence position monitoring
Quarterly commercial intelligence reports
Immediate audit response support
Renewal negotiation included