Create an Autonomous Container Database

You create an Autonomous Container Database from the Autonomous Container Databases page.

Required IAM Policies

  • Oracle Public Cloud Deployments:
    • manage autonomous-container-databases

    • use cloud-exadata-infrastructures

    • use cloud-autonomous-vmclusters

  • Exadata Cloud@Customer Deployments:
    • manage autonomous-container-databases

    • use cloud-exadata-infrastructures

    • use autonomous-vmclusters

    • use backup-destinations

Minimum Resource Requirements

To create one Autonomous Container Database, you need at least:
  • 2 OCPUs or 4 ECPUs
  • 50GB local storage

Related Live Labs

For a "try it out" alternative that demonstrates these instructions, see Lab 6: Provisioning an Autonomous Container Database in Oracle Autonomous Database Dedicated for Fleet Administrators Workshop.

Procedure

  1. Go to Autonomous Database in the Oracle Cloud Infrastructure Console.

    For instructions, see Access Dedicated Autonomous Database in the Oracle Cloud Infrastructure Console.

  2. In the side menu’s list of resource types, click Autonomous Container Database.

    The list of Autonomous Container Databases in your current Compartment is displayed.

  3. In the side menu’s Compartment list, select the Compartment where you want to create an Autonomous Container Database.

    The list of Autonomous Container Databases refreshes to show those in the selected Compartment.

  4. Click Create Autonomous Container Database.

    The Create Autonomous Container Database page is displayed.

  5. Fill out the Create Autonomous Container Database page with the following information:
    Setting Description Notes

    Compartment

    Select a compartment to host the Autonomous Exadata VM Cluster.

     

    Display name

    Enter a user-friendly description or other information that helps you easily identify the resource.

    The display name does not have to be unique and you can change it whenever you want.

    Avoid entering confidential information.

    Exadata Infrastructure

    The Exadata Infrastructure to host the new Autonomous Container Database.

    APPLIES TO: Applicable Oracle Public Cloud only

    Autonomous Exadata VM Cluster

    The Autonomous Exadata VM Cluster to host the new Autonomous Container Database.

     

    Autonomous Data Guard

    Select Enable Autonomous Data Guard to configure Autonomous Data Guard to create primary and standby autonomous container databases.

    Configuring Autonomous Data Guard enables you to keep your critical production databases available to mission critical applications despite failures.

    Configure Autonomous Data Guard: Standby Container Database

    Provide information about the standby autonomous container database: its compartment, display name, region, the underlying Exadata Infrastructure resource, and Autonomous Exadata VM Cluster in which to place it.

    If you choose to create an Autonomous Container Database with a cross-region Autonomous Data Guard association, note the following about encryption keys:
    • If you are managing keys using the OCI Vault service, you must use a key from a virtual private vault located in the region of the primary database. This vault must be replicated in the region of the standby database. See Replicating Vaults and Keys for information on creating and managing these resources.
    • The replicated vault used by the standby is read-only. So, when the standby assumes the primary role from a switchover or failover, you cannot create a new Pluggable Database or rotate the key.

    Configure Autonomous Data Guard: Protection Mode

    Choose a protection mode from Maximum Performance and Maximum Availability.

    Maximum Performance is selected by default.

    For information about Autonomous Data Guard and guidance in choosing where to place the standby autonomous container database and which protection mode to use, see About Autonomous Data Guard and Choosing Autonomous Data Guard Configuration Options.

    Configure Autonomous Data Guard: Automatic Failover

    Optionally, enable automatic failover by selecting the Enable automatic failover check-box.

    For more details about automatic failover, see Automatic Failover or Fast-Start Failover.

    Configure Automatic Maintenance

    Optionally, configure a preferred maintenance type or schedule.

    Click Modify Maintenance to display the Edit Automatic Maintenance card.

     

    Edit Automatic Maintenance: Maintenance Type

    Select a maintenance type from the Maintenance type list.

    The available options are Release Update (RU) and Release Update Revision (RUR)

    The default maintenance type is Release Update (RU).

    Currently, the Release Update Revision (RUR) maintenance type is not a selectable option. When release update revisions become available for Autonomous Database, this option will become selectable.

    Edit Automatic Maintenance: Maintenance Schedule

    Optionally, you can change the maintenance schedule from the default (No preference, which permits Oracle to schedule maintenance as needed) to Custom schedule.

    For Custom schedule, you can optionally select the months, weeks, days and hours for the schedule. If you have enabled Autonomous Data Guard, you can also select the buffer period between primary and standby maintenance.

    For guidance on choosing a custom schedule, see Settings in Maintenance Schedule that are Customizable.

    Configure Backup Destination

    You can configure the backup destination to be used for backups of Autonomous Databases created in the Autonomous Container Database.

    Select a Backup Destination Type and then specify options based on the selected type:
    • Object Storage: Stores backups in an Oracle-managed object storage container on Oracle Cloud Infrastructure.

      If you choose Object Storage as the type, you can optionally specify an internet HTTP proxy to use when connecting to the storage container. Oracle recommends using a proxy when possible for enhanced security.

    • Network File System (NFS): Stores backups in a Network File System (NFS) storage location.

      If you choose Network File System (NFS) as the type, select a previously defined Backup Destination that uses Network File System (NFS) storage.

    • Recovery Appliance: Stores backups in one of your previously defined backup destinations that uses Oracle Zero Data Loss Recovery Appliance.

      If you choose Recovery Appliance as the type, select a previously defined Backup Destination that uses Oracle Zero Data Loss Recovery Appliance, the DB_UNIQUE_NAME of the Autonomous Container Database, and the VPC user name password.

    APPLIES TO: Applicable Exadata Cloud@Customer only

    As of the current release, the Backup Destination Type cannot be changed once an Autonomous Container Database is created.

    To learn more about configuring NFS backup destination for Cloud@Customer, see Prerequisites for Backup Destinations for Exadata Cloud at Customer.

    Show/hide advanced options

    By default, advanced options are hidden. Click Show advanced options to display them.

     

    Advanced options: Management

    Change the Backup Retention Policy value to meet your needs.

    APPLIES TO: Applicable Oracle Public Cloud only

    The Backup Retention Policy value defaults to 7 days for an Autonomous Container Database on Oracle Cloud.

    The maximum backup retention period that you can choose is 60 days for Oracle Cloud.

    Advanced options: Backup

    Change the Backup Retention Period value to meet your needs.

    APPLIES TO: Applicable Exadata Cloud@Customer only

    The Autonomous Container Database on Exadata Cloud@Customer defaults Backup Retention Policy to 30 days for Object Storage and Network File System (NFS) backup destination types.

    For the Recovery Appliance backup destination type, this value is controlled by the Recovery Appliance protection policy.

    The maximum backup retention period that you can choose is 60 days for Exadata Cloud@Customer (with Object Storage and NFS).

    Advanced options: Encryption Key

    Optionally, you can configure the Autonomous Container Database to use customer-managed encryption keys instead of Oracle-managed encryption keys.

    Select Encrypt using customer-managed keys and then select either the Vault and Master encryption key or the Key Store to use for the Autonomous Container Database, depending on whether you are creating the container database on Oracle Public Cloud or on Exadata Cloud@Customer.

    By default, Encrypt using Oracle-managed keys is selected.

    You can use customer-managed encryption keys with Autonomous Data Guard-enabled Autonomous Container Databases with the primary and standby databases located in different availability domains within the same region.

    For information about using customer-managed keys, see About Master Encryption Keys.

    Advanced options: Tags

    If you want to use tags, add tags by selecting a Tag Namespace, Tag Key, and Tag Value.

    You can not modify the time zone settings for an Autonomous Exadata VM Cluster already provisioned. If needed, you can create a service request in My Oracle Support. For help with filing a support request, see Create a Service Request in My Oracle Support.

  6. Click Create Autonomous Container Database.

The list of Autonomous Container Databases refreshes to show the new Autonomous Container Database with a status of Provisioning until it is available.