You create an Exadata Infrastructure resource from the Exadata Infrastructure page.

Required IAM Policies

manage cloud-exadata-infrastructures

use vnic

use subnet

Related LiveLabs

• Lab 2: Provisioning a Cloud Exadata Infrastructure for Autonomous Database on Dedicated Infrastructure
• Lab 4: Provisioning Exadata Infrastructure for Autonomous Database on Exadata Cloud@Customer

Procedure

1. Go to Autonomous Database in the Oracle Cloud Infrastructure Console.

   For instructions, see Access Autonomous Database in the Oracle Cloud Infrastructure Console.

2. In the side menu’s list of Autonomous Database resource types, click Exadata Infrastructure.

   The list of Exadata Infrastructure resources in your current Compartment is displayed.

3. In the side menu’s Compartment list, choose the Compartment where you want to create an Exadata Infrastructure resource.

   The list of Exadata Infrastructure resources refreshes to show those in the selected Compartment.

4. Click Create Exadata Infrastructure.

5. On the Create Exadata Infrastructure page, enter or select a value for the following:

   • Compartment: Select a compartment in which you want to create the Exadata Infrastructure resource.

   • 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, and you can change it whenever you like.

   • Availability domain: Select an availability domain where you want the resource placed.

   • Exadata system model: Choose the type of Oracle Exadata Database Machine you want the allocate to this resource.

     For capacity information about the models and their configurations, see Characteristics of Infrastructure Shapes.

     Note
     
     You can also select the Base System option to allocate a base system with reduced hardware capacity. Base System supports a single AVM Cluster, similar to X7 and X8 systems. You can not create a Multiple VM - Autonomous VM Cluster (AVMC) on Exadata Infrastructure resources provisioned on an Exadata Base system.

   • Exadata system shape: Select an Exadata system shape for the Exadata system model chosen above.

     Note
     
     X8M-2 and X9M-2 systems on Oracle Public Cloud and X10M systems on Exadata Cloud@Customer do not support fixed shapes such as quarter rack, half rack, and full rack.
     Note
     
     You can only create a Multiple VM - Autonomous VM Cluster (AVMC) on Exadata Infrastructure resources created in Oracle Cloud after the launch of the multiple VM Autonomous Databases feature. Please create a service request in My Oracle Support if you need to address this limitation and want to add an Autonomous VM Cluster to older Exadata Infrastructure resources. For help with filing a support request, see Create a Service Request in My Oracle Support.
   • Compute and Storage Configuration: Specify the number of database and storage servers for configuring your Exadata Infrastructure resource.

     • On Oracle Public Cloud: For X8M-2 and X9M-2 systems, the default configuration is 2 database servers and 3 storage servers. However, you have the flexibility to choose a different value for database servers and storage servers within a valid range. The acceptable range of values is 2 to 32 for database servers and 3 to 64 for storage servers.

       Note
       
       As X7-2 and X8-2 systems support fixed shapes such as quarter rack, half rack, and full rack, you can not configure compute and storage for these systems.

     • On Exadata Cloud@Customer deployments: The number of database servers and storage servers is pre-determined based on the Exadata system shape chosen above. You can not select a different value for database servers, but you can select another value for the Storage servers as per your requirement.

       Note
       
       In the case of X10M systems, you can pick the number of database servers and storage servers within a valid range, depending on the X10M shape you chose above.
   • Automatic Maintenance: Optionally, configure the automatic maintenance schedule by clicking Modify Schedule.

     You can then change the maintenance schedule from the default (No preference, which permits Oracle to schedule maintenance as needed) by selecting Specify a schedule and then selecting the months, weeks, days and hours for the schedule. You can also set a lead time to receive a notification message about an upcoming maintenance from Oracle. For guidance on choosing a custom schedule, see Settings in Maintenance Schedule that are Customizable.

     When you are finished, click Update Maintenance Schedule.

   • Contact Email(s): You can provide up to ten contacts' email address for operational notifications and announcements. Click Add Contact after entering each email address.

6. If you want to use Tags, click Show Advanced Options and display the Tags tab. Then add tags by selecting a Tag Namespace, Tag Key, and Tag Value. Tagging is a metadata system that allows you to organize and track resources within your tenancy. See Tagging Dedicated Autonomous Database Cloud Resources.

7. Optionally, you can save the resource configuration as a stack by clicking Save as Stack. You can then use the stack to create the resource through the Resource Manager service.

   Enter the following details on the Save as Stack dialog, and click Save.

   • Name: Optionally, enter a name for the stack.
   • Description: Optionally, enter a description for this stack.
   • Save in compartment: Select a compartment where this Stack will reside.
   • Tag namespace, Tag key, and Tag value: Optionally, apply tags to the stack.

   For requirements and recommendations for Terraform configurations used with Resource Manager, see Terraform Configurations for Resource Manager. To provision the resources defined in your stack, apply the configuration.

8. Click Create Exadata Infrastructure.

The list of Exadata Infrastructure resources refreshes to show the new resource with a status of Provisioning until the new Exadata Infrastructure resource is available.