The name of the availability domain that the Autonomous Exadata Infrastructure is located in.
The OCID of the compartment.
Defined tags for this resource. Each key is predefined and scoped to a namespace. For more information, see Resource Tags.
The user-friendly name for the Autonomous Exadata Infrastructure.
The domain name for the Autonomous Exadata Infrastructure.
Free-form tags for this resource. Each tag is a simple key-value pair with no predefined name, type, or namespace. For more information, see Resource Tags.
Example: {@code {\"Department\": \"Finance\"}}
The host name for the Autonomous Exadata Infrastructure node.
The OCID of the Autonomous Exadata Infrastructure.
The OCID of the last maintenance run.
The Oracle license model that applies to all databases in the Autonomous Exadata Infrastructure. The default is BRING_YOUR_OWN_LICENSE.
Additional information about the current lifecycle state of the Autonomous Exadata Infrastructure.
The current lifecycle state of the Autonomous Exadata Infrastructure.
The OCID of the next maintenance run.
The list of OCIDs for the network security groups (NSGs) to which this resource belongs. Setting this to an empty list removes all resources from all NSGs. For more information about NSGs, see Security Rules. NsgIds restrictions:
The FQDN of the DNS record for the SCAN IP addresses that are associated with the Autonomous Exadata Infrastructure.
The shape of the Autonomous Exadata Infrastructure. The shape determines resources to allocate to the Autonomous Exadata Infrastructure (CPU cores, memory and storage).
The OCID of the subnet the Autonomous Exadata Infrastructure is associated with.
*Subnet Restrictions:** - For Autonomous Databases with Autonomous Exadata Infrastructure, do not use a subnet that overlaps with 192.168.128.0/20
These subnets are used by the Oracle Clusterware private interconnect on the database instance. Specifying an overlapping subnet will cause the private interconnect to malfunction. This restriction applies to both the client subnet and backup subnet.
The date and time the Autonomous Exadata Infrastructure was created.
The OCID of the zone the Autonomous Exadata Infrastructure is associated with.
Deprecated These APIs are deprecated with the introduction of the Autonomous Exadata VM Cluster resource and a shift to a common Exadata Infrastructure resource for all Exadata Cloud-based services, including Autonomous Database on dedicated Exadata infrastructure. For more details, see Latest Resource Model.
Infrastructure that enables the running of multiple Autonomous Databases within a dedicated DB system. For more information about Autonomous Exadata Infrastructure, see [Oracle Autonomous Database](https://docs.oracle.com/en/cloud/paas/autonomous-database/index.html).
To use any of the API operations, you must be authorized in an IAM policy. If you're not authorized, talk to an administrator. If you're an administrator who needs to write policies to give users access, see [Getting Started with Policies](https://docs.cloud.oracle.com/Content/Identity/Concepts/policygetstarted.htm).
For information about access control and compartments, see [Overview of the Identity Service](https://docs.cloud.oracle.com/Content/Identity/Concepts/overview.htm).
For information about availability domains, see [Regions and Availability Domains](https://docs.cloud.oracle.com/Content/General/Concepts/regions.htm).
To get a list of availability domains, use the ListAvailabilityDomains operation in the Identity service API.