Skip to main content

autonomous_exadata_infrastructures

Creates, updates, deletes, gets or lists an autonomous_exadata_infrastructures resource.

Overview​

Nameautonomous_exadata_infrastructures
TypeResource
Idoci.database.autonomous_exadata_infrastructures

Fields​

The following fields are returned by SELECT queries:

The Autonomous Exadata Infrastructure details.

NameDatatypeDescription
idstringThe OCID of the Autonomous Exadata Infrastructure.
availabilityDomainstringThe name of the availability domain that the Autonomous Exadata Infrastructure is located in.
compartmentIdstringThe OCID of the compartment.
definedTagsobjectDefined tags for this resource. Each key is predefined and scoped to a namespace. For more information, see [Resource Tags](/Content/General/Concepts/resourcetags.htm).
displayNamestringThe user-friendly name for the Autonomous Exadata Infrastructure.
domainstringThe domain name for the Autonomous Exadata Infrastructure.
freeformTagsobjectFree-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](/Content/General/Concepts/resourcetags.htm). Example: {"Department": "Finance"}
hostnamestringThe host name for the Autonomous Exadata Infrastructure node.
lastMaintenanceRunIdstringThe [OCID](/Content/General/Concepts/identifiers.htm) of the last maintenance run.
licenseModelstringThe Oracle license model that applies to all databases in the Autonomous Exadata Infrastructure. The default is BRING_YOUR_OWN_LICENSE. (LICENSE_INCLUDED, BRING_YOUR_OWN_LICENSE)
lifecycleDetailsstringAdditional information about the current lifecycle state of the Autonomous Exadata Infrastructure.
lifecycleStatestringThe current lifecycle state of the Autonomous Exadata Infrastructure. (PROVISIONING, AVAILABLE, UPDATING, TERMINATING, TERMINATED, FAILED, MAINTENANCE_IN_PROGRESS)
maintenanceWindowobjectThe scheduling details for the quarterly maintenance window. Patching and system updates take place during the maintenance window.
nextMaintenanceRunIdstringThe [OCID](/Content/General/Concepts/identifiers.htm) of the next maintenance run.
nsgIdsarrayThe list of [OCIDs](/Content/General/Concepts/identifiers.htm) 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](/Content/Network/Concepts/securityrules.htm).
scanDnsNamestringThe FQDN of the DNS record for the SCAN IP addresses that are associated with the Autonomous Exadata Infrastructure.
shapestringThe shape of the Autonomous Exadata Infrastructure. The shape determines resources to allocate to the Autonomous Exadata Infrastructure (CPU cores, memory and storage).
subnetIdstringThe OCID of the subnet the Autonomous Exadata Infrastructure is associated with. Subnet Restrictions: - For Autonomous AI 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.
timeCreatedstring (date-time)The date and time the Autonomous Exadata Infrastructure was created.
zoneIdstringThe OCID of the zone the Autonomous Exadata Infrastructure is associated with.

Methods​

The following methods are available for this resource:

