The name of the availability domain in which the Exadata VM cluster on Exascale Infrastructure is located.
A list of the OCIDs of the network security groups (NSGs) that the backup network of this DB system belongs to. Setting this to an empty array after the list is created removes the resource from all NSGs. For more information about NSGs, see Security Rules. Applicable only to Exadata systems.
The OCID of the backup network subnet associated with the Exadata VM cluster on Exascale Infrastructure.
The cluster name for Exadata VM cluster on Exascale Infrastructure. The cluster name must begin with an alphabetic character, and may contain hyphens (-). Underscores (_) are not permitted. The cluster name can be no longer than 11 characters and is not case sensitive.
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 Exadata VM cluster on Exascale Infrastructure. The name does not need to be unique.
A domain name used for the Exadata VM cluster on Exascale Infrastructure. If the Oracle-provided internet and VCN resolver is enabled for the specified subnet, then the domain name for the subnet is used (do not provide one). Otherwise, provide a valid DNS domain name. Hyphens (-) are not permitted. Applies to Exadata Database Service on Exascale Infrastructure only.
The number of ECPUs to enable for an Exadata VM cluster on Exascale Infrastructure. Note: Numbers greater than Number.MAX_SAFE_INTEGER will result in rounding issues.
The OCID of the Exadata Database Storage Vault.
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\"}}
A valid Oracle Grid Infrastructure (GI) software version.
Grid Setup will be done using this grid image id
The type of Grid Image
The hostname for the Exadata VM cluster on Exascale Infrastructure. The hostname must begin with an alphabetic character, and can contain alphanumeric characters and hyphens (-). For Exadata systems, the maximum length of the hostname is 12 characters.
The maximum length of the combined hostname and domain is 63 characters.
*Note:** The hostname must be unique within the subnet. If it is not unique, then the Exadata VM cluster on Exascale Infrastructure will fail to provision.
The OCID of the Exadata VM cluster on Exascale Infrastructure.
The OCID of the last maintenance update history entry. This value is updated when a maintenance update starts.
The Oracle license model that applies to the Exadata VM cluster on Exascale Infrastructure. The default is BRING_YOUR_OWN_LICENSE.
Additional information about the current lifecycle state.
The current state of the Exadata VM cluster on Exascale Infrastructure.
The port number configured for the listener on the Exadata VM cluster on Exascale Infrastructure. Note: Numbers greater than Number.MAX_SAFE_INTEGER will result in rounding issues.
The memory that you want to be allocated in GBs. Memory is calculated based on 11 GB per VM core reserved. Note: Numbers greater than Number.MAX_SAFE_INTEGER will result in rounding issues.
The number of nodes in the Exadata VM cluster on Exascale Infrastructure. Note: Numbers greater than Number.MAX_SAFE_INTEGER will result in rounding issues.
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 private zone ID in which you want DNS records to be created.
The FQDN of the DNS record for the SCAN IP addresses that are associated with the Exadata VM cluster on Exascale Infrastructure.
The OCID of the DNS record for the SCAN IP addresses that are associated with the Exadata VM cluster on Exascale Infrastructure.
The OCID of the Single Client Access Name (SCAN) IP addresses associated with the Exadata VM cluster on Exascale Infrastructure. SCAN IP addresses are typically used for load balancing and are not assigned to any interface. Oracle Clusterware directs the requests to the appropriate nodes in the cluster.
*Note:** For a single-node DB system, this list is empty.
The TCP Single Client Access Name (SCAN) port. The default port is 1521. Note: Numbers greater than Number.MAX_SAFE_INTEGER will result in rounding issues.
The Secured Communication (TCPS) protocol Single Client Access Name (SCAN) port. The default port is 2484. Note: Numbers greater than Number.MAX_SAFE_INTEGER will result in rounding issues.
The shape of the Exadata VM cluster on Exascale Infrastructure resource
The public key portion of one or more key pairs used for SSH access to the Exadata VM cluster on Exascale Infrastructure.
The OCID of the subnet associated with the Exadata VM cluster on Exascale Infrastructure.
System tags for this resource. Each key is predefined and scoped to a namespace. For more information, see Resource Tags.
Operating system version of the image.
The date and time that the Exadata VM cluster on Exascale Infrastructure was created.
The time zone to use for the Exadata VM cluster on Exascale Infrastructure. For details, see Time Zones.
The number of Total ECPUs for an Exadata VM cluster on Exascale Infrastructure. Note: Numbers greater than Number.MAX_SAFE_INTEGER will result in rounding issues.
The OCID of the virtual IP (VIP) addresses associated with the Exadata VM cluster on Exascale Infrastructure. The Cluster Ready Services (CRS) creates and maintains one VIP address for each node in the Exadata Cloud Service instance to enable failover. If one node fails, then the VIP is reassigned to another active node in the cluster.
The OCID of the zone with which the Exadata VM cluster on Exascale Infrastructure is associated.
Details of the Exadata VM cluster on Exascale Infrastructure. Applies to Exadata Database Service on Exascale Infrastructure only.