Compute Model

This is the compute billing metric for Autonomous Database. You can select either ECPU or OCPU models.

The default model is ECPU, and is based on the number of cores elastically allocated from a pool of compute and storage servers. You can change to OCPU compute model during creation of an AVMC. The OCPU compute model is based on the physical core of a processor with hyper-threading enabled.

The compute model chosen here will apply to all the Autonomous Container Databases and Autonomous Databases created in this Autonomous Exadata VM Cluster resource.

DB Server Selection

AVMCs can be provisioned across any number of DB servers (VMs). You can view and select from a list of available VMs during provisioning of an AVMC.

During provisioning of an AVMC, you must select at least 2 DB Servers to deploy an AVMC resource. A minimum of 2 DB Servers are needed for high availability (HA) configuration.

You can not add or remove DB Servers after provisioning an AVMC.

Maintenance Schedule

In general, Oracle schedules and performs entire fleet maintenance spread throughout each quarter.

You can let Oracle handle maintenance scheduling, or you can set a specific maintenance window when Oracle can begin maintenance operations.

You can schedule separate maintenance runs for each Autonomous VM Cluster on the same Exadata Infrastructure.

You can change the maintenance schedule from the default (No preference, which permits Oracle to schedule maintenance as needed) by selecting the months, weeks, days and hours for the schedule. You can also set a lead time to receive a notification message about an upcoming maintenance from Oracle.

Manage Resources

You can customize compute, storage, and memory of each Autonomous Exadata VM Cluster configuration for the intended workload. You can monitor these resources using by viewing resource allocation and usage visualizations.

Optionally, while provisioning an AVMC, you can define a suitable value for the following resource management attributes to suit your needs:

• Maximum number of Autonomous Container Databases: The number of ACDs specified represents the upper limit on ACDs.
• CPU count per VM or node: Specify the CPU count for each individual VM. The minimum value is 5 OCPUs or 20 ECPUs per VM.
• Database memory per CPU (GB): The memory per CPU allocated for the Autonomous Databases in the Autonomous VM Cluster.
• Allocate Storage for Local Backups: For Exadata Cloud@Customer, you can check this option to configure the Exadata storage to enable local database backups.
• Database storage (TB): Data storage allocated for Autonomous Database creation in the Autonomous VM Cluster.

The terms VM and node are used interchangeably between Oracle Exadata Cloud@Customer and Oracle Public Cloud deployments.

Network Settings

On Oracle Public Cloud, you define network access control using components of the Networking service. You create a Virtual Cloud Network (VCN) containing private Subnets in which your autonomous databases are network-accessible.

APPLIES TO: Oracle Public Cloud only

The following settings can be adjusted while provisioning an AVMC:

• Virtual cloud network: The virtual cloud network (VCN) in which you want to create the new AVMC.
• Subnet: A subnet within the above selected VCN for the new Autonomous Exadata VM Cluster.

VM cluster network

On Exadata Cloud@Customer, you define network access controls by specifying a client network within your data center and recording it in a VM Cluster Network resource within the Exadata Infrastructure resource.

APPLIES TO: Exadata Cloud@Customer only

The VM cluster network in which to create the new Autonomous Exadata VM Cluster is selected during while provisioning an AVMC.

License Type

You can choose to use existing Oracle Database software licenses or subscribe to Oracle Database software licenses.

There are two options for the license type:

• Bring your own license: Select this option if your organization already owns Oracle Database software licenses that you want to use on Autonomous Database.
• License included: Select this option to subscribe to Oracle Autonomous Database software license

Time Zone

You can set the time-zone of each Autonomous Exadata VM Cluster.

The default time zone for the Autonomous Exadata VM Cluster is UTC, but you can specify a different time zone.

Listener

You can choose a Single Client Access Name (SCAN) listener port for TLS and non-TLS, and choose between one-way TLS and mTLS for database TLS certificates.

The SCAN listener ports can not be changed after provisioning the AVMC resource.

As ORDS certificates are one-way TLS certificates, choosing between one-way TLS and mutual TLS (mTLS) is applicable only to database TLS certificates.

Manage certificates

You can upload your CA-signed certificate to your Autonomous VM Cluster and use it for secure connections.

By default, Oracle managed self-signed certificates are automatically generated while provisioning an Autonomous Exadata VM Cluster (AVMC) and apply to all the databases created in that AVMC. You also have the option to use your own CA-signed server-side certificate with Autonomous Database.

You can rotate both types of certificates via the console or API.

Certificate Management