Oracle Adds Bedrock to Select AI While Keeping More AI Work in Its Database

The new capabilities place embedding, retrieval and workflow functions closer to enterprise data, but generated SQL and agent actions still require careful model, access and network controls.

By 2 min read
Oracle Adds Bedrock to Select AI While Keeping More AI Work in Its Database
Oracle Adds Bedrock to Select AI While Keeping More AI Work in Its Database

Listen to this story

The audio brief

About 1:38
0:001:38
Read transcript
Oracle is putting Amazon Bedrock inside Select AI for Autonomous AI Database on Dedicated Infrastructure, while keeping more of the supporting work close to enterprise data. The package adds nine other capabilities, including in-database embeddings, correction memory, synthetic-data generation, and agent tools. Select AI takes natural-language requests through SQL or PL/SQL. For a SQL task, it builds a prompt from schema metadata and sends that prompt to a customer-selected large language model, or LLM, to generate, run, or explain a query. With Bedrock, customers must choose a model, inference profile, or ARN, and configure region-specific network routing. A database permission to make outbound calls is not enough. The boundary is also important: SQL generation receives schema metadata, not table or view contents. Retrieval works differently. An ONNX embedding model can chunk and vectorize documents inside the database, but the retrieved context still goes to an LLM for the final answer. Those embedding jobs consume ECPUs and can compete with database workloads. Select AI Feedback stores prompts and corrections in a vector index, then retrieves similar examples for future requests. Oracle describes that as retrieval-based prompting, not fine-tuning. Agents can call NL2SQL, retrieval, web search, notifications, and custom PL/SQL, including ReAct-style actions. Generated SQL still runs in the customer’s database, so the key constraint is careful control of models, access, and network paths.

Story brief

3 key points

Oracle’s latest Select AI package turns Autonomous AI Database into a broader in-database AI control layer, but it does not eliminate external model calls. Bedrock can generate SQL from schema metadata, while ONNX embeddings, vectorization, feedback memory, synthetic-data generation, and agent tooling run close to Oracle data. Retrieved context and final prompts still reach an LLM, and embedding jobs consume ECPUs....

  1. 01

    Amazon Bedrock integration requires a selected model, inference profile or ARN, plus region-specific network routing; permission alone is insufficient.

  2. 02

    Schema metadata crosses the boundary for SQL generation; table and view contents do not, but retrieved context is sent to an LLM.

  3. 03

    Select AI Feedback retrieves prior corrections from a vector index; it is retrieval-based prompting, not fine-tuning.

Oracle has added Amazon Bedrock support and nine other Select AI capabilities for Autonomous AI Database on Dedicated Infrastructure. The package brings local embedding, correction memory, synthetic data and agent tools under a shared configuration model, designed to keep more AI processing near the database.

The configuration layer

Select AI accepts natural-language prompts through SQL and PL/SQL. For SQL tasks, it builds an augmented prompt from database metadata and sends it to a customer-selected large language model, or LLM, to generate, run or explain a query. An AI profile holds the provider, model, credentials and database objects used by these functions.

The AWS option lets Bedrock models generate SQL against Oracle data. Users must specify a Bedrock model, inference profile or ARN, and configure network access for the chosen region. On Dedicated Infrastructure, a database permission to make an outbound call does not itself create the route needed to reach Bedrock.

Retrieval and correction inside the database

For retrieval-augmented generation, Select AI can run an imported ONNX embedding model through the database’s ONNX Runtime. Document chunking and vectorization stay inside the database perimeter, although retrieved context still goes to an LLM for the final answer. Oracle says embedding inference uses ECPUs, so a large initial vectorization job can compete with database workloads.

Select AI Feedback keeps prompts and corrections in a vector index, then retrieves similar examples as hints for future natural-language-to-SQL requests. That is retrieval-based prompt engineering, not model fine-tuning. Profiles can also supply table and column comments, annotations and foreign-key constraints as model context.

From questions to actions

  • Schema-aware synthetic-data generation can use data types, constraints and referential integrity, with parallel processing for larger multi-table jobs.
  • Conversations can be session-based or persistent, resumable and shareable across SQL, chat and narration operations.
  • Property-graph metadata can guide the translation of natural-language questions into GRAPH_TABLE queries.

The agent capability extends the system beyond answers. It uses the ReAct reasoning-and-acting pattern with short- and long-term memory, and can call NL2SQL, retrieval, web-search and notification tools, along with custom PL/SQL procedures. Oracle warns that LLM-generated SQL can be wrong or create security risks; generated queries run in the customer’s database.

Sources

  1. docs.oracle.comdocs.oracle.com
  2. blogs.oracle.comMove the AI to the Data: What