Oracle adds business definitions and simulations to its AI lakehouse
The updates connect agents to distributed company data, shared metrics and scenario planning. Oracle has not specified when the new capabilities will become available.
Loading page…
The updates connect agents to distributed company data, shared metrics and scenario planning. Oracle has not specified when the new capabilities will become available.
Listen to this story
Oracle’s October 26 update adds a shared semantic layer and Essbase-based simulations to Autonomous AI Lakehouse, aiming to let agents use consistent business definitions and model decisions across connected data. The platform can query data in place, and Oracle says its catalog connects to sources including Snowflake and Databricks; no release date was provided. For teams evaluating it, the practical test will be whether shared definitions and access controls are accurate enough for reliable agent workflows.
The Business Semantic Layer supports annotations, AI-enriched table and column descriptions, reusable Analytic Views, and compatible semantic-model imports.
Expanded Iceberg support lets users and agents create, update, and delete tables through Oracle SQL, with table-level access controls.
Oracle reports a threefold Data Lake Accelerator improvement on a 100 TB TPC-DS benchmark and a maximum cluster-size increase from 32 to 100 nodes.
Oracle wants AI agents to understand company data, not just retrieve it. On October 26, it announced Autonomous AI Lakehouse updates combining shared business definitions, broader data operations and what-if simulations. The promise is business-aware decision support across connected systems; Oracle has not specified a release date for the new capabilities.
The company’s approach is to query data where it already lives, rather than require copies in a separate AI environment. Oracle says the platform connects to Oracle and non-Oracle sources, including Snowflake and Databricks. Its AI Data Catalog can connect to AWS Glue, Databricks Unity Catalog and Snowflake Horizon Catalog, bringing discovery, business context and governance together across those sources.
The Business Semantic Layer supplies common definitions for users, applications and agents. Customers can annotate data, import existing Oracle Database SQL annotations and generate AI-enriched descriptions of tables and columns. Oracle says that shared context helps tools interpret data consistently across connected systems, rather than leaving each agent or analytics tool to work from disconnected descriptions.
For more complex calculations, AI-suggested Oracle Analytic Views package metrics, hierarchies and business calculations into reusable models. They also contain the logic for joining and aggregating data, reducing the query logic users must write. Oracle says support for Apache Ossie lets customers import compatible semantic models instead of recreating existing definitions.
The catalog also narrows what an agent needs to inspect. Oracle describes a search process that moves from catalogs and schemas down to relevant tables and columns, using business meaning and relationships. The intended benefit is more focused context, with less metadata for an agent to process.
In Oracle-published analyst commentary, theCUBE co-founder and chief analyst Dave Vellante said the combination could ground agent workflows in relevant business metrics and relationships. He also identified a prerequisite:
Realizing that value requires accurate business definitions and clear controls over execution.
Dave Vellante, co-founder and chief analyst, theCUBE, in commentary published by Oracle
Expanded Apache Iceberg support goes beyond querying and analysis. Oracle says users and agents can create, populate, update and delete Iceberg tables through Oracle SQL, its database query language. Support for Iceberg V2 and V3 broadens compatibility, while customers can retain their supported catalogs, object storage and compatible processing engines.
Access controls sit in the AI Data Catalog. Oracle describes role-based permissions covering distributed Oracle databases, selected non-Oracle sources and Iceberg tables. Customers can authorize access to an individual Iceberg table, for example, rather than grant access to an entire object-storage bucket.
Data Studio brings this work into an AI-assisted workspace accessible through an Oracle Cloud Infrastructure account. Oracle describes three practical routes through it:
The new business simulation engine uses Oracle Essbase for planning, forecasting and what-if analysis. Users can model changes in revenue, demand, pricing, capacity, cost or risk, with calculations across business hierarchies. Results can be written back to Oracle AI Database and Iceberg tables. Business users can ask natural-language questions, generate simulation reports or analyze models in Excel through Oracle Smart View.
Oracle also claims faster processing. It reports a threefold Data Lake Accelerator improvement in its TPC-DS database benchmark on a 100 TB dataset, alongside an increase in maximum cluster size from 32 to 100 nodes. Lake Cache stores frequently accessed external data on Exadata flash; in Oracle’s Iceberg TPC-DS test, query time fell from 96 seconds to 17 seconds.
Story updates
Oracle says companies can now run Essbase as a fully managed service on Autonomous AI Lakehouse across Oracle Cloud Infrastructure, AWS, Microsoft Azure and Google Cloud. Detailed on October 27, the offering combines AI-assisted model building and conversational analysis with the calculations and Excel planning workflows that existing Essbase users already maintain.
Oracle says companies can now run Essbase as a fully managed service on Autonomous AI Lakehouse across Oracle Cloud Infrastructure, AWS, Microsoft Azure and Google Cloud. Detailed on October 27, the offering combines AI-assisted model building and conversational analysis with the calculations and Excel planning workflows that existing Essbase users already maintain.
The availability detail follows Oracle’s October 26 announcement of a Business Simulation Engine, built by integrating Essbase natively into the lakehouse. Oracle describes that engine as supporting forecasts and what-if analysis, including advanced calculations, allocations and rollups through business hierarchies. The October 27 post explains how customers can build and operate those Essbase applications within the managed service.
AI Cube Builder starts with a user’s intent and relational data, then proposes dimensions, hierarchies and measures for an Essbase cube. Those elements organize the analytical model—for example, sales viewed by product, market and time. Users can review and refine the proposal before building the cube; Oracle says the interface does not require prior knowledge of Essbase interfaces.
Once a model is ready, compatible AI assistants can use Essbase tools to query it and explain results using its defined measures and calculations. Oracle’s example asks which products contributed most to a region’s revenue variance in the previous quarter. Compatible tools can also present results as visualizations or interactive dashboards, while Essbase supplies the underlying model and calculation logic.
Essbase data and metadata are managed in the database. Oracle says customers no longer need to separately operate the Essbase infrastructure, filesystem storage and underlying relational storage layer. Autonomous Database Serverless supplies availability services, automated backup and recovery, security controls, encryption and database administration managed by Oracle.
Oracle also points to workload management, parallel database processing, automated optimization and elastic compute for applications facing uneven demand. Its examples include financial close, budgeting and forecasting cycles.
AI connections run through the Essbase MCP Server. Model Context Protocol, or MCP, provides a standard connection for compatible AI clients to work with applications, metadata, calculations and data. Oracle describes two controls on that access:
MCP access profiles control which tools are available over authenticated connections.
Essbase permissions govern which operations each user can perform.
The service supports more than reading results. Authorized users can write revised planning values back to the Essbase model through Smart View for Microsoft Excel. In Oracle’s example, a planning team revises a monthly forecast, saves its changes and runs the application’s calculations to see how the revised plan affects results.
Teams can retain MDX, the query language used with Essbase, alongside their existing calculation capabilities and Smart View workflows. For database and lakehouse users, Essbase adds a shared model for comparing actuals with budgets, calculating year-to-date results and exploring forecasts across products, markets and time periods.
Models can draw on Oracle database data and external data, including Apache Iceberg tables. Oracle specifies that external data reaches Essbase through supported integration and loading workflows. For existing customers getting started, it recommends validating a representative application before connecting a compatible AI assistant to explore the results.
Oracle wants AI agents to query company data where it already lives, under shared access rules. On October 26, 2026, it introduced Oracle AI Data Catalog, built into Autonomous AI Lakehouse. The promise is a common gateway across Oracle and non-Oracle systems; the formal announcement places the described catalog capabilities within the next 12 months.
Oracle wants AI agents to query company data where it already lives, under shared access rules. On October 26, 2026, it introduced Oracle AI Data Catalog, built into Autonomous AI Lakehouse. The promise is a common gateway across Oracle and non-Oracle systems; the formal announcement places the described catalog capabilities within the next 12 months.
Oracle’s technical introduction describes a catalog of catalogs: one place to discover and access assets across existing systems. Proposed connections include Oracle databases, PostgreSQL and MySQL, and external catalogs such as Microsoft Purview, AWS Glue and Unity Catalog. It also includes a managed Iceberg catalog for tables in object storage.
The core mechanism is federated querying: the Oracle database engine queries connected sources rather than requiring their contents to be copied into a new store. Oracle says users and agents can access live data without ETL—the process of extracting, transforming and loading data elsewhere.
Loading discussion...
Oracle illustrates this with a hypothetical retailer. Order lines sit in an on-premises Oracle database, customer details in a managed cloud database, and product details in Iceberg tables registered through Unity Catalog. An analyst’s query combines all three sources to return order IDs, customer names and product names.
The catalog also carries descriptions and business definitions intended to help agents find and interpret relevant data. Oracle describes three ways to supply that context:
Written annotations: Users can add explanations throughout the catalog hierarchy, down to individual columns.
AI-generated descriptions: Oracle describes automatic descriptions for catalogs, schemas, tables, views and columns.
Analytic views: Reusable definitions capture business metrics, dimensions and hierarchies.
In the retailer example, an analyst can ask Data Studio’s built-in assistant for the combined information in plain language. Oracle says the assistant can generate the three-source SQL query for review and execution.
Administrators can assign catalog privileges to roles, then grant those roles to users or groups. Rules can cover an entire source or smaller collections of tables. Those privileges govern requests through catalog-connected clients and query engines; permissions on the underlying source still apply.
Oracle also describes lineage reports showing where data came from and how it changed. The catalog can collect that history from Oracle systems or configured third-party systems emitting OpenLineage events, including Spark, Trino, dbt and Apache Airflow. Users can inspect the history through Data Studio or REST APIs.
Join the conversation
Explain what else you would need before acting on its recommendations.
Be the first to share a perspective or an experience.
Reader comments
Newest comments first. Replies stay oldest first.