Creating an Autonomous Container Database
This topic describes how to provision a new Autonomous Container Database using the Oracle Cloud Infrastructure Console or the API. Container databases are only necessary for Autonomous Databases on dedicated Exadata infrastructure. For a brief overview, see Overview of Autonomous Database on Dedicated Exadata Infrastructure.
This topic is not applicable to Autonomous Databases on shared Exadata infrastructure.
To create an Autonomous Container Database, you must be given the required type of access in a policy written by an administrator, whether you're using the Console or the REST API with an SDK, CLI, or other tool. If you try to perform an action and get a message that you don’t have permission or are unauthorized, confirm with your administrator the type of access you've been granted and which compartment you should work in. See Authentication and Authorization for more information on user authorizations for the Oracle Cloud Infrastructure Database service.
- To create an Autonomous Container Database, you must have an available Autonomous Exadata Infrastructure instance. For information on creating an infrastructure instance, see Creating an Autonomous Exadata Infrastructure Resource.
Using the Oracle Cloud Infrastructure Console
To create an Autonomous Container Database
Open the navigation menu. Under Database, click Autonomous Transaction Processing or Autonomous Data Warehouse.
- Click Autonomous Container Database.
- Click Create Autonomous Container Database.
In the Create Autonomous Container Database dialog, enter the following database information:
- Compartment: Specify the compartment in which the container database will be created.
- Display Name: A user-friendly description or other information that helps you easily identify the resource. The display name does not have to be unique. Avoid entering confidential information.
Choose the Autonomous Exadata Infrastructure you wish to use to create your container database:
- Compartment: Specify the compartment containing the Autonomous Exadata Infrastructure you wish to use for your container database.
- Autonomous Exadata Infrastructure: Choose an Autonomous Exadata Infrastructure for your container database. See Creating an Autonomous Exadata Infrastructure Resource for more information.
Optionally, you can change the default scheduling and maintenance patching type for your Autonomous Container Database maintenance. The patch type choices are Release Update (RU) and Release Update Revision (RUR). The Release Update setting installs only the most current release update, while the Release Update Revision 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).
The following Advanced Options are available:
- 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.
- Management - Optionally, you can specify the backup retention policy, which controls the length of time you retain backups in the Autonomous Container Database. The choices are 7 days, 15 days, 30 days, and 60 days. The default setting is 60 days.
- Click Create Autonomous Container Database.
After creating an Autonomous Container Database, you can create one or more Autonomous Databases within the container database.
- Click Configure Maintenance. In the Edit Automatic Maintenance dialog that opens, you can configure both the maintenance schedule and the patch type.
For Maintenance Type, select either Release Update (RU) or Release Update Revision (RUR). Learn more.
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 will be scheduled to precede your container database maintenance.
- Under Maintenance months, specify at least one month for each quarter during which Autonomous Exadata Infrastructure maintenance will take place.
- 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.
- Click Save Changes.
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 CreateAutonomousContainerDatabase API operation to create an Autonomous container database.