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.

Note

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 your Autonomous Container Database.
  • View the Autonomous Container Database next scheduled maintenance and maintenance history.
  • Immediately patch an Autonomous Container Database
  • Skip a scheduled maintenance run. For container databases, you can skip maintenance runs for up to two consecutive quarters, if necessary.
  • Edit the maintenance patch version of your Autonomous Container Database.
  • 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
  1. Open the navigation menu. Under Oracle Database, click Autonomous Data Warehouse, Autonomous JSON Database, or Autonomous Transaction Processing.
  2. Choose your Compartment.
  3. Under Autonomous Database, click Autonomous Container Database.
  4. In the list of Autonomous Container Databases, click on the display name of the container database you are interested in.
  5. On the Autonomous Container Database details page, under Backup, click the Edit link in the Backup Retention Field.
  6. Specify a backup retention period from the list of choices.
  7. Click Save Changes.
To configure the automatic maintenance schedule for an Autonomous Container Database
  1. Open the navigation menu. Under Oracle Database, click Autonomous Data Warehouse, Autonomous JSON Database, or Autonomous Transaction Processing.
  2. Choose your Compartment.
  3. Under Autonomous Database, click Autonomous Container Database.
  4. In the list of Autonomous Container Databases, click on the display name of the container database you are interested in.
  5. On the Autonomous Container Database details page, under Maintenance, click the edit link in the Maintenance Details field. In the Edit Automatic Maintenance dialog that opens, you can configure both the maintenance schedule and the patch type.
  6. Optionally, you can change the maintenance patch type. To edit this setting, select either Release Update (RU) or Release Update Revision (RUR). Learn more.

  7. To configure the maintenance schedule, select Specify a schedule in the Configure the automatic maintenance schedule section. Choose your preferred month, week, weekday, and start time for container database maintenance. Autonomous Container Database maintenance should be scheduled so that it follows after the maintenance scheduled for the associated Autonomous Exadata Infrastructure. To see the scheduling of the associated Autonomous Exadata Infrastructure, you can click Show Autonomous Exadata Infrastructure maintenance schedule. If you have not specified an infrastructure maintenance schedule (and Oracle is scheduling infrastructure maintenance), your infrastructure maintenance scheduling will be automatically modified so that it precedes your container database maintenance during each quarter.

    • Under Maintenance months, specify at least one month for each maintenance quarter during which you want Autonomous Exadata Infrastructure maintenance to occur.
      Note

      Maintenance quarters begin in February, May, August, and November, with the first maintenance quarter of the year beginning in February.
    • 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 Start hour, specify the hour during which the maintenance run will begin.
  8. Click Save Changes.
To configure the type of maintenance patching for an Autonomous Container Database
  1. Open the navigation menu. Under Oracle Database, click Autonomous Data Warehouse, Autonomous JSON Database, or Autonomous Transaction Processing.
  2. Choose your Compartment.
  3. Under Autonomous Database, click Autonomous Container Database.
  4. In the list of Autonomous Container Databases, click on the display name of the container database you are interested in.
  5. On the Autonomous Container Database details page, under Maintenance, click the Edit link in the Maintenance Details field.
  6. In the Automatic Maintenance Schedule dialog, under Maintenance Type, select either Release Update (RU) or Release Update Revision (RUR).

    • 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.
  7. Optionally, you can configure the automatic maintenance schedule as described in To configure the automatic maintenance schedule for an Autonomous Container Database.
  8. Click Save Changes.
To view the next scheduled maintenance run of an Autonomous Container Database
  1. Open the navigation menu. Under Oracle Database, click Autonomous Data Warehouse, Autonomous JSON Database, or Autonomous Transaction Processing.
  2. Choose your Compartment.
  3. Under Autonomous Database, click Autonomous Container Database.
  4. In the list of Autonomous Container Databases, click on the display name of the container database you are interested in.
  5. On the Autonomous Container Database details page, under Maintenance, click the View link in the Next Maintenance field.
  6. On the Maintenance page, under Autonomous Database Maintenance, click Maintenance. In the list of maintenance events, you can the details of scheduled maintenance runs. Maintenance event details include the following:

    • The status of the scheduled maintenance run
    • The type of maintenance run (quarterly software maintenance or a critical patch)
    • The OCID of the maintenance event.
    • The start time and date of the maintenance
To view the maintenance history of an Autonomous Container Database
  1. Open the navigation menu. Under Oracle Database, click Autonomous Data Warehouse, Autonomous JSON Database, or Autonomous Transaction Processing.
  2. Choose your Compartment.
  3. Under Autonomous Database, click Autonomous Container Database.
  4. In the list of Autonomous Container Databases, click on the display name of the container database you are interested in.
    1. On the Autonomous Container Database details page, under Maintenance, click the View link in the Next Maintenance field.
  5. On the Maintenance page, under Autonomous Database Maintenance, click Maintenance History. In the list of past maintenance events, you can click on an individual event title to read the details of the maintenance that took place. Maintenance event details include the following:

    • The category of maintenance (quarterly software maintenance or a critical patch)
    • Whether the maintenance was scheduled or unplanned
    • The OCID of the maintenance event.
    • The start time and date of the maintenance
