1. Open the navigation menu. Under Oracle Database, click Exadata Database Service on Cloud@Customer.
2. Click Autonomous Container Databases.
3. Click Create Autonomous Container Database.
   The Create Autonomous Container Database page is displayed.
4. Provide the following basic information:
   • Compartment: Choose the compartment in which your autonomous container database will be created.
   • Display Name: Enter a user-friendly description or other information that helps you easily identify the autonomous container database. The display name does not have to be unique. Avoid entering confidential information.
5. Select the Autonomous Exadata VM Cluster you wish to use to create your autonomous container database.
6. Optionally, you can configure an automatic maintenance schedule.
   1. Click Modify Maintenance.
   2. In the resulting dialog enter the following details:
      • Configure maintenance method: Choose between Rolling or Non-rolling maintenance methods. By default, it's always Rolling with Time Zone File update disabled.
        • Rolling: The Rolling method updates the ACD, one node at a time, with no downtime for the Autonomous Databases.
        • Non-rolling: The Non-rolling method shuts down and updates the ACD in parallel across all nodes. This method minimizes maintenance time but it requires full downtime for the ACD and all associated Autonomous Databases.

          Optionally, you can also select Enable time-zone update. Updating the time-zone file would require complete downtime for the ACD and the associated Autonomous Databases. The downtime is dependent on the amount of data that is time-zone sensitive.

          Note
          
          All the RUs that include time-zone updates will be patched using the non-rolling maintenance method (with full system downtime) only. So, if you configure your maintenance to the rolling method and enable time-zone update, all the RUs that include a time-zone update are applied in the non-rolling method only. Only those RUs without a time-zone update are applied in the rolling method.
      • Configure container database maintenance version: Choose Next release update (RU) or Latest release update (RU) to configure the next maintenance version of the Autonomous Container Database. Accordingly, the autonomous container database will be updated to the next immediate release or the latest release in the upcoming maintenance window.
      • Configure automatic maintenance schedule: You can change the maintenance schedule settings, as desired:
        • Select No preference to permit Oracle to schedule maintenance as needed based on the maintenance schedule of the Exadata Infrastructure resource hosting the Autonomous Container Database.
        • Select Custom schedule to restrict when Oracle can schedule maintenance. You can choose your preferred month, week, weekday, start time, and buffer period between primary and standby maintenance execution for the Autonomous Container Database maintenance.
      • To configure the Custome schedule, select Specify a schedule.

        Choose your preferred month, week, weekday, and start time for autonomous container database maintenance.

        • Under Week of the month, specify which week of the month maintenance will take place. Weeks start on the 1st, 8th, 15th, and 22nd days of the month, and have a duration of 7 days. Weeks start and end based on calendar dates, not days of the week. Maintenance cannot be scheduled for the fifth week of months that contain more than 28 days.
        • Under Day of the week, specify the day of the week on which the maintenance will occur.
        • Under Hour of the day, specify the hour during which the maintenance run will begin.
   3. Click Save Changes.
7. Select a Backup Destination Type:
   • Object Storage: Stores backups in an Oracle-managed object storage container on Oracle Cloud Infrastructure. Optionally, you can use this field to specify your corporate HTTP proxy. Oracle recommends using an HTTP proxy when possible for enhanced security.
   • Network File System (NFS): Stores backups in one of your previously defined backup destinations that uses Network File System (NFS) storage.
     • Select a Backup Destination.
   • Recovery Appliance: Stores backups in one of your previously defined backup destinations that uses Oracle Zero Data Loss Recovery Appliance (ZDLRA).
     • Select a Backup Destination.
     • Provide a unique name for the database.
     • Provide a VPC user name and password.

   To use ZDLRA as the Backup Destination, before creating the ACD, add the database to the Recovery Appliance, and assign a protection policy to the database.

   1. Ensure to provide the connection string that connects to the recovery appliance in an Oracle "easy connect" string format, as shown below:

      host:port/service name

      Where host is the SCAN hostname of the Zero Data Loss Recovery Appliance.

   2. Create a VPC user on the Recovery Appliance or use an existing user.

      For more information about creating VPC user accounts, see Creating Virtual Private Catalog Accounts.

   3. Add the database to the Recovery Appliance using the intended unique name of the database (db_unique_name) and intended protection policy.

      EXEC dbms_ra.add_db(db_unique_name=>'<DB_UNIQUE_NAME of the database to add>', protection_policy_name=>'<name of the protection policy to assign to the database>', reserved_space=>'<guaranteed disk space available for the protected database>');

      For example:

      EXEC dbms_ra.add_db(db_unique_name=>'ACDNAME', protection_policy_name=>'BRONZE', reserved_space=>'1024G');

      For more information about enrolling the protected database, see Enrolling the Protected Database with Recovery Appliance (Command Line).

   4. Grant access to this database to the Recovery Appliance user account.

      EXEC dbms_ra.grant_db_access(db_unique_name=>'<DB_UNIQUE_NAME of the database>', username=>'<Recovery Appliance user account>');
      

      For example:

      EXEC dbms_ra.grant_db_access(db_unique_name=>'ACDNAME', username=>'RAVPC1');

8. The following Advanced Options are available:
   • Backup retention period: Customize the retention period for automatic backups. For Recovery Appliance, you cannot select the retention period.
   • Encryption Key: Choose an encryption option, Encrypt using Oracle-managed keys or Encrypt using customer-managed keys. The default option is Oracle-managed keys.

     To use customer-managed keys, select the Encrypt using customer-managed keys option, select the compartment where you have created the Key Store, and then select the Key Store. As part of the CDB creation, a new wallet is created for the CDB in Oracle Key Vault (OKV). Also, a TDE Master Key is generated for the CDB and added to the wallet in OKV.

     Note
     
     

     • Autonomous Container Databases and Autonomous Databases only support 256-bit Hardware Security Module (HSM) Vault keys.
     • Validate OKV Key encryption post restart: OKV TDE Maser Key is validated every time you start or restart your ACD. Start or restart fails if the key is not validated. Work requests and life cycle states indicate the reason for failure.
     • View OKV keys post database restore: When you restore a CDB, the master key associated with that backup is restored as well.
     • Enable CDB backups to capture wallet name: CDB backups information about the wallet associated with the backup.
     • OKV Wallet or TDE Master Key on CDB deletion: If you delete a CDB, then the wallet and TDE Master Key remains in OKV and will not be deleted.
   • Tags: Optionally, you can apply tags. If you have permissions to create a resource, you also have permissions to apply free-form tags to that resource. To apply a defined tag, you must have permissions to use the tag namespace. For more information about tagging, see Resource Tags. If you are not sure if you should apply tags, skip this option (you can apply tags later) or ask your administrator. Avoid entering confidential information.
9. Optionally, you can save the resource configuration as a stack.
   • To save the resource configuration as a Stack:
     1. Click Save as Stack.
     2. In the resulting Save as Stack dialog, provide the following details:
        1. Name: (Optional) Provide an easy to remember descriptive name.
        2. Description: (Optional) Enter a short description.
        3. Compartment: Select a compartment where this Stack will reside.
        4. Tags: Add tags.
     3. Click Save.

        After saving the Stack, the system displays a banner with a link to the saved Stack.

     4. Click the link to open the Stack in the Resource Manager Service console.

        See, Resource Manager and Terraform.

   • To view the details of a Stack:
     1. Open the navigation menu. Under Developer Services, click Resource Manager.
     2. Click Stacks.
     3. Click the name of the Stack that you want to view details.

        Or, click the Actions menu (three dots), and select the View stack details option.

10. Click Create Autonomous Container Database.

• View the List of Autonomous Container Databases in an Autonomous Exadata VM Cluster
  
• View the List of Autonomous Container Databases in a Compartment
  

1. Open the navigation menu. Under Oracle Database, click Exadata Database Service on Cloud@Customer.
2. Click Autonomous Container Databases.
3. In the list of Autonomous Container Databases, click the display name of the database you wish to view details.

   On the Autonomous Container Database Details page encryption details are displayed under Encryption.

   If you have chosen customer-managed keys while creating the database, then you will see a link to the Encryption Key Store and OKV Wallet Name.

   Note
   
   OKV Wallet Name represents the name of the wallet in which keys for this CDB are generated on the OKV.

   Click the Key Store link to view details.

   If you have chosen Oracle-managed keys while creating the database, then you will not see the link to Encryption Key Store and OKV Wallet Name.

   Resource usage: For more information, see Resource Terminology.

   In the General Information section, the Time zone file version field displays the current time zone file version.

• Update Autonomous Container Database Maintenance Preferences
  

1. Open the navigation menu. Under Oracle Database, click Exadata Database Service on Cloud@Customer.
2. Click Autonomous Container Databases.
3. In the list of Autonomous Container Databases, click the display name of the database you wish to view details.
4. Click More actions, and then click Schedule maintenance.
5. In the resulting Schedule Maintenance panel, enter the following details:
   • Configure update type
     • Release Update (RU): Click to schedule a release update (RU) along with a time zone file update. This option is disabled if your ACD is already patched to the latest RU.
     • Time-zone file update: Click to schedule time zone file update only.
       Note
       
       Time zone files can only be updated using the non-rolling configuration method that involves full system downtime.
   • Configure maintenance method:
     • Rolling: The Rolling method updates the ACD, one node at a time, with no downtime for the Autonomous Databases.
     • Non-rolling: The Non-rolling method shuts down and updates the ACD in parallel across all nodes. This method minimizes maintenance time but it requires full downtime for the ACD and all associated Autonomous Databases.
   • Enable time-zone update

     Optionally, you can also select Enable time-zone update. Time-zone files can only be updated using the non-rolling configuration method.

     If you configure your maintenance to the rolling method and enable time-zone update, all the RUs that include a time-zone update are applied in the non-rolling method only. Only those RUs without a time-zone update are applied in the rolling method.

   • Schedule start time

     Using the calendar tool, choose a date and time for the maintenance update.

6. Click Schedule maintenance.
   Note
   
   The maintenance settings selected from the Schedule maintenance dialog apply to the maintenance update scheduled from this dialog only. These changes do not apply to the maintenance preferences defined at the ACD level.

1. Open the navigation menu. Under Oracle Database, click Exadata Cloud@Customer.
2. Click Autonomous Container Databases.
3. In the list of Autonomous Container Databases, click the display name of the database you wish to view details.
4. On the Autonomous Container Database Details page, click Rotate Encryption Key.
5. On the Rotate Encryption Key dialog, click Rotate Encryption Key.

1. Open the navigation menu. Under Oracle Database, click Exadata Database Service on Cloud@Customer.
2. Click Autonomous Container Databases.
3. In the list of Autonomous Container Databases, click the display name of the container database you are interested in.
4. On the Autonomous Container Database details page, under Backup, click the Edit link in the Backup retention policy field.
5. Specify a backup retention period from the list of choices.
6. Click Update.

1. Open the navigation menu. Under Oracle Database, click Exadata Database Service on Cloud@Customer.
2. Click Autonomous Container Databases.
3. In the list of Autonomous Container Databases, click the display name of the container database you are interested in.
4. On the Autonomous Container Database details page, under Maintenance, click the edit link in the Maintenance Details field.
5. In the Edit Automatic Maintenance dialog that opens, configure automatic maintenance schedule.
   • No preference: The system assigns a date and start time for container database maintenance.
   • Specify a schedule: Choose your preferred month, week, weekday, and start time for container database maintenance.
6. Click Save Changes.

1. Open the navigation menu. Under Oracle Database, click Exadata Database Service on Cloud@Customer.
2. Click Autonomous Container Databases.
3. In the list of Autonomous Container Databases, click the display name of the container database you are interested in.

   Autonomous Container Database details page is displayed.

   Autonomous Container Database details page displays details that include total OCPU, available OCPU, reclaimable OCPU, and database memory per OCPU in GB.

4. On the Autonomous Container Database details page, click Restart.
5. In the confirmation dialog, type the name of the Autonomous Container Database.
6. Click Restart.

   (or)

   1. Open the navigation menu. Under Oracle Database, click Exadata Database Service on Cloud@Customer.
   2. Click Autonomous Container Databases.
   3. In the list of Autonomous Container Databases, click the Actions icon (three dots) for the container database you are interested in, and then select Restart.
   4. In the confirmation dialog, type the name of the Autonomous Container Database.
   5. Click Restart.

1. Open the navigation menu. Under Oracle Database, click Exadata Database Service on Cloud@Customer.
2. Click Autonomous Container Databases.
3. In the list of Autonomous Container Databases, click the display name of the container database you wish to move.
4. Click Move Resource.
5. Select the new compartment.
6. Click Move Resource.

1. Open the navigation menu. Under Oracle Database, click Exadata Database Service on Cloud@Customer.
2. Click Autonomous Container Databases.
3. In the list of Autonomous Container Databases, click the display name of the infrastructure resource you are interested in.
4. Click Terminate.
5. In the confirmation dialog, type the name of the Autonomous Container Database, and then click Terminate Autonomous Container Database.

For information about using the API and signing requests, see REST APIs and Security Credentials. For information about SDKs, see Software Development Kits and Command Line Interface.

The following table lists the REST API endpoints to manage Autonomous Container Databases.