Oracle Text — the full-text search and document management capability built into Oracle Database — is included at no additional cost in Enterprise Edition and Standard Edition 2. Oracle OLAP — the multidimensional analytical engine that lets Oracle Database serve as an OLAP cube server — is a separately licensed option at $17,500 per processor. The compliance trap is that Oracle OLAP was a default installation component in Oracle Database 10g through 12c standard database installations. Organisations that installed Oracle Database using the default options found OLAP schemas and packages installed and registered in DBA_REGISTRY without ever knowingly selecting the OLAP option. Oracle LMS scripts detect DBA_REGISTRY entries as evidence of option usage — and that is where the audit claims originate. Former Oracle insiders explain both options in full, the DBA_REGISTRY accidental-registration trap, and how to push back against inflated OLAP claims.
Oracle Text (formerly Oracle interMedia Text and Oracle ConText) provides full-text indexing, searching, and document retrieval capabilities within Oracle Database. It enables applications to index and search text stored in VARCHAR2, CLOB, BLOB, BFILE, and XMLTYPE columns using Oracle SQL — without requiring a separate search engine or middleware layer.
Oracle Text is included in Oracle Database Enterprise Edition and Standard Edition 2 at no additional licence cost. It has been a standard, included Oracle Database capability since Oracle 8i. The CTXSYS schema and Oracle Text packages (CTX_DDL, CTX_QUERY, CTX_DOC, etc.) are installed by default in standard Oracle Database installations.
Oracle Text is free — but Oracle sometimes sells Oracle Text as part of a product bundle. If your Oracle contract includes a line item for "Oracle Text" as a separately priced component, challenge it. Oracle Text as a standalone Oracle Database capability is included in EE and SE2. The only scenario where Oracle Text might appear as a separately purchased component is if you are using Oracle Secure Enterprise Search (a separate search platform product, now generally end-of-life) or a legacy contract structure.
Oracle OLAP is a separately licensed Oracle Database EE option at $17,500 per processor that enables Oracle Database to function as an OLAP (Online Analytical Processing) cube server. It extends Oracle Database with multidimensional data modelling, OLAP DML (a proprietary analytical programming language), and the Oracle OLAP API for programmatic cube access.
Oracle OLAP creates multidimensional cubes stored as Analytic Workspaces within Oracle Database, allowing applications to retrieve pre-aggregated multidimensional data without scanning relational tables. This was Oracle's strategic response to standalone OLAP products (Hyperion Essbase, Microsoft Analysis Services, IBM Cognos TM1) that competed with Oracle's relational analytics capabilities.
Oracle OLAP has seen declining enterprise adoption since approximately 2010, as Essbase-based analytics, SAP BW, and cloud-native analytics platforms displaced in-database OLAP cube servers. Many Oracle Database estates have Oracle OLAP installed from legacy decisions that were never revisited — and the installations remain, creating LMS audit targets in databases where nobody is actively using OLAP capabilities.
The Oracle OLAP accidental installation problem has a specific root cause: Oracle Database 10g and 11g standard installation procedures included Oracle OLAP as a default installation component. When DBAs installed Oracle Database using the "Typical" installation type (the most common choice for non-DBA-specialist teams), Oracle OLAP was installed alongside the database without requiring explicit selection.
The OLAP installation created the OLAPSYS schema, populated DBA_REGISTRY with Oracle OLAP component entries, and installed all OLAP packages and procedures. In Oracle Database installations created through 10g and much of 11g, finding Oracle OLAP in DBA_REGISTRY is the norm, not the exception — even for organisations that have never knowingly used an OLAP feature.
Oracle's audit position: Oracle LMS's interpretation is that if Oracle OLAP appears in DBA_REGISTRY, it has been "installed and available for use," and therefore a licence is required. Oracle's licence policies for most options state that if an option is installed (not just used), the licence requirement applies. This is Oracle's most aggressive audit claim position, and it is challenged regularly by independent licence advisors — with significant success where actual usage can be negated.
The scale of this problem is significant. Enterprises with 50-100 Oracle Database instances — common in large financial services, manufacturing, or government organisations — may have Oracle OLAP registered in every database that was installed from standard 10g or 11g media. At $17,500 per processor per database, the aggregate back-licence claim can reach seven figures before Oracle has finished counting processors. This is exactly the scenario where our Oracle audit defence service focuses on technical counter-arguments rather than commercial negotiation.
Before you accept Oracle's audit claim, let us review your actual OLAP usage evidence. Our Oracle compliance review documents the difference between an installed schema and active OLAP usage — and builds the technical record you need to challenge an inflated OLAP back-licence claim.
Oracle LMS detects Oracle OLAP through a combination of DBA_REGISTRY queries and OLAP-specific usage evidence queries. Understanding both layers matters for your defence strategy — because the DBA_REGISTRY query establishes that OLAP is installed, but the usage evidence queries determine whether Oracle can demonstrate that OLAP was actively used.
The critical distinction is between DBA_REGISTRY evidence (installation) and Analytic Workspace evidence (active use). Most organisations with accidental OLAP installations will have DBA_REGISTRY entries but empty or absent Analytic Workspaces. Challenging Oracle's OLAP claim requires demonstrating that although OLAP was installed, no Analytic Workspaces were created, no OLAP DML was executed, and no application accessed OLAP functionality.
DBA_REGISTRY is a data dictionary view that records which Oracle Database components are installed in a database. It was designed as an installation inventory tool, not as a licence compliance mechanism. Oracle LMS treats DBA_REGISTRY as evidence of option installation and — per Oracle's licence policies for many options — installation triggers the licence requirement.
The counter-argument that independent Oracle licence advisors make in OLAP audit disputes has two prongs. First, DBA_REGISTRY records installation by Oracle's own installation scripts, not by a deliberate customer action to deploy the option — the customer never "used" Oracle OLAP, they used Oracle's installation media that happened to install OLAP without disclosure. Second, even if the installation is treated as a licence trigger, the licence obligation applies from the point of installation, and for many affected databases the OLAP-inclusive installation occurred many database versions ago; Oracle's audit reach-back has contractual and reasonable limits.
Important: Do not manually delete OLAPSYS schema objects or attempt to remove OLAP from DBA_REGISTRY using unofficial methods. This can corrupt the Oracle data dictionary and create database integrity issues. If you want to formally de-install Oracle OLAP, use Oracle's documented deinstall procedures (catnoaps.sql and related scripts) in a test environment first, with full database backup. Our compliance review service includes guidance on legitimate OLAP removal procedures.
Oracle provides documented deinstallation scripts for Oracle OLAP that remove the OLAP components from DBA_REGISTRY, drop the OLAPSYS schema, and remove OLAP-related packages. This process must be performed carefully — it requires DBA privileges, should be done during a maintenance window, and requires a full database backup beforehand.
Important nuance: removing Oracle OLAP from DBA_REGISTRY prospectively demonstrates that the option is not installed going forward. It does not retroactively eliminate any licence obligation for periods when Oracle claims OLAP was installed and potentially usable. In an active audit where Oracle is claiming back-licence fees for a historical period, removing OLAP now does not resolve the historical claim — but it does prevent the claim from growing larger. Pair the removal with a documented evidence record that no Analytic Workspaces were created or used during the claimed period.
We have successfully challenged Oracle OLAP back-licence claims by demonstrating that the DBA_REGISTRY entry resulted from Oracle's default installation behaviour, not a deliberate customer election to use the OLAP option. Our audit defence team understands Oracle's playbook — because we helped write it.
Oracle OLAP audit claims are more defensible than Oracle LMS teams typically suggest. The argument that DBA_REGISTRY installation = licence obligation is Oracle's position, not an unchallenged fact. Independent Oracle licence advisors — including former Oracle LMS personnel who now work buyer-side — have successfully reduced or eliminated OLAP back-licence claims in a significant proportion of cases where the technical record shows installation without active use.
In a representative engagement, a financial services firm with 67 Oracle Database instances received an OLAP back-licence claim of $4.2M — based on OLAP appearing in DBA_REGISTRY across their entire estate, with Oracle claiming a 3-year retroactive licence requirement at full list price. Our review found zero Analytic Workspaces in any database, no OLAP DML execution history, and clear evidence that OLAP was installed by Oracle's default 10g media. After presenting this technical record to Oracle LMS, the final settlement was $0 for OLAP, converted into improved pricing on an upcoming EA renewal. See our case studies for additional examples.
The complete playbook for defending against Oracle LMS audit claims — including accidental options, DBA_REGISTRY disputes, and the commercial settlement strategies that eliminate or minimise back-licence claims.
Download Free White Paper →Audit alerts, accidental options updates, and negotiation tactics — direct to your inbox. Read by Oracle stakeholders at 500+ enterprises.
Written by the Oracle Licensing Experts team — former Oracle executives, LMS auditors, and contract managers who now work exclusively for enterprise buyers. Not affiliated with Oracle Corporation.