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 Transaction Processing databases that use the dedicated deployment option. For a brief overview of the dedicated deployment option, see Overview of Autonomous Transaction Processing Dedicated Deployments.
- This topic is not applicable to Autonomous Databases using the serverless deployment option.
- Dedicated deployment is currently available only for the Autonomous Transaction Processing workload type.
To create an Autonomous Transaction Processing container database, you must be given the required type of access in a An IAM document that specifies who has what type of access to your resources. It is used in different ways: to mean an individual statement written in the policy language; to mean a collection of statements in a single, named "policy" document (which has an Oracle Cloud ID (OCID) assigned to it); and to mean the overall body of policies your organization uses to control access to resources. 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 A collection of related resources that can be accessed only by certain groups that have been given permission by an administrator in your organization. you should work in. See Authentication and Authorization for more information on user authorizations for the Oracle Cloud Infrastructure Database service.
See Let database and fleet administrators manage Autonomous Databases for sample Autonomous Database policies. See Details for the Database Service for detailed information on policy syntax.
- 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 Instance.
- Open the navigation menu. Under Database, click Autonomous Transaction Processing.
- Click Autonomous Container Database.
- Click Create Autonomous Container Database.
In the Create Autonomous Container Database dialog, enter the following database information:
- 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.
- Compartment: Specify the compartment in which the container database will be created.
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 Instance for more information.
Optionally, you can change the maintenance type for your Autonomous Container Database. The maintenance 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 more information, see Release Update Introduction and FAQ (Doc ID 2285040.1) in the My Oracle Support online help portal.To change the Autonomous Container Database maintenance type
- In the Create Autonomous Container Database dialog, click Modify Schedule.
- In the Automatic Maintenance Type dialog, select your desired maintenance type.
- Click Update Automatic Maintenance.
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.
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 Transaction Processing container database.
After creating an Autonomous Container Database, you can create one or more Autonomous Transaction Processing databases within the container database.