This topic describes how to provision an Autonomous Exadata Infrastructure resource for Autonomous Databases with dedicated deployment, using the Oracle Cloud Infrastructure Console or the API. For an overview of the dedicated deployment option, see Overview of Autonomous Database Dedicated Deployments.
The infrastructure resource includes the physical Exadata hardware and intelligent Exadata software. Once you have provisioned an infrastructure instance, you can provision one or more Autonomous Container Databases to run on your infrastructure. To provision an Autonomous Database, you must have both an infrastructure resource and at least one container database available.
This topic is not applicable to Autonomous Databases using the serverless deployment option.
To create an Autonomous Exadata Infrastructure resource, 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.
- You will also need a Virtual Cloud Network and a Subnet, which you create using Oracle Cloud Infrastructure's Networking service. For information on creating and managing these resources, see VCNs and Subnets.
- Open the navigation menu. Under Database, click Autonomous Transaction Processing or Autonomous Data Warehouse.
- Choose your Compartment.
- Click Autonomous Exadata Infrastructure.
- Click Create Autonomous Exadata Infrastructure.
In the Create Autonomous Exadata Infrastructure dialog, enter the following general information:
- Display Name: A user-friendly description or other information that helps you easily identify the infrastructure resource. The display name does not have to be unique. Avoid entering confidential information.
- Compartment: Specify the compartment in which the Autonomous Exadata Infrastructure will be created.
- Availability Domain: Select an One or more isolated, fault-tolerant Oracle data centers that host cloud resources such as instances, volumes, and subnets. A region contains one or more availability domains. for the Autonomous Exadata Infrastructure.
Shape: Read only. Oracle Cloud Infrastructure currently offers the Exadata.Quarter2.92 shape for provisioning an Autonomous Exadata Infrastructure resource. This shape has 92 cores, 106 TB storage, and 1440 GB RAM. See Exadata X7 shapes for more information on Exadata shape specifications.
Enter the following network information:
- Virtual cloud network compartment: The compartment containing the VCN you wish to use for the Autonomous Exadata Infrastructure. The default value is the user's current compartment. Click change compartment to select a VCN in a different compartment.
- Virtual cloud network: The VCN in which to launch the Autonomous Exadata Infrastructure.
- Subnet compartment: The compartment containing the subnet you wish to use for the Autonomous Exadata Infrastructure. The default value is the user's current compartment. Click change compartment to select a subnet in a different compartment.
- Subnet: The subnet to which the Autonomous Exadata Infrastructure should attach. Do not use a subnet that overlaps with 188.8.131.52/24.
Use network security groups to control traffic: Optional. You can specify up to five network security groups (NSGs) for your Autonomous Exadata Infrastructure resource by selecting this option. NSGs function as virtual firewalls, allowing you to apply a set of ingress and egress security rules to your infrastructure resource. A maximum of five NSGs can be specified. To add an NSG, select the compartment containing the NSG using the Network security group compartment selector, then select the NSG itself using the Network security group selector.
For more information on creating and working with NSGs, see Network Security Groups.
Note that if you choose a subnet with a security list, the security rules for the infrastructure resource will be a union of the rules in the security list and the NSGs.
Optionally, you can specify the date and start time for the Autonomous Exadata Infrastructure quarterly maintenance.
Oracle recommends that you define the acceptable maintenance times for your Autonomous Exadata Infrastructure resources and Autonomous Container Databases. Doing so will prevent maintenance runs from occurring at times that would be disruptive to regular database operations.To change the Autonomous Exadata Infrastructure maintenance schedule
- In the Create Autonomous Exadata Infrastructure dialog, click Modify Schedule.
- In the Automatic Maintenance Schedule dialog, select Specify a Schedule
- In the Maintenance months selector, specify at least one month for each quarter during which infrastructure maintenance will take place.
- For Week of the Month, select a week during the month that the 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. For example, to allow maintenance during the 2nd week of the month (from the 8th day to the 14th day of the month), use the value 2. Maintenance cannot be scheduled for the fifth week of months that contain more than 28 days.
- For Day of the Week, select the day of the week that the maintenance will take place.
- For Start Hour, select one of the six start time windows available. The maintenance will begin during the 4 hour time window that you specify and may continue beyond the end of the period chosen. The start time window is specified in universal coordinated time (UTC).
- Click Update Maintenance Schedule.
Choose the license type you wish to use. Your choice affects metering for billing. You have the following options:
- Bring your own license: If you choose this option, make sure you have proper entitlements to use for new service instances that you create.
- License included: With this choice, the cost of the cloud service includes a license for the Database service.
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.
- Click Create Autonomous Exadata Infrastructure.
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 LaunchAutonomousExadataInfrastructure API operation to create an Autonomous Exadata Infrastructure resource.
After creating an Autonomous Exadata Infrastructure resource, you can create one or more Autonomous Container Databases within your infrastructure. You must have provisioned both an infrastructure resource and at least one container database before you can create your first Autonomous Database in Oracle Cloud Infrastructure.