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 AI Databases.
EI is one of the four components of the four-level database architecture model, which is the foundation for an Autonomous AI Database on Dedicated Exadata Infrastructure.
To get a holistic idea of the four layer architecture used with Autonomous AI Database on Dedicated Exadata Infrastructure and understand Exadata Infrastructure’s positioning in this architecture, refer to Components of Autonomous AI Database on Dedicated Exadata Infrastructure.
EI is created by Fleet Administrators. See User Roles Associated with Autonomous AI Database on Dedicated Exadata Infrastructure to learn more.
The fleet administrator must first create an EI resource to host the Autonomous AI 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.
-
Deploying on Oracle Public Cloud:
-
Deploying on Exadata Cloud@Customer:
-
Deploying on Multicloud:
Note:
Exadata Infrastructure (EI) resources are created and managed through Exadata Database Service. The same EI resource on Dedicated Infrastructure or Exadata Cloud@Customer can host both Autonomous Exadata VM Clusters and Exadata VM Clusters. If an EI resource is already provisioned for Exadata Database Service and has sufficient capacity for Autonomous AI Database resources, you do not need to create an additional EI resource.
Some links in this section point to the corresponding Exadata Database Service documentation for Exadata Database Service on Dedicated Infrastructure and Exadata Cloud@Customer deployments.
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 AI Database on Exadata Cloud@Customer.
Exadata Infrastructure Requirements
Note: Depending on your Cloud Service Provider, see the following prerequisites for deployments:
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 AI 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 AI 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. |
|
Compute and Storage Configuration You can specify the number of database and storage servers for configuring your EI resource. |
|
|
Maintenance Schedule In general, Oracle schedules and performs entire fleet maintenance spread throughout each quarter and monthly infrastructure security fixes for vulnerabilities across all CVSS scores. 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. | |
Contact Email You can provide contact emails where you can receive operational notifications, announcements, and unplanned maintenance notifications regarding your Exadata Infrastructure. |
Oracle recommends using the email address of an administrator group rather than an individual’s, whenever possible, to ensure no important notifications or announcements are missed. |
Exadata Infrastructure Management Operations
You can perform the following management operations on an Exadata Infrastructure.
The above listed operations can also be achieved using API. See API to Manage Exadata Infrastructure Resources for further reference.