Create an Autonomous Database
In an Autonomous Data Guard setup, you can not create an Autonomous Database in an Autonomous Container Database (ACD) whose standby ACD is in a snapshot standby role.
Required IAM Policies
manage autonomous-databases
read autonomous-container-databases
Related Live Labs
For a "try it out" alternative that demonstrates these instructions, see Lab 1: Provisioning Databases in Oracle Autonomous Database Dedicated for Developers and Database Users Workshop.Procedure
- Fill out the Create Autonomous Database page with the following information:
Setting Description Notes Compartment
Select a compartment to host the Autonomous Database.
Display name
Enter a user-friendly description or other information that helps you easily identify the Autonomous Database.
Avoid entering confidential information.
Database name
Provide a name for the new Autonomous Database.
Must consist of letters and numbers only. The maximum length is 30 characters.
The same database name cannot be used for multiple Autonomous Databases in the same Autonomous Exadata VM Cluster.
Workload type
Choose Data Warehouse or Transaction Processing. Determines the configuration of the new Autonomous Database.
JSON and APEX workload types are not supported on dedicated Exadata infrastructure.
Deployment type
Select Dedicated Infrastructure. APPLIES TO: 
Oracle Public Cloud onlyAutonomous Container Database
Select an Autonomous Container Database (ACD) in which to create the Autonomous Database.
Start by choosing whether you want a standard ACD or an ACD configured to use Autonomous Data Guard.
Click Change Compartment to select from a different compartment.
The Autonomous Database software version is determined by the Database Software Version of the ACD chosen in this step.
If you choose an ACD configured to use Autonomous Data Guard, two databases of the CPU count and storage you select are created: one in a primary container database, and one (a synchronized copy) in a standby container database. For more information, see Manage Primary and Standby Databases in an Autonomous Data Guard Configuration .
You can not create an Autonomous Database in an ACD whose standby ACD is in a snapshot standby role.
Suppose an ACD with a cross-region Autonomous Data Guard association has a switchover or failover, and its standby assumes the primary role. In this case, creating a Autonomous Database in such an ACD will fail because the replicated vault used by the standby is read-only.
You can not create an Autonomous Database for Developers instance on an Autonomous Data Guard enabled container database.
Configure the database: Free instance Toggle the Free instance button on, if you want to create an Autonomous Database for Developers instance.
ECPU count and Storage (GB) are auto-populated with 4 and 32 respectively because Autonomous Database for Developers comes fixed at 4 ECPUs and 32GB storage.
Compute auto scaling is disabled because developer database instances do not support manual or auto-scaling.
Autonomous Database for Developers is a free tier offering designed for database development and functional testing activities. See Autonomous Database for Developers for more details.
As developer database instances can only be created on an ECPU-based ACDs without Autonomous Data Guard, the Free instance toggle button is disabled for ACDs with OCPU, Autonomous Data Guard, or both.
Configure the database: CPU count
Select the number of CPUs for your database from the list of provisionable CPUs.
The CPU type, that is, ECPU or OCPU is determined by the parent Autonomous Exadata VM Cluster's compute type. This value defaults to 4 ECPUs or 1 OCPU depending on the CPU type. Refer to Compute Models in Autonomous Database for more details. For databases that need 1 or more OCPUs or 2 or more ECPUs, you must specify the number of assigned CPUs as an integer. For example, you cannot assign 3.5 ECPUs to a database. The next available number of ECPUs above 3 is 4.
You can also assign OCPU count from 0.1 to 0.9 in increments of 0.1 OCPUs for databases that do not need an entire OCPU. This allows you to overprovision CPU and run more databases on each infrastructure instance. Refer to CPU Overprovisioning for more details.
CPU overprovisioning is not supported for Autonomous Databases that use ECPUs.
Configure the database: CPU auto scaling
Enable or disable CPU auto scaling, which permits Autonomous Database to automatically use up to three times as many CPUs as specified by CPU Count as the workload on the database increases.
Configure the database: Storage (GB)
Specify the storage to allocate to your database in terabytes (GB), with a minimum value of 32 GB.
The default values are 1024 GB for Autonomous Data Warehouse and 32 GB for the Autonomous Transaction Processing workloads.
Configure the database: Elastic Pools
If Compute auto scaling disabled, you can choose to create an elastic pool as a pool leader or join an existing elastic pool as a pool member.
- Click Show advanced options.
- Select Enable elastic pool.
- To join an existing pool, select Join an existing elastic pool and select a pool leader from Select pool leader in compartment.
- To create a new elastic pool, select Create an elastic pool, and select a pool size for Pool ECPU count from available list of pool shapes: 128, 256, 512, 1024, 2048, or 4096.
Only Autonomous Transaction Processing databases without Autonomous Data Guard that use ECPU compute model can be used to create an elastic pool.
Username
Denotes the database's username. This is a read-only value.
Password
Set the password for the Admin database user in your new database.
The password must meet the strong password complexity criteria based on Oracle Cloud security standards. For more information on the password complexity rules, see Create Database Users.
Confirm password
Re-enter the password for confirmation.
Access Control
Optionally, click Modify Access Control to configure network access by enabling database level access control, which is disabled by default.
Clicking Modify Access Control opens the Edit Access Control List dialog. Database-level access control
To configure network access by creating an access control list (ACL), select Enable database-level access control, and click + Access Control Rule on the Edit Access Control List dialog.
Depending on the types of addresses in your list, select one of the following options from the IP notation type drop-down selector:- IP Address: Specify individual IP addresses. You can use commas to separate multiple IP addresses.
- CIDR Block: Specify ranges of public IP addresses using CIDR notation. You can use commas to separate multiple values.
An ACL provides additional protection to your Autonomous Database by allowing only the client with specific IP addresses to connect to the database. See Restrict Access Using a Network Access Control List for details.
Standby database access control
If the parent Autonomous Container Database uses Autonomous Data Guard, you can define access control for the standby database also.
Depending on your preference, select one of the following options for Standby database access control:- Choose Same as primary database to apply the ACL that you already defined for the primary database to the standby database as well. This is the default selection.
- Choose Define standby database access control to define a separate ACL for the standby database. By default, the standby database ACL is initialized with the same values as the primary database ACL. Add or modify the entries as needed.
By default, the ACL defined for the primary database applies to the standby database also. Contact email
Provide contact emails where you can receive operational notifications, announcements, and unplanned maintenance notifications.
Oracle recommends using the email address of an administrator group rather than an individual's, whenever possible, to ensure no important notifications or announcements are missed.
Show/hide advanced options
By default, advanced options are hidden. Click Show advanced options to display them.
Advanced options: Encryption key
The encryption key settings are inherited from the parent Autonomous Container Database. Advanced options: Management
Choose a Character Set and National Character Set from the drop-down list.
Refer to Character Set Selection for Dedicated Autonomous Database for more details.
Advanced options: Database In-memory
Optionally, select Enable database In-memory and adjust the percentage of System Global Area (SGA) to allocate.
Please see Database In-Memory for the requirements and guidelines to use this feature with Autonomous Database.
If required, you can also disable Database In-Memory from the Oracle Cloud Infrastructure (OCI) console. See Enable or Disable Database In-Memory for instructions.
Advanced options: Tags
If you want to use tags, add tags by selecting a Tag Namespace, Tag Key, and Tag Value.
Tagging is a metadata system that allows you to organize and track resources within your tenancy. See Tagging Dedicated Autonomous Database Cloud Resources.
Your display shows Provisioning until the new Autonomous Database is available.
When you create an Autonomous Database, CPU billing is initiated, billed by the second with a minimum usage period of one minute.
Parent topic: Create and Manage Dedicated Autonomous Databases