NameAccessible byRequired ParamsOptional ParamsDescription
getselectautonomousExadataInfrastructureId, regionDeprecated. Use the [GetCloudExadataInfrastructure](#/en/database/latest/CloudExadataInfrastructure/GetCloudExadataInfrastructure) operation to get details of an Exadata Infrastructure resource and the [GetCloudAutonomousVmCluster](#/en/database/latest/CloudAutonomousVmCluster/GetCloudAutonomousVmCluster) operation to get details of an Autonomous Exadata VM cluster.<br />
listselectcompartmentId, regionlimit, page, sortBy, sortOrder, lifecycleState, availabilityDomain, displayNameDeprecated. Use the [ListCloudExadataInfrastructures](#/en/database/latest/CloudExadataInfrastructure/ListCloudExadataInfrastructures) operation to list Exadata Infrastructures in the Oracle cloud and the [ListCloudAutonomousVmClusters](#/en/database/latest/CloudAutonomousVmCluster/ListCloudAutonomousVmClusters) operation to list Autonomous Exadata VM clusters.<br />
launchinsertregion, compartmentId, availabilityDomain, subnetId, shapeopc-retry-tokenDeprecated To create a new Autonomous AI Database system on dedicated Exadata Infrastructure, use the [CreateCloudExadataInfrastructure](#/en/database/latest/CloudExadataInfrastructure/CreateCloudExadataInfrastructure) and [CreateCloudAutonomousVmCluster](#/en/database/latest/CloudAutonomousVmCluster/CreateCloudAutonomousVmCluster) operations instead. Note that to create an Autonomous VM cluster, you must have an existing Exadata Infrastructure resource to contain the VM cluster.<br />
updateupdateautonomousExadataInfrastructureId, regionif-matchDeprecated. Use the [UpdateCloudExadataInfrastructure](#/en/database/latest/CloudExadataInfrastructure/UpdateCloudExadataInfrastructure) operation to update an Exadata Infrastructure resource and [UpdateCloudAutonomousVmCluster](#/en/database/latest/CloudAutonomousVmCluster/UpdateCloudAutonomousVmCluster) operation to update an Autonomous Exadata VM cluster.<br />
terminatedeleteautonomousExadataInfrastructureId, regionif-matchDeprecated. To terminate an Exadata Infrastructure resource in the Oracle cloud, use the [DeleteCloudExadataInfrastructure](#/en/database/latest/CloudExadataInfrastructure/DeleteCloudExadataInfrastructure) operation. To delete an Autonomous Exadata VM cluster in the Oracle cloud, use the [DeleteCloudAutonomousVmCluster](#/en/database/latest/CloudAutonomousVmCluster/DeleteCloudAutonomousVmCluster) operation.<br />
change_compartmentexecautonomousExadataInfrastructureId, region, compartmentIdopc-retry-token, opc-request-id, if-matchDeprecated. Use the [ChangeCloudExadataInfrastructureCompartment](#/en/database/latest/CloudExadataInfrastructure/ChangeCloudExadataInfrastructureCompartment) operation to move an Exadata infrastructure resource to a different compartment and [ChangeCloudAutonomousVmClusterCompartment](#/en/database/latest/CloudAutonomousVmCluster/ChangeCloudAutonomousVmClusterCompartment) operation to move an Autonomous Exadata VM cluster to a different compartment.<br />For more information, see<br />[Moving Database Resources to a Different Compartment](/Content/Database/Concepts/databaseoverview.htm#moveRes).<br />
rotate_ords_certsexecautonomousExadataInfrastructureId, regionopc-request-id, opc-retry-token, if-matchDeprecated. Use the [RotateCloudAutonomousVmClusterOrdsCerts](#/en/database/latest/CloudAutonomousVmCluster/RotateCloudAutonomousVmClusterOrdsCerts) to rotate Oracle REST Data Services (ORDS) certs for an Autonomous Exadata VM cluster instead.<br />
rotate_ssl_certsexecautonomousExadataInfrastructureId, regionopc-request-id, opc-retry-token, if-matchDeprecated. Use the [RotateCloudAutonomousVmClusterSslCerts](#/en/database/latest/CloudAutonomousVmCluster/RotateCloudAutonomousVmClusterSslCerts) to rotate SSL certs for an Autonomous Exadata VM cluster instead.<br />

Parameters​

Parameters can be passed in the WHERE clause of a query. Check the Methods section to see which parameters are required or optional for each operation.

NameDatatypeDescription
autonomousExadataInfrastructureIdstringThe Autonomous Exadata Infrastructure [OCID](/Content/General/Concepts/identifiers.htm).
compartmentIdstringThe compartment [OCID](/Content/General/Concepts/identifiers.htm).
regionstringOCI region identifier (e.g. us-ashburn-1, ap-sydney-1); resolves from OCI_REGION when not supplied in the query. (default: us-ashburn-1, x-stackQL-envVar: OCI_REGION)
availabilityDomainstringA filter to return only resources that match the given availability domain exactly.
displayNamestringA filter to return only resources that match the entire display name given. The match is not case sensitive.
if-matchstringFor optimistic concurrency control. In the PUT or DELETE call for a resource, set the if-match parameter to the value of the etag from a previous GET or POST response for that resource. The resource will be updated or deleted only if the etag you provide matches the resource's current etag value.
lifecycleStatestringA filter to return only resources that match the given lifecycle state exactly.
limitintegerThe maximum number of items to return per page.
opc-request-idstringUnique identifier for the request.
opc-retry-tokenstringA token that uniquely identifies a request so it can be retried in case of a timeout or server error without risk of executing that same action again. Retry tokens expire after 24 hours, but can be invalidated before then due to conflicting operations (for example, if a resource has been deleted and purged from the system, then a retry of the original creation request may be rejected).
pagestringThe pagination token to continue listing from.
sortBystringThe field to sort by. You can provide one sort order (sortOrder). Default order for TIMECREATED is descending. Default order for DISPLAYNAME is ascending. The DISPLAYNAME sort order is case sensitive. Note: If you do not include the availability domain filter, the resources are grouped by availability domain, then sorted.
sortOrderstringThe sort order to use, either ascending (ASC) or descending (DESC).

SELECT examples​

Deprecated. Use the [GetCloudExadataInfrastructure](#/en/database/latest/CloudExadataInfrastructure/GetCloudExadataInfrastructure) operation to get details of an Exadata Infrastructure resource and the [GetCloudAutonomousVmCluster](#/en/database/latest/CloudAutonomousVmCluster/GetCloudAutonomousVmCluster) operation to get details of an Autonomous Exadata VM cluster.<br />

SELECT
id,
availabilityDomain,
compartmentId,
definedTags,
displayName,
domain,
freeformTags,
hostname,
lastMaintenanceRunId,
licenseModel,
lifecycleDetails,
lifecycleState,
maintenanceWindow,
nextMaintenanceRunId,
nsgIds,
scanDnsName,
shape,
subnetId,
timeCreated,
zoneId
FROM oci.database.autonomous_exadata_infrastructures
WHERE autonomousExadataInfrastructureId = '{{ autonomousExadataInfrastructureId }}' -- required
AND region = '{{ region }}' -- required
;

INSERT examples​

Deprecated To create a new Autonomous AI Database system on dedicated Exadata Infrastructure, use the [CreateCloudExadataInfrastructure](#/en/database/latest/CloudExadataInfrastructure/CreateCloudExadataInfrastructure) and [CreateCloudAutonomousVmCluster](#/en/database/latest/CloudAutonomousVmCluster/CreateCloudAutonomousVmCluster) operations instead. Note that to create an Autonomous VM cluster, you must have an existing Exadata Infrastructure resource to contain the VM cluster.<br />

INSERT INTO oci.database.autonomous_exadata_infrastructures (
availabilityDomain,
compartmentId,
definedTags,
displayName,
domain,
freeformTags,
licenseModel,
maintenanceWindowDetails,
nsgIds,
shape,
subnetId,
region,
opc-retry-token
)
SELECT 
'{{ availabilityDomain }}' /* required */,
'{{ compartmentId }}' /* required */,
'{{ definedTags }}',
'{{ displayName }}',
'{{ domain }}',
'{{ freeformTags }}',
'{{ licenseModel }}',
'{{ maintenanceWindowDetails }}',
'{{ nsgIds }}',
'{{ shape }}' /* required */,
'{{ subnetId }}' /* required */,
'{{ region }}',
'{{ opc-retry-token }}'
RETURNING
id,
availabilityDomain,
compartmentId,
definedTags,
displayName,
domain,
freeformTags,
hostname,
lastMaintenanceRunId,
licenseModel,
lifecycleDetails,
lifecycleState,
maintenanceWindow,
nextMaintenanceRunId,
nsgIds,
scanDnsName,
shape,
subnetId,
timeCreated,
zoneId
;

UPDATE examples​

Deprecated. Use the [UpdateCloudExadataInfrastructure](#/en/database/latest/CloudExadataInfrastructure/UpdateCloudExadataInfrastructure) operation to update an Exadata Infrastructure resource and [UpdateCloudAutonomousVmCluster](#/en/database/latest/CloudAutonomousVmCluster/UpdateCloudAutonomousVmCluster) operation to update an Autonomous Exadata VM cluster.<br />

UPDATE oci.database.autonomous_exadata_infrastructures
SET 
definedTags = '{{ definedTags }}',
displayName = '{{ displayName }}',
freeformTags = '{{ freeformTags }}',
maintenanceWindowDetails = '{{ maintenanceWindowDetails }}',
nsgIds = '{{ nsgIds }}'
WHERE 
autonomousExadataInfrastructureId = '{{ autonomousExadataInfrastructureId }}' --required
AND region = '{{ region }}' --required
AND if-match = '{{ if-match}}'
RETURNING
id,
availabilityDomain,
compartmentId,
definedTags,
displayName,
domain,
freeformTags,
hostname,
lastMaintenanceRunId,
licenseModel,
lifecycleDetails,
lifecycleState,
maintenanceWindow,
nextMaintenanceRunId,
nsgIds,
scanDnsName,
shape,
subnetId,
timeCreated,
zoneId;

DELETE examples​

Deprecated. To terminate an Exadata Infrastructure resource in the Oracle cloud, use the [DeleteCloudExadataInfrastructure](#/en/database/latest/CloudExadataInfrastructure/DeleteCloudExadataInfrastructure) operation. To delete an Autonomous Exadata VM cluster in the Oracle cloud, use the [DeleteCloudAutonomousVmCluster](#/en/database/latest/CloudAutonomousVmCluster/DeleteCloudAutonomousVmCluster) operation.<br />

DELETE FROM oci.database.autonomous_exadata_infrastructures
WHERE autonomousExadataInfrastructureId = '{{ autonomousExadataInfrastructureId }}' --required
AND region = '{{ region }}' --required
AND if-match = '{{ if-match }}'
;

Lifecycle Methods​

Deprecated. Use the [ChangeCloudExadataInfrastructureCompartment](#/en/database/latest/CloudExadataInfrastructure/ChangeCloudExadataInfrastructureCompartment) operation to move an Exadata infrastructure resource to a different compartment and [ChangeCloudAutonomousVmClusterCompartment](#/en/database/latest/CloudAutonomousVmCluster/ChangeCloudAutonomousVmClusterCompartment) operation to move an Autonomous Exadata VM cluster to a different compartment.<br />For more information, see<br />[Moving Database Resources to a Different Compartment](/Content/Database/Concepts/databaseoverview.htm#moveRes).<br />

EXEC oci.database.autonomous_exadata_infrastructures.change_compartment 
@autonomousExadataInfrastructureId='{{ autonomousExadataInfrastructureId }}' --required, 
@region='{{ region }}' --required, 
@opc-retry-token='{{ opc-retry-token }}', 
@opc-request-id='{{ opc-request-id }}', 
@if-match='{{ if-match }}' 
@@json=
'{
"compartmentId": "{{ compartmentId }}"
}'
;