Running Oracle? Find out exactly what you're overpaying. Free cost analysis, no commitment.
500+ enterprise clients · Est. 2016 · 15-min response · No commitment
Oracle Business Intelligence Enterprise Edition (OBIEE) — now branded Oracle Analytics Server (OAS) in on-premises deployments — has been the enterprise reporting and analytics platform for Oracle EBS, PeopleSoft, JD Edwards, and Fusion Applications customers for over 20 years. Oracle BI Publisher (XML Publisher) handles regulatory and operational report output across these same environments. Together, these components form the analytics and reporting layer for thousands of enterprise Oracle deployments worldwide.
Oracle's strategy is clear: end OBIEE on-premises and migrate customers to Oracle Analytics Cloud (OAC), a SaaS subscription product that carries a substantially higher per-user annual cost than OBIEE on-premises support. If you're running OBIEE 11g, OBIEE 12c, or Oracle Analytics Server 5.x/6.x on-premises, you're receiving migration pressure — and your support costs may be growing as Oracle reduces investment in the on-premises platform.
This article provides an independent assessment of your OBIEE support options, the OAC migration economics, and how third-party support provides a credible alternative path.
OBIEE Support Lifecycle and the OAC Migration Pressure
OBIEE 11g — Already in Sustaining Engineering
OBIEE 11g reached end of Premier Support in January 2022. As of 2026, OBIEE 11g is in Sustaining Engineering — meaning Oracle provides no new bug fixes, no new security patches, and no regulatory updates. If you're running OBIEE 11g and paying Oracle's 22% annual maintenance fee, Oracle has formally wound down its support obligation while continuing to invoice you. Third-party support for OBIEE 11g provides the security remediation and break-fix coverage that Oracle's Sustaining Engineering designation explicitly excludes.
OBIEE 12c / Oracle Analytics Server 5.x — Approaching End of Premier Support
OBIEE 12c (12.2.1.x) and its rebrand as Oracle Analytics Server (OAS) 5.x reached end of Premier Support in March 2024. OAS 6.x (2023) is currently in Premier Support but approaching the typical 4–5 year window. Oracle uses the convergence of these timelines to accelerate OAC migration conversations.
Oracle Analytics Cloud (OAC) Pricing Reality
Oracle positions OAC as a natural migration path from OBIEE. The commercial reality is that OAC is priced on per-user OCPU-based subscription that, for large OBIEE deployments with hundreds or thousands of named or concurrent users, typically costs 2–4× more than current OBIEE on-premises support fees. For organisations with deeply embedded OBIEE deployments — extensive custom RPD metadata, BI Publisher report catalogues, Delivers alert customisation, and EBS/PeopleSoft integration — the migration cost and disruption are substantial on top of this subscription premium.
Running OBIEE 11g or 12c in production?
Oracle has wound down support for OBIEE 11g but is still charging 22% per year. Get an independent assessment of what third-party OBIEE support costs — versus OAC migration.
Get Free OBIEE Assessment →OBIEE / OAS Version Support Matrix
| Version | Oracle Branding | Oracle Premier Support End | Oracle Status (2026) | TPS Available |
|---|---|---|---|---|
| OAS 6.x / OAC 2023+ | Oracle Analytics Server 6 | ~2027–2028 | Premier Support | ✓ Yes |
| OAS 5.x / OBIEE 12.2.1.5 | Oracle Analytics Server 5 | Mar 2024 | Extended/Sustaining | ✓ Full TPS |
| OBIEE 12c (12.2.1.1–12.2.1.4) | Oracle BI 12c | 2021–2022 | Sustaining Engineering | ✓ Full TPS |
| OBIEE 11g (11.1.1.9.x) | Oracle BI 11g | Jan 2022 | Sustaining Engineering | ✓ Full TPS |
| OBIEE 11g (11.1.1.7.x and earlier) | Oracle BI 11g | 2018–2020 | Sustaining Engineering | ✓ Full TPS |
| OBIEE 10g and earlier | Oracle BI 10g / Siebel Analytics | 2012–2014 | Sustaining Engineering | ✓ Full TPS |
What Third-Party Support Covers for OBIEE
- Break-fix support for OBIEE 11g, OBIEE 12c, and Oracle Analytics Server 5.x on-premises deployments
- RPD (Repository / Semantic Layer) issues — metadata corruption, query generation failures, column mapping errors
- Oracle BI Publisher support — template failures, report rendering issues, bursting configuration, delivery manager
- Oracle Delivers (iBot/Agent) alert and delivery pipeline troubleshooting
- OBIEE–EBS integration support: BI Financials, BI Human Resources, BI Supply Chain analytics content areas
- OBIEE–PeopleSoft, OBIEE–JD Edwards integration support for content package environments
- Security vulnerability remediation with CVE documentation
- WebLogic and Fusion Middleware support for OBIEE application server layer
- Oracle Database support for OBIEE catalog and data source layers
- Performance tuning — query plan analysis, cache optimisation, NQS parameter tuning for large-scale environments
- LDAP/Active Directory integration support, SSO configuration (SAML/Kerberos)
- Answers and Dashboards (front-end) issue resolution, prompted filters, dashboard prompts
Oracle Analytics Cloud Migration: The Reality
Oracle positions OAC migration as a straightforward lift-and-shift from OBIEE. Most organisations that have attempted a full OBIEE-to-OAC migration have encountered significantly more complexity:
- RPD migration is not seamless. The OAS/OAC semantic model differs from the OBIEE 11g/12c RPD in several areas. Organisations with large, complex RPDs — particularly those with extensive aggregate rules, complex hierarchy definitions, or non-standard data types — often find that migrated RPDs require significant rework.
- BI Publisher is being deprecated in OAC. Oracle is not investing in BI Publisher in the cloud. Organisations heavily dependent on BI Publisher reports — financial statements, regulatory reports, complex formatted output — face a difficult choice: migrate to OAC's native Data Visualisation for analytical reporting while retaining BI Publisher on-premises (a hybrid that adds complexity), or re-engineer all Publisher reports in a different format.
- EBS/PeopleSoft content areas may not migrate cleanly. Oracle's prebuilt analytics content for EBS Financials, HR, and Supply Chain does not have a direct equivalent in OAC. Organisations that have customised these content areas face re-engineering rather than migration.
- Per-user OAC subscription costs exceed OBIEE support at scale. For organisations with 200+ OBIEE users — common in medium-to-large enterprise environments — the annual OAC subscription typically costs more than 2× the current OBIEE on-premises support fee.
Oracle Support Cost Reduction Playbook
54-page guide covering support cost reduction across Oracle EBS, Database, OBIEE, Java, and Fusion Middleware. Includes migration pressure analysis and TPS transition playbook for the complete Oracle estate.
Download Free Guide →OBIEE TPS Cost Model vs OAC Subscription
| Org Profile | OBIEE User Count | Current Oracle Annual Support (22%) | OAC Annual Subscription (est.) | TPS Annual Cost (est.) | TPS Saving vs Oracle Support |
|---|---|---|---|---|---|
| Mid-size ERP deployment | 100 users | £48K | £80K–£120K | £17K–£24K | £24K–£31K (50–64%) |
| Large enterprise analytics | 500 users | £165K | £280K–£420K | £58K–£82K | £83K–£107K (50–65%) |
| Very large (global ERP) | 2,000 users | £520K | £900K–£1.35M | £182K–£260K | £260K–£338K (50–65%) |
Strategic Options for OBIEE / OAS in 2026
Option 1: Third-Party Support (Best for OBIEE 11g/12c)
Switch OBIEE support to GoVendorFree. Save 50–65% annually. Maintain full OBIEE/OAS functionality indefinitely. Removes OAC migration deadline. Recommended for large, complex OBIEE environments with significant RPD and BI Publisher investment.
Option 2: Oracle Analytics Cloud Migration
Full migration to OAC SaaS. Higher annual cost but removes on-premises infrastructure maintenance. Only viable for smaller, simpler OBIEE environments without heavy BI Publisher or EBS content area dependency. Expect 18–36 months and £500K–£5M migration investment depending on complexity.
Option 3: Third-Party BI Platform Migration
Migrate from OBIEE to Microsoft Power BI, Tableau, or Qlik. For organisations already moving away from Oracle ERP, this removes the Oracle analytics lock-in entirely. High migration effort but long-term avoidance of Oracle commercial leverage. Best combined with ERP modernisation rather than a standalone BI migration.
Option 4: Negotiate Oracle Renewal with TPS Leverage
Use TPS quotes as negotiation leverage to reduce Oracle OBIEE renewal costs 15–25%. Useful short-term tactic. Oracle will recover fees in future years through escalation clauses. Not a sustainable long-term strategy but can extend the evaluation window at lower cost.
OBIEE Within the Broader Oracle Support Strategy
Most organisations running OBIEE on-premises also run other Oracle products — Oracle EBS, Oracle Database, Oracle Fusion Middleware, Java. GoVendorFree can provide third-party support for the entire Oracle stack, not just OBIEE. This means a single support provider, simplified contract management, and further cost reduction as each Oracle product's support moves to the TPS model:
- Oracle Database (OBIEE data sources) → Oracle Database TPS
- Oracle EBS (primary OBIEE data source for most organisations) → Oracle EBS TPS
- Oracle WebLogic (OBIEE application server) → Oracle WebLogic TPS
- Oracle Fusion Middleware (OID, OVD, SOA Suite) → Oracle FMW TPS
Organisations with large Oracle estates often find that consolidating all Oracle product support under GoVendorFree — rather than moving products individually — produces the largest cost reduction and simplifies the support operating model significantly.
Conclusion
Oracle OBIEE on-premises is a mature, stable platform that thousands of organisations depend on for their operational reporting and regulatory output. Oracle's end-of-support timeline for OBIEE 11g and 12c is designed to accelerate OAC cloud migration — not because OAC is technically superior for established OBIEE environments, but because Oracle's revenue model requires cloud subscription growth. Third-party support removes this commercial pressure, saves 50–65% on annual Oracle fees, and gives your organisation the time to evaluate migration options on a commercially rational basis rather than an Oracle-imposed deadline.