New Feature Announcements

Announcements for the noteworthy changes made to Autonomous AI Database on Dedicated Exadata Infrastructure.

February 2026

Feature Description
Provide Feedback to Improve LLMs with Select AI

On Autonomous Database on Dedicated Exadata Infrastructure, Select AI enables you to give feedback on generated NL2SQL results to improve query generation accuracy. Feedback can be given on the SQL command line as well as through PL/SQL procedures.

See Provide Feedback to Improve LLMs, Example: Select AI Feedback, and FEEDBACK Procedure to explore the feature.

Create and Customize Conversations with Select AI

On Autonomous AI Database on Dedicated Exadata Infrastructure, Select AI supports customizable conversations enabling you to use Select AI with different topics without mixing context, improving both flexibility and efficiency. You can create, set, delete, and update conversations through the DBMS_CLOUD_AI conversation procedures and functions.

See Use and Customize Conversations and Example: Enable Conversations in Select AI, and Summary of DBMS_CLOUD_AI Subprograms for more information.

Generate Property Graph Data with Select AI

On Autonomous Database on Dedicated Exadata Infrastructure, you can use Select AI to graph structures and query SQL property graphs using natural language, reducing the time and effort in building graph queries using the GRAPH_TABLE operator.

See Query Graph Data with Property Graphs, Example: Select AI for Property Graphs, and Example: Sample Prompts for Property Graphs for more information.

Select AI Agent (autonomous agent framework)

Select AI Agent (autonomous agent framework) introduces a framework for building agentic workflows enabling developers to create agents, tools, tasks, and teams that reason, act, and collaborate using generative AI within the database.

Agents can plan actions, use built-in or custom tools (such as SQL, RAG, Websearch, or Notification), and maintain context across multi-turn conversations. This feature enables developers to create agentic workflows using SQL and PL/SQL that support AI-driven automation, data interaction, and human-in-the-loop control.

See Build Autonomous Agents with Select AI Agent, DBMS_CLOUD_AI_AGENT Package, DBMS_CLOUD_AI_AGENT Views, and Examples of Using Select AI Agent to explore this feature.

January 2026

Feature Description
Configure Autonomous Data Guard between ACD in OCI and ACD in AWS region.

You can create and manage Autonomous Data Guard between an ACD in OCI and an ACD in AWS. This feature provides full Autonomous Data Guard functionality for disaster recovery and high availability across clouds.

See Manage Autonomous Data Guard Configuration for more details.

Use AWS Key Management Service (AWS KMS) to manage Master Encryption Keys in Autonomous AI Database on Oracle Database@AWS.

In Autonomous AI Database on Oracle Database@AWS, you can use AWS Key Management Service (AWS KMS) to manage Master Encryption Keys in AWS.

See Autonomous AI Database on Dedicated Exadata Infrastructure in AWS Region for more details.

Ability to choose Autonomous Recovery Service as the backup destination.

On Oracle Public Cloud deployments, you can choose Autonomous Recovery Service as the backup destination while creating the ACD. This is the recommended option for the backup destination.

See Create an Autonomous Container Database and Edit Autonomous Container Database Backup Settings for more details.

Ability to use a third network interface card (NIC) for specific database operations like Autonomous Data Guard and cloning the Autonomous AI Database.

On Exadata Cloud@Customer deployments, if you have enabled a Disaster Recovery Network, you can use the third NIC that you have configured for specific database operations like Autonomous Data Guard (AuDG) and cloning the Autonomous AI Database. The Data guard and cloning operations are separated from regular network traffic, reducing the risk of network congestion and improving performance.

To use the third NIC with your Autonomous Virtual Machine Cluster (AVMC), you must first submit a Service Request (SR) to Oracle Support. This Service Request must be made before the AVMC is created. Once enabled, all the Data Guard and cloning operations from database instance uses only the 3rd NIC.

See Network Requirements for Oracle Exadata Database Service on Cloud@Customer for more details.