Oracle Cloud Infrastructure Documentation

Managing an Autonomous Container Database

This topic describes the database management tasks for Autonomous Container Databases that you complete using the Oracle Cloud InfrastructureConsole or the API. Container databases are used by Autonomous Databases on dedicated Exadata infrastructure. See Overview of Autonomous Database on Dedicated Exadata Infrastructure for more information.


    This topic is not applicable to Autonomous Databases on shared Exadata infrastructure.

The following management operations can be performed on Autonomous Container Databases in Oracle Cloud Infrastructure:

  • Edit the backup retention policy. By default, database backups are retained for 60 days. You have the option of retaining backups for 7, 15, 30, or 60 days. The current backup retention policy for an Autonomous Container Database is displayed on the Autonomous Container Database details page.
  • Configure the type of database maintenance. You can choose to use Release Update (RU) or Release Update Revision (RUR) updates for your Autonomous Container Database maintenance. Release Update (RU): Autonomous Database installs only the most current release update. Release Update Revision (RUR): Autonomous Database installs the release update plus additional fixes.

    For information about Release Updates (RUs) and Release Updatate Revisions (RURs), see Release Update Introduction and FAQ (Doc ID 2285040.1) in the My Oracle Support online help portal (MOS login required).

  • Configure the scheduling for yoru Autonomous Container Database.
  • View the Autonomous Container Database next scheduled maintenance and maintenance history.
  • Skip a scheduled maintenance run. For container databases, you can skip maintenance runs for up to 2 consecutive quarters if needed.
  • Perform a rolling restart of databases within an Autonomous Container Database. You can perform a "rolling restart" on all the Autonomous Databases in an Autonomous Container Database to ensure that the current memory allocation is optimized. During a rolling restart, each node of an Autonomous Database is restarted separately while the remaining nodes continue to be available. No interruption of service occurs during a rolling restart. You cannot perform a container database restart if a backup is in progress.
  • Terminate an Autonomous Container Database. Note that you must terminate all Autonomous Databases within a container database before you can terminate the container database itself.

Using the Oracle Cloud Infrastructure Console

To set the backup retention policy for an Autonomous Container Database
To configure the automatic maintenance schedule for an Autonomous Container Database
To configure the type of maintenance patching for an Autonomous Container Database
To view the next scheduled maintenance run of an Autonomous Container Database
To view the maintenance history of an Autonomous Container Database
To reschedule or skip a scheduled maintenance run for an Autonomous Container Database
To perform a rolling restart of databases within an Autonomous Container Database
To move an Autonomous Container Database to another compartment
To terminate an Autonomous Container Database

Using the API

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.

Use the UpdateAutonomousContainerDatabase API operation to perform the following management actions:

  • Set the backup retention period for an Autonomous Container Database.
  • Set the maintenance patching type of an Autonomous Container Database.

Use the UpdateMaintenanceRun API operation to skip a container database maintenance run.

Use the ListMaintenanceRun API to get a list of maintenance runs in a specified compartment. Can be used to see maintenance history and scheduled maintenance runs.

Use the RestartAutonomousContainerDatabase API operation to perform a rolling restart on a container database.

Use the ChangeAutonomousContainerDatabaseCompartment API operation to move a container database to another compartment.

Use the TerminateAutonomousContainerDatabase API operation to terminate a container database.