Autonomous AI Database for Developers

Autonomous AI Database for Developers provides you with low cost instances for developers and others to build and test new Autonomous AI Database applications.

Billing for Autonomous AI Database for Developers databases is hourly per instance. See Autonomous AI Database for Developers Billing and Tenancy Service Limit for details.

Autonomous AI Database for Developers are low-cost, fixed shape databases intended for development and testing uses cases, and are not recommended for production use cases. When you need more compute or storage resources or you want to take advantage of additional Autonomous AI Database features, you can upgrade your Autonomous AI Database for Developers instance to a full paid service instance.

Resource Restrictions with Autonomous AI Database for Developers

Autonomous AI Database for Developers instances come with compute and storage resources included.

• 4 ECPUs per instance. The number of ECPUs cannot be scaled manually or automatically unless you upgrade to a full paid service instance.

• Maximum of approximately 20 GB storage per database (you may see more than this). The storage size cannot be scaled manually or automatically unless you upgrade to a full paid service instance.

• Maximum of 30 simultaneous database sessions

• The HTTP interface for Autonomous AI Database for Developers is rate limited to restrict the number of simultaneous service users. Approximately 3-6 simultaneous users can be supported across all of the APEX, Oracle REST Data Services, and Database Actions running on an Autonomous AI Database for Developers instance.

  Additional simultaneous users beyond that number may result in users encountering HTTP errors such as HTTP status code 429.

• The Maximum of 30 simultaneous database sessions limit for Autonomous AI Database for Developers allows you to work with Autonomous AI Database; however, if your usage includes many simultaneous users, many concurrent database client connections, or both, then you can exceed these limits, resulting in errors. To avoid such errors, obtain more resources for your Autonomous AI Database by upgrading to a full paid service instance. See Upgrade Autonomous AI Database for Developers Instance to a Full Paid Instance for more information.

Oracle AI Database Versions with Autonomous AI Database for Developers

Shows the available Oracle AI Database versions for Autonomous AI Database for Developers.

• Oracle Database 19c

  If you are using Autonomous AI Database for Developers with Oracle Database 19c, then many of the concepts and features of this service are further documented here:

  • Oracle Database 19c

• Oracle AI Database 26ai

  If you are using Autonomous AI Database for Developers with Oracle AI Database 26ai, then many of the concepts and features of this service are further documented here:

  • Oracle AI Database 26ai

  • Oracle AI Database New Features

Supported Features with Autonomous AI Database for Developers

Autonomous AI Database for Developers supports most but not all of the Autonomous AI Database features.

The following features help you use your Autonomous AI Database instance for development tasks:

• Cloning: Autonomous AI Database for Developers instances are low-cost, fixed shape databases intended for development and testing uses cases, and are not recommended for production use cases. In the Autonomous AI Database Free Developer tier, cloning is supported only from a running database. Cloning from a backup is not supported. For uses such as full scale load testing and production deployments or to access all Autonomous AI Database features, you can clone an Autonomous AI Database for Developers instance to a full paid service instance.

  See Clone an Autonomous AI Database Instance for instructions.

• Service Maintenance: Autonomous AI Database for Developers instances have the same patching schedule as full paid service instances.

  See About Scheduled Maintenance and Patching for more information.

• Database Application Development and Developer Tools: Autonomous AI Database for Developers provides all of the developer-related features and built-in tools that a full paid service Autonomous AI Database offers.

  See About Autonomous AI Database Built-in Tools for more information.

• Backup and Restore Operations:

  You can use backup and restore functionality with an Autonomous AI Database for Developers instance.

  See Backup and Restore Autonomous AI Database Instances for more information.

Autonomous AI Database for Developers comes with a service level objective (SLO) of 99.5%, and you can log service requests (SRs) to Oracle Support for assistance. However, there is no Severity 1 SR support for Autonomous AI Database for Developers instances. See Get Help, Search Forums, Contact Support and Create a Service Request to learn how to contact Oracle Support for assistance.

Provisioning and Cloning Workflow with Autonomous AI Database for Developers

You can provision or clone Autonomous AI Database for Developers from the Oracle Cloud Infrastructure(OCI) console or using the API.

Provisioning or cloning Autonomous AI Database for Developers instances from the OCI console follows the same workflow as provisioning or cloning a full paid service Autonomous AI Database. In the Configure the database step, select Autonomous AI Database for Developers.

See Provision an Autonomous AI Database Instance and Clone an Autonomous AI Database Instance for more information.

Upgrade Autonomous AI Database for Developers Instance to a Full Paid Instance

You can upgrade an Autonomous AI Database for Developers instance to a full paid service instance.

If your Oracle Cloud Infrastructure account is in a trial period or has paying status you can upgrade your Autonomous AI Database for Developers database to a full paid service instance as follows:

1. From the Oracle Cloud Infrastructure left navigation menu click Oracle AI Database and then click Autonomous AI Database.

2. On the Autonomous AI Databases page select an Autonomous AI Database for Developers (Developer) instance from the links under the Display name column.

3. On the Autonomous AI Database Details page, from the More actions drop-down list select Upgrade instance to full paid service.

4. Click Upgrade instance to full paid service.

When you upgrade from an Autonomous AI Database for Developers instance to a full paid service instance, you get an instance with the same workload type. The ECPU and storage in the upgraded paid instance are initially set to the minimum ECPU and storage values based on your workload type. The upgrade to a full paid service instance is an online operation and does not incur any downtime or dropped connections.

Note: After you upgrade you can scale up your compute and storage resources to fit your needs.

Features Not Available in Autonomous AI Database for Developers

There are some features that are not available with an Autonomous AI Database for Developers instance, compared to a full paid service instance.

The limitations for Autonomous AI Database for Developers are in place to ensure that instances are specifically used as a development sandbox and to assist you in working with Autonomous AI Database. When you want to use a feature that is not available, you can upgrade to a full paid service Autonomous AI Database.

Autonomous AI Database for Developers restrictions and exclusions:

• Does not support disaster recovery options, including: Autonomous Data Guard, Backup-Based Disaster Recovery, or OCI Full Stack Disaster Recovery

• Supports ECPUs only (does not support OCPUs)

• Comes with fixed compute and storage sizing and does not support compute manual scaling or auto scaling, or storage scaling

• Does not support elastic pools

• Does not provide an SLA guarantee

• Use of refreshable clones is not allowed

• Does not provide auto start-stop schedules

• Does not support Bring Your Own License (BYOL) licensing

• Autonomous AI Database for Developers databases cannot be provisioned with a private endpoint and cannot reside within a Virtual Cloud Network (VCN). See Configure Private Endpoints When You Provision or Clone an Instance for further information on private endpoints.