To reschedule or skip scheduled maintenance for an Autonomous Container Database
  1. Open the navigation menu. Under Oracle Database, click Autonomous Data Warehouse, Autonomous JSON Database, or Autonomous Transaction Processing.
  2. Choose your Compartment.
  3. In the Autonomous Database section, click Autonomous Container Database.
  4. In the list of Autonomous Container Databases, click the display name of the container database that you want to manage.
  5. On the Autonomous Container Database details page, in the Maintenance section, click the View link in the Next Maintenance field.
  6. On the Maintenance page, any container database maintenance events planned for the next 15 days will appear in the list of maintenance events.

    To skip scheduled maintenance for a container database, click Skip.
    Note

    You cannot skip scheduled maintenance more than twice, consecutively.

    To reschedule maintenance, click Edit and enter a start time for the update in the Edit Maintenance dialog. Make sure that your specified container database maintenance window is later in the quarter than your scheduled Exadata infrastructure maintenance.

To immediately patch an Autonomous Container Database

After you schedule maintenance for your Autonomous Container Databases, you can patch the component, immediately, at any time before scheduled maintenance occurs. If you choose to patch a Autonomous Container Database, immediately, while another component is in the process of maintenance, then this maintenance operation gets queued and will begin, in turn.

  1. Open the navigation menu. Under Database, click Autonomous Transaction Processing or Autonomous Data Warehouse.
  2. Choose your compartment from the Compartment drop-down list.
  3. In the Dedicated Infrastructure section, click Autonomous Container Database to display a list of Autonomous Container Databases for your selected compartment.
  4. Click the display name of the Autonomous Container Database that you want to patch.
  5. On the Autonomous Container Database Details page, in the Maintenance section, click the View link in the Next Maintenance field to display the Maintenance page for the Autonomous Container Database that you want to patch.
  6. In the Autonomous Container Database section, click the Patch Now link in the Scheduled Start Time field to display the Run Maintenance dialog.
  7. Click Run Maintenance to start the patching operation.
To edit the maintenance patch version of an Autonomous Container Database

You can select from a list of available patches of either maintenance type (release update or release update revision) to apply to your Autonomous Container Database during scheduled maintenance.

  1. Open the navigation menu. Under Oracle Database, click Autonomous Data Warehouse, Autonomous JSON Database, or Autonomous Transaction Processing.
  2. Choose your compartment from the Compartment drop-down.
  3. In the Autonomous Database section, click either Autonomous Container Database or Autonomous Exadata Infrastructure.
  4. In the list of Autonomous Container Databases, click the display name of the container database that you want to manage.Alternatively, if you clicked Autonomous Exadata Infrastructure in the previous step, then click the name of the Exadata infrastructure that contains the Autonomous Container Database that you want to edit.
  5. On the Autonomous Container Database details page or the Autnomous Exadata Infrastructure Details page, in the Maintenance section, click the View link in the Next Maintenance field.
  6. On the Maintenance page, click the Edit link in the Version field to display the Edit Maintenance dialog.
  7. Select the database version with which you want to patch your Autonomous Container Database.
    Note

    • You must select a version that is later than the current version of the Autonomous Container Database.
    • The list of available versions may contain both release update (RU) and release update revision (RUR) maintenance types. Your configured maintenance policy does not change if you choose a maintenance type other than that for which your Autonomous Container Database maintenance schedule is configured.
  8. Click Save Changes.
To perform a rolling restart of databases within an Autonomous Container Database
  1. Open the navigation menu. Under Oracle Database, click Autonomous Data Warehouse, Autonomous JSON Database, or Autonomous Transaction Processing.
  2. Choose your Compartment.
  3. Under Autonomous Database, click Autonomous Container Database.
  4. In the list of Autonomous Container Databases, click on the display name of the container database you are interested in.
  5. On the Autonomous Container Database details page, click Restart.
  6. In the confirmation dialog, type the name of the Autonomous Container Database.
  7. Click Restart.
To move an Autonomous Container Database to another compartment
Note

  • To move resources between compartments, resource users must have sufficient access permissions on the compartment that the resource is being moved to, as well as the current compartment. For more information about permissions for Database resources, see Details for the Database Service.
  • If your Autonomous Container Database is in a security zone, the destination compartment must also be in a security zone. See the Security Zone Policies topic for a full list of policies that affect Database service resources.
  1. Open the navigation menu. Under Oracle Database, click Autonomous Data Warehouse, Autonomous JSON Database, or Autonomous Transaction Processing.
  2. Choose your Compartment.
  3. Under Autonomous Database, click Autonomous Container Database.
  4. In the list of Autonomous Container Databases, click on the display name of the container database you wish to move.
  5. Click Move Resource.
  6. Select the new compartment.
  7. Click Move Resource.

    For information about dependent resources for Database resources, see Moving Database Resources to a Different Compartment.

To terminate an Autonomous Container Database
  1. Open the navigation menu. Under Oracle Database, click Autonomous Data Warehouse, Autonomous JSON Database, or Autonomous Transaction Processing.
  2. Choose your Compartment.
  3. Under Autonomous Database, click Autonomous Container Database.
  4. In the list of Autonomous Exadata Infrastructure resources, click on the display name of the infrastructure resource you are interested in.
  5. Click Terminate.
  6. Confirm that you wish to terminate your Autonomous Exadata Infrastructure in the confirmation dialog.

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.