New Feature Announcements

June 2025

Feature	Description
MongoDB API support from the Oracle Cloud Infrastructure (OCI) console.	You can enable the MongoDB API on your Autonomous Database from the OCI console. The MongoDB API enables MongoDB-compatible clients and drivers to connect directly to your Autonomous Database. See Use MongoDB API with Oracle Autonomous Database for instructions on enabling the MongoDB API and connecting MongoDB applications to an Autonomous Database.
Documentation Update: Autonomous Database on Exadata Cloud@Customer Events.	Autonomous Database on Dedicated Exadata Infrastructure documentation is updated with the complete list of events emitted by the following Exadata Cloud@Customer resources such as Exadata Infrastructure, Autonomous Exadata VM Cluster, Autonomous Container Database, Autonomous Database. You can refer to Events for Autonomous Database on Dedicated Exadata Infrastructure to view the updated events.
Oracle Application Express (APEX) 24.2 is now available for new Autonomous Container Databases (ACD).	You can use Oracle Application Express 24.2 to develop applications for an Autonomous Database. Only newly created ACDs have access to Oracle Application Express 24.2. All existing ACDs will continue to run with the APEX version they were provisioned with. To use the latest Oracle Application Express features for enhancing the existing applications, you can schedule an upgrade to your APEX instance through Service Request (SR) in My Oracle Support. You must supply the OCIDs of the tenancy and Autonomous Database for which you request the APEX upgrade in the SR. See Build an Oracle Application Express (APEX) Application for more details.
Documentation Update: New events for Autonomous Container Database.	With Autonomous Database deployments on Exadata Cloud@Customer, you can now get notified when: Your Network File Storage server is out of space. Incorrect permissions are set on your Network File Storage server. Your Zero Data Loss Recovery Appliance server is out of space. Your Network File Storage backups consume at least 80% of space in the backup destination. Your Autonomous Container Database's backup destination is back to a healthy state. Refer to Events for Autonomous Database on Dedicated Exadata Infrastructure for a complete list of events emitted by Autonomous Database resources.
Ability to create a cross region backup copy of an Autonomous Container Database	Oracle Public Cloud deployments of Autonomous Database on Dedicated Exadata Infrastructure allow you to select a secondary region for a copy of your Autonomous Container Database (ACD) backups. You can also view and clone remote backups from the OCI console. In case of a region failure, you can clone the ACD's remote backup to restore the data. The backup of an ACD can only be cloned to an Autonomous Exadata VM Cluster (AVMC) different from its source AVMC. For instructions on enabling cross region backup copies, see Create an Autonomous Container Database and Edit Autonomous Container Database Backup Settings.
Ability to clone an Autonomous Container Database	On Oracle Public Cloud deployments, Autonomous Database on Dedicated Exadata Infrastructure lets you clone an Autonomous Container Database (ACD) and all its Autonomous Databases from the ACD Details page on the Oracle Cloud Infrastructure (OCI) console. See About Cloning Autonomous Container Database on Dedicated Exadata Infrastructure and Clone an Autonomous Container Database for further information and guidance.

May 2025

Feature	Description
OCPU billing metric retirement for new Autonomous Exadata VM Clusters (AVMCs)	Starting May 28th, 2025, Autonomous Database on Dedicated Exadata Infrastructure does not allow you to create new AVMCs using the OCPU billing metric. All the new AVMCs can only be provisioned with ECPUs. Existing OCPU AVMCs and Autonomous Databases will continue to operate as usual. You can have your OCPU AVMCs and respective Autonomous Databases updated to ECPU via service requests. See Doc ID 2998755.1 for more information.
Transport Layer Security 1.3 (TLS 1.3) certificate-based authentication	Autonomous Database on Dedicated Exadata Infrastructure with Oracle Database version 23ai or later can use either TLS 1.2 or TLS 1.3 (Transport Layer Security) certificate-based authentication for database connections. See Encryption of Data in Transit
Use custom kerberos service name for Kerberos authentication	Autonomous Database on Dedicated Exadata Infrastructure supports custom kerberos service name for Kerberos authentication. When you use a custom name you must specify the `kerberos_service_name` parameter with `DBMS_CLOUD_ADMIN.ENABLE_EXTERNAL_AUTHENTICATION`. Specifying this parameter is not required when you use the GUID for the service name. See Components of the Kerberos Authentication System for more details.
New database metric for Session Utilization	Autonomous Database on Dedicated Exadata Infrastructure provides a new metric called `SessionUtilization` to show the maximum session utilization as a percentage value, aggregated across all consumer groups. See Available Metrics: oci_autonomous_database for more details.

April 2025

Feature	Description
Manage Customer Contacts for Autonomous Database resources	When customer contacts are set, Oracle sends announcements, operational notifications, and unplanned maintenance notifications to the specified email addresses. With Autonomous Database on Dedicated Exadata Infrastructure, you can add, view, and update customer contacts at the following resource levels: Exadata Infrastructure Autonomous Container Database (ACD) Autonomous Database See the following pages for more instructions: Manage Customer contacts for an Exadata Infrastructure Create an Autonomous Container Database Manage Customer contacts for an Autonomous Container Database Clone an Autonomous Database Instance Clone an Autonomous Database from Backup

Feature

Description

Manage Customer Contacts for Autonomous Database resources

When customer contacts are set, Oracle sends announcements, operational notifications, and unplanned maintenance notifications to the specified email addresses.

With Autonomous Database on Dedicated Exadata Infrastructure, you can add, view, and update customer contacts at the following resource levels:

Exadata Infrastructure
Autonomous Container Database (ACD)
Autonomous Database

See the following pages for more instructions:

March 2025

Feature	Description
Provision Autonomous Exadata VM Clusters with IPv4/IPv6 dual-stack networking	With Autonomous Database on Dedicated Exadata Infrastructure, you can provision Autonomous Exadata VM Clusters with IPv4/IPv6 dual-stack networking, enabling both IPv4 and IPv6 addresses. This option is enabled while you create a VCN, and while creating a subnet. You can use the corresponding subnet (which has both IP4 and IP6 addresses) while provisioning an Autonomous Exadata VM Cluster.
Integration with OCI Logging Service	With Autonomous Database on Dedicated Exadata Infrastructure, you can enable or disable capturing of Oracle Cloud Infrastructure service logs using the OCI Logging Service. See Observe Resource Logs with OCI Logging Service for details.
Select AI with Google, Anthropic, and Hugging Face	Autonomous Database on Dedicated Exadata Infrastructure can interact with AI service providers. In addition to the previously supported providers, Select AI supports Google Gemini, Anthropic, and Hugging Face. This feature supports having LLMs work with Oracle database by generating SQL from natural language prompts, enabling you to talk to your database. See Use Select AI to Generate SQL from Natural Language Prompts for information on using Select AI with Autonomous Database.
Dual standby database support in an Autonomous Data Guard configuration	Autonomous Database on Dedicated Exadata Infrastructure lets you enable Autonomous Data Guard from the Details page of an Autonomous Container Database (ACD) and create up to two standby ACDs. The second standby ACD must be in the same tenancy as the primary ACD. See Add a Second Standby Autonomous Container Database for instructions. With this release, the previous Autonomous Data Guard Associations model and associated APIs will be deprecated and replaced with the new Autonomous Data Guard Groups model and APIs. All new ACDs provisioned after March 2025 from the Oracle Cloud Infrastructure (OCI) console will automatically use the new Autonomous Data Guard Groups model. See Knowledge Base for more information. To transition existing ACDs, customers can migrate to the new model by clicking the Upgrade to Autonomous Data Guard Groups from the ACD Details page on the OCI Console or using the MigrateAutonomousContainerDatabaseDataguardAssociation API. See Autonomous Data Guard Models to know more details about upgrading to the new model.

February 2025

Feature	Description
NFS space utilization	With Autonomous Database deployments on Exadata Cloud@Customer, if the backup destination type is NFS, then you can view the NFS space utilization from the ACD details page. The current NFS space utilization is displayed as a percentage along with a status icon. See View NFS Space Utilization for more details.
Change the backup destination type of an Autonomous Container database	With Autonomous Database deployments on Exadata Cloud@Customer, you can change the backup destination type for an Autonomous Container Database which has the automatic backup enabled. See Edit Autonomous Container Database Backup Settings for more details.
Restore Database to a specific SCN	On Autonomous Database on Dedicated Exadata Infrastructure, you can restore the database to a specific System Change Number (SCN). See Restore and Recover Autonomous Database on Dedicated Exadata Infrastructure for more details.
Database Clone from the latest backup	On Autonomous Database on Dedicated Exadata Infrastructure, when you clone the database from a backup, you can choose the Backup clone type as Latest backup timestamp. With this backup clone type, you can clone the database from the most recent backup data that is available. See Clone Autonomous database from backup for more details.
Oracle Maintained Pipelines	Autonomous Database on Dedicated Exadata Infrastructure provides built-in pipelines that enable you to export the database audit logs or Oracle APEX workspace activity log to OCI Object Storage in JSON format. These pipelines are preconfigured and can be started by the ADMIN user. See Oracle Maintained Pipelines for more information.

January 2025

Feature Description

Doc update: Vulnerability Assessment and Security Testing Policies

Feature	Description
Doc update: Vulnerability Assessment and Security Testing Policies	We have updated the Autonomous Database on Dedicated Exadata Infrastructure documentation with details about: Vulnerability scans and patching that Autonomous Database frequently performs using commercial vulnerability scanning tools. Security testing policies governing activities such as penetration testing and vulnerability scanning that Oracle customers can perform against their Autonomous Database. See Vulnerability Scans and Patching and Oracle Cloud Security Testing Policy for complete details.
Support for `DELETE_OPERATION` procedure in `DBMS_CLOUD` package.	On Autonomous Database on Dedicated Exadata Infrastructure, you can use `DBMS_CLOUD.DELETE_OPERATION` procedure to clear the data load entries for the specified operation ID logged in the `user_load_operations` or `dba_load_operations` tables in your schema.
X11M systems available for Autonomous Database on Oracle Public Cloud and Autonomous Database on Exadata Cloud@Customer deployments.	When you create Autonomous Database deployments on Oracle Public Cloud or Exadata Cloud@Customer, you can deploy to X11M Exadata Database Machine systems. For details about the capacities and characteristics of the X11M systems supported by the Autonomous Database, see Exadata X11M Systems.

We have updated the Autonomous Database on Dedicated Exadata Infrastructure documentation with details about:

Vulnerability scans and patching that Autonomous Database frequently performs using commercial vulnerability scanning tools.
Security testing policies governing activities such as penetration testing and vulnerability scanning that Oracle customers can perform against their Autonomous Database.

See Vulnerability Scans and Patching and Oracle Cloud Security Testing Policy for complete details.

Support for DELETE_OPERATION procedure in DBMS_CLOUD package. On Autonomous Database on Dedicated Exadata Infrastructure, you can use DBMS_CLOUD.DELETE_OPERATION procedure to clear the data load entries for the specified operation ID logged in the user_load_operations or dba_load_operations tables in your schema.

X11M systems available for Autonomous Database on Oracle Public Cloud and Autonomous Database on Exadata Cloud@Customer deployments.

When you create Autonomous Database deployments on Oracle Public Cloud or Exadata Cloud@Customer, you can deploy to X11M Exadata Database Machine systems.

For details about the capacities and characteristics of the X11M systems supported by the Autonomous Database, see Exadata X11M Systems.