Data Source: oci_database_autonomous_exadata_infrastructure
This data source provides details about a specific Autonomous Exadata Infrastructure resource in Oracle Cloud Infrastructure Database service.
Deprecated. Use the GetCloudExadataInfrastructure operation to get details of an Exadata Infrastructure resource and the GetCloudAutonomousVmCluster operation to get details of an Autonomous Exadata VM cluster.
Example Usage
data "oci_database_autonomous_exadata_infrastructure" "test_autonomous_exadata_infrastructure" {
#Required
autonomous_exadata_infrastructure_id = oci_database_autonomous_exadata_infrastructure.test_autonomous_exadata_infrastructure.id
}
Argument Reference
The following arguments are supported:
autonomous_exadata_infrastructure_id- (Required) The Autonomous Exadata Infrastructure OCID.
Attributes Reference
The following attributes are exported:
availability_domain- The name of the availability domain that the Autonomous Exadata Infrastructure is located in.compartment_id- The OCID of the compartment.defined_tags- Defined tags for this resource. Each key is predefined and scoped to a namespace. For more information, see Resource Tags.display_name- The user-friendly name for the Autonomous Exadata Infrastructure.domain- The domain name for the Autonomous Exadata Infrastructure.freeform_tags- 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:{"Department": "Finance"}hostname- The host name for the Autonomous Exadata Infrastructure node.id- The OCID of the Autonomous Exadata Infrastructure.last_maintenance_run_id- The OCID of the last maintenance run.license_model- The Oracle license model that applies to all databases in the Autonomous Exadata Infrastructure. The default is BRING_YOUR_OWN_LICENSE.lifecycle_details- Additional information about the current lifecycle state of the Autonomous Exadata Infrastructure.maintenance_window- The scheduling details for the quarterly maintenance window. Patching and system updates take place during the maintenance window.custom_action_timeout_in_mins- Determines the amount of time the system will wait before the start of each database server patching operation. Custom action timeout is in minutes and valid value is between 15 to 120 (inclusive).days_of_week- Days during the week when maintenance should be performed.name- Name of the day of the week.
hours_of_day- The window of hours during the day when maintenance should be performed. The window is a 4 hour slot. Valid values are- 0 - represents time slot 0:00 - 3:59 UTC - 4 - represents time slot 4:00 - 7:59 UTC - 8 - represents time slot 8:00 - 11:59 UTC - 12 - represents time slot 12:00 - 15:59 UTC - 16 - represents time slot 16:00 - 19:59 UTC - 20 - represents time slot 20:00 - 23:59 UTC
is_custom_action_timeout_enabled- If true, enables the configuration of a custom action timeout (waiting period) between database server patching operations.is_monthly_patching_enabled- If true, enables the monthly patching option.lead_time_in_weeks- Lead time window allows user to set a lead time to prepare for a down time. The lead time is in weeks and valid value is between 1 to 4.months- Months during the year when maintenance should be performed.name- Name of the month of the year.
patching_mode- Cloud Exadata infrastructure node patching method, either “ROLLING” or “NONROLLING”. Default value is ROLLING.IMPORTANT: Non-rolling infrastructure patching involves system down time. See Oracle-Managed Infrastructure Maintenance Updates for more information.
preference- The maintenance window scheduling preference.skip_ru- If true, skips the release update (RU) for the quarter. You cannot skip two consecutive quarters. An RU skip request will only be honoured if the current version of the Autonomous Container Database is supported for current quarter.weeks_of_month- Weeks during the month when maintenance should be performed. 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. Note that this parameter works in conjunction with the daysOfWeek and hoursOfDay parameters to allow you to specify specific days of the week and hours that maintenance will be performed.
next_maintenance_run_id- The OCID of the next maintenance run.nsg_ids- 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:- A network security group (NSG) is optional for Autonomous Databases with private access. The nsgIds list can be empty.
scan_dns_name- The FQDN of the DNS record for the SCAN IP addresses that are associated with the Autonomous Exadata Infrastructure.shape- The shape of the Autonomous Exadata Infrastructure. The shape determines resources to allocate to the Autonomous Exadata Infrastructure (CPU cores, memory and storage).state- The current lifecycle state of the Autonomous Exadata Infrastructure.subnet_id- 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.
time_created- The date and time the Autonomous Exadata Infrastructure was created.zone_id- The OCID of the zone the Autonomous Exadata Infrastructure is associated with.