Oracle Analytics Server — the on-premise successor to Oracle Business Intelligence Enterprise Edition (OBIEE) — underpins the enterprise reporting and analytics infrastructure of thousands of large organisations. Banks run Basel IV and IFRS 17 regulatory reports on it. Manufacturers run their operational intelligence dashboards on it. Government departments run their budget and performance reporting on it. Oracle knows this. And Oracle's account teams know that telling a customer their analytics estate must move to Oracle Analytics Cloud (OAC) is one of the most effective leverage points at renewal time — because the migration is genuinely complex and genuinely expensive.
Third-party support for Oracle Analytics Server (OAS 5.x, 6.x) and OBIEE 12c (12.2.1.x) cuts your annual support cost by 50–65%, removes Oracle's migration leverage, and lets your BI team continue optimising an established analytics environment without the disruptive cost and risk of a cloud re-platform. For organisations with sophisticated semantic models, hundreds of custom reports, and deep RPD repository customisation, TPS is the commercially rational choice while you control your own roadmap.
Running Oracle? Find out exactly what you're overpaying. Free cost analysis, no commitment.
500+ enterprise clients · Est. 2016 · 15-min response · No commitment
OBIEE 12.2.1.4 (the last OBIEE release) reached Premier Support end in October 2024. Oracle Analytics Server 5.5 Premier Support ends December 2025. OAS 6.4 extends to December 2027. Organisations running OBIEE 12c or OAS 5.x are either past or approaching Oracle's support boundary — meaning Oracle support engineers will increasingly require costly upgrades before assisting with production issues. See our OBIEE TPS overview for the full version history and migration path analysis.
Oracle Analytics Cloud Migration — The True Cost Oracle Doesn't Advertise
Oracle Analytics Cloud (OAC) is Oracle's SaaS BI platform — a genuine product with real analytical capabilities including augmented analytics, machine learning integration, and seamless Oracle Cloud data source connectivity. For greenfield deployments or organisations building net-new analytics on top of Oracle Cloud ERP and HCM, OAC makes architectural sense. For organisations with mature OAS or OBIEE environments, the migration cost picture is materially different.
A production OBIEE or OAS environment typically contains an RPD (Repository/Semantic Model) with hundreds of subject areas, logical table sources, and calculation rules developed over years of business-specific refinement. Migrating that RPD to OAC's semantic model is not a lift-and-shift — it requires rearchitecting the semantic layer, re-mapping data sources, recreating security filters, and regression-testing every dashboard and report. System integrator estimates for a mid-tier OBIEE migration (200–500 reports, 50–100 users, on-premise Oracle Database sources) range from £400K–£1.5M in professional services. For an enterprise OBIEE environment (1,000+ reports, Oracle EBS or Fusion as source, complex financial hierarchies), migration costs reach £1.5M–£4M before infrastructure and subscription costs. GoVendorFree TPS costs a fraction of that, annually, to maintain your existing environment in production.
OAS and OBIEE Version Matrix — TPS Eligibility
| Product / Version | Release Year | Oracle Premier Support | TPS Available |
|---|---|---|---|
| OBIEE 11g (11.1.1.9) | 2014 | Ended Oct 2018 — Sustaining only | ✓ Yes — ideal TPS candidate |
| OBIEE 12c (12.2.1.4) | 2018 | Premier Support ended Oct 2024 | ✓ Yes — largest OBIEE TPS cohort |
| Oracle Analytics Server 5.5 | 2021 | Premier Support ends Dec 2025 | ✓ Yes — transitioning to TPS |
| Oracle Analytics Server 5.9 | 2022 | Premier Support ends Dec 2026 | ✓ Yes |
| Oracle Analytics Server 6.4 | 2023 | Premier Support to Dec 2027 | ✓ Yes |
| Oracle Analytics Cloud (OAC) | SaaS | Subscription — always current | N/A — SaaS product |
GoVendorFree TPS Coverage for Oracle Analytics Server and OBIEE
GoVendorFree's Oracle TPS covers the full Oracle Analytics stack — the BI Server, Presentation Services, web catalogue, security framework, and data integration layer. Coverage includes:
- Oracle BI Server and RPD: Physical, business model, and presentation layer configuration; logical table source troubleshooting; aggregate navigation; fragmentation and partitioning; XML Gateway and LDAP data sources; Oracle Database, SQL Server, and SAP BW connectivity stability
- Oracle Analytics Presentation Services: Dashboard and report stability; Answers, Interactive Dashboards, and BI Publisher rendering; KPI watchlist and scorecard; mobile analytics (OBIEE Mobile App Designer and Oracle DAM); conditional formatting and guided navigation
- BI Publisher and FTP/Email Delivery: Report template stability (RTF, Excel, PDF); bursting configuration; scheduler job management; delivery channel configuration (FTP, WebDAV, email, printer, content server)
- Security Framework: Weblogic-embedded security for OAS/OBIEE; LDAP/Active Directory integration; Oracle Virtual Private Database row-level security; Application Role and Application Policy security; SSO configuration (SAML 2.0, Oracle Access Manager)
- Data Integration — ODI and Informatica Compatibility: Oracle Data Integrator (ODI 12c) usage advisory in conjunction with OAS; ETL pipeline stability for OAS data warehouse sources; Oracle Essbase integration (for Financial Consolidation use cases)
- Oracle Essbase (Embedded): OAS-embedded Essbase 21c cube stability; calculation scripts; MaxL and MDX query performance; Smart View for Office integration; Financial Reporting Studio (FRS) report generation
- Performance Tuning and Incident Management: Query log analysis; cache management; connection pool optimisation; NQSServer.log-level incident diagnosis; clustering and horizontal scalability advisory for multi-node OAS deployments
Why RPD Complexity Makes TPS the Logical Default
The core argument for keeping OAS or OBIEE on TPS rather than migrating to OAC is the RPD — the semantic model that represents years of business logic investment. An enterprise OBIEE 12c environment might have 15,000–50,000 lines of XML in its RPD, encoding complex many-to-many relationships, multi-currency calculations, period-over-period comparisons, and account hierarchy mapping that every financial analyst in the business relies on. This is not infrastructure. It is institutional knowledge encoded in software.
Oracle Analytics Cloud uses a different semantic model architecture — the OAC Data Model — which is not a direct migration target for OBIEE RPD content. Oracle's own migration tooling (the OAC Semantic Modeler) can translate portions of OBIEE RPD content, but the output requires substantial manual rework. Organisations that have attempted this migration report that 30–60% of their RPD logic requires complete re-creation rather than translation. Every analyst's dashboard that breaks during migration represents both a technical project task and a business disruption that finance, operations, or regulatory teams experience directly. Our Oracle Hyperion guide covers the analogous financial analytics migration trap in the EPM space.
Financial Services Analytics on OAS — The Regulatory Reporting Constraint
Financial services organisations running regulatory reporting workflows on OBIEE or OAS face a specific constraint that amplifies the case for TPS: change validation. The reports that feed Basel IV capital calculations, IFRS 9 expected credit loss models, Solvency II SCR submissions, and FINREP/COREP regulatory returns are subject to model validation requirements. A migration to OAC that changes report output — even by one decimal place in a calculated ratio — triggers a model change validation exercise under the organisation's model risk management framework. That validation is not free: it involves data governance sign-off, risk management review, and often regulatory notification depending on the jurisdiction.
Third-party support on the existing OBIEE or OAS environment avoids triggering this validation chain. The reports produce the same output they have always produced. The business logic remains unchanged. The validation obligation does not arise. See our financial services practice page for a full analysis of TPS in regulated BI environments and our Oracle Support Cost Reduction white paper for the detailed regulatory analytics cost model.