Oracle introduces an AI database query agent grounded in business rules
Deep NL2SQL arrives in Private Agent Factory 26.10 with curated feedback and tests for knowledge changes. Experts still have to supply the definitions and validated examples.
Loading page…
Deep NL2SQL arrives in Private Agent Factory 26.10 with curated feedback and tests for knowledge changes. Experts still have to supply the definitions and validated examples.
Listen to this story
Oracle’s October 26, 2026 release adds Deep NL2SQL to Private Agent Factory 26.10, aiming to make database answers reflect business definitions—not just valid table relationships. Teams can supply metric rules and examples, let the agent ask users to resolve ambiguity, and inspect its generated SQL. The approach shifts accuracy work toward maintaining business knowledge and tested queries; Oracle’s claim that accuracy can approach 100% is conditional on that upfront preparation and is not independently verified.
Experts review user feedback and curate knowledge changes; the system does not automatically add every response to shared knowledge.
Teams can test proposed edits against representative questions and validated “gold” SQL before publishing them.
The release adds a Python SDK, REST interfaces, expanded Agent-to-Agent support, and reusable knowledge ingestion.
Oracle is giving its private-agent platform a way to check what a business question means before turning it into a database query. Announced October 26, 2026, Private Agent Factory 26.10 introduces Deep NL2SQL, an agent designed to combine business definitions, user clarification and tested knowledge changes rather than rely on database structure alone.
SQL is the language used to query database tables. A statement can execute successfully while applying the wrong business definition. Oracle illustrates this with top-selling products: sales could mean units, revenue or profit, and might count only after the return window closes.
Deep NL2SQL addresses that gap through a Business Knowledge Graph, an organized collection of database relationships and business context. Application experts use a Knowledge Workbench to group tables, metric definitions, rules, documents and example questions into topics. Oracle says search selects relevant topics instead of presenting the model with the entire enterprise database structure.
If that context leaves the question ambiguous, the agent can ask the user to clarify. It plans, generates and executes SQL, then reviews its answer. Users can inspect the generated SQL rather than receive only a final answer.
The agent logs conversation feedback, including votes on results. Experts review feedback and curate useful knowledge rather than automatically adding every user response to the shared knowledge base.
Changes also have a staging step. Teams register representative questions and validated SQL as a “gold” test set. Oracle’s Deep NL2SQL technical explanation describes how proposed knowledge edits remain unpublished while an evaluation compares generated answers with expected results, checking for disruption of previously validated behavior.
The same release adds a Python software development kit and standardized REST interfaces for connecting agents to applications. Expanded Agent-to-Agent support handles structured content and tasks that need not finish immediately. An Ingestion Service makes prepared knowledge reusable across research and custom workflows.
Native observability lets authorized users inspect execution traces, latency, token usage and errors. Teams can distinguish time spent in model calls, tools and other workflow steps when investigating slow agents or unexpected results.
Loading discussion...
Join the conversation
Explain when faster learning would outweigh the risk of spreading a mistake.
Be the first to share a perspective or an experience.
Reader comments
Newest comments first. Replies stay oldest first.