About Exadata Infrastructure

The Exadata Infrastructure (EI) resource represents the Exadata Database Machine system, together with the networking configuration that connects it to Oracle Cloud. It hosts the underlying components Autonomous VM Clusters, Autonomous Container Databases, and Autonomous Databases.

EI is one of the four components of the four-level database architecture model, which is the foundation for an Autonomous Database on Dedicated Exadata Infrastructure.

To get a holistic idea of the four layer architecture used with Autonomous Database on Dedicated Exadata Infrastructure and understand Exadata Infrastructure's positioning in this architecture, refer to Components of Autonomous Database on Dedicated Exadata Infrastructure

EI is created by Fleet Administrators. See User Roles Associated with Autonomous Database on Dedicated Exadata Infrastructure to learn more.

The fleet administrator must first create an EI resource to host the Autonomous Database resources following the instructions in Create an Exadata Infrastructure Resource. Depending on the platform that you are deploying on, the following pages can be helpful in deciding the EI attributes such as the Infrastructure shape and capacity.

Note

You can skip creating a new EI resource if you are an existing customer for Oracle Exadata Database Service on Dedicated Infrastructure or Oracle Exadata Database Service on Cloud@Customer and already provisioned an EI resource. You can deploy both Autonomous Database and Exadata Database Service on the same EI.

Exadata Infrastructure resources emit events, which are structured messages that indicate changes in resources. Refer to Cloud Exadata Infrastructure Event Types for a list of event types that Exadata Infrastructure instances emit on Oracle Public Cloud and Exadata Infrastructure Event Types for listings of the operations that generate events for Autonomous Database on Exadata Cloud@Customer.

Exadata Infrastructure Requirements

IAM Policy Requirements

You must have an Oracle Cloud Infrastructure account with privileges granted through required IAM Policies. The required policies depend on the operation you are performing. For a list of IAM policies pertaining to Exadata Infrastructure, see Policies to Manage Exadata Infrastructure Resources.

Minimum Resource Requirements

Ensure your service limits show at least one supported Exadata system shape available. Before attempting to create the infrastructure resources, request a service limit increase if necessary. See Request Service Limit Increase for guidance.

Note

You need to have sufficient remaining resources on the EI to support the creation of at least one Autonomous Exadata VM Cluster.

Database Features Managed from Exadata Infrastructure

The following features of Autonomous Database can be defined and managed at the Exadata Infrastructure (EI) level.

Feature Notes Further Reference

Region and Availability Domain

When you create an EI resource, you must select a region and availability domain. A region is a localized geographic area, and an availability domain is one or more data centers located within a region. A region is composed of one or more availability domains.

Regions are grouped into realms. Your tenancy exists in a single realm and can access all regions that belong to that realm. You cannot access regions that are not in your realm.

Ensure that you select the most appropriate region for your EI as it cannot be changed later.

Regions and Availability Domains

Exadata System Model and Shape

Exadata Infrastructure can be provisioned on different Exadata System models. Each model comes in different shapes equipped with a fixed amount of memory, storage, and network resources.

The total resources allocated to your Autonomous Database on Dedicated Exadata Infrastructure is determined by the Exadata System (and shape) used to provision your service.

The available Exadata System Shapes depends on your choice of Exadata System model.

Exadata System Shapes

Characteristics of Infrastructure Shapes

Compute and Storage Configuration

You can specify the number of database and storage servers for configuring your EI 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.
  • 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. 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.
 

Maintenance Schedule

In general, Oracle schedules and performs entire fleet maintenance spread throughout each quarter and monthly infrastructure security fixes for vulnerabilities with CVSS scores greater than or equal to 7.

You can let Oracle handle maintenance scheduling, or you can set a specific maintenance window when Oracle can begin maintenance operations.

You can define or modify the maintenance schedule settings for an EI to be managed by Oracle or you can set a custom maintenance schedule.

Settings in Maintenance Schedule that are Customizable

Management Operations on a Scheduled Maintenance

Exadata Infrastructure Management Operations

You can perform the following management operations on an Exadata Infrastructure.

Operation Task Instructions
Create an Exadata Infrastructure Resource Create an Exadata Infrastructure Resource
Change the Maintenance Schedule of an Exadata Infrastructure Resource Change the Maintenance Schedule of an Exadata Infrastructure Resource
Move an Exadata Infrastructure Resource to a Different Compartment Move an Exadata Infrastructure Resource to a Different Compartment
View Details of an Exadata Infrastructure Resource View Details of an Exadata Infrastructure Resource
View a List of Exadata Infrastructure Resources View a List of Exadata Infrastructure Resources
View and Manage Scheduled Maintenance of an Exadata Infrastructure Resource View and Manage Scheduled Maintenance of an Exadata Infrastructure Resource
View Past Maintenance of an Exadata Infrastructure Resource View Past Maintenance of an Exadata Infrastructure Resource
Terminate an Exadata Infrastructure Resource Terminate an Exadata Infrastructure Resource

The above listed operations can also be achieved using API. See API to Manage Exadata Infrastructure Resources for further reference.