The name of the availability domain that the cloud Exadata infrastructure resource is located in.
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 cloud VM cluster.
*Subnet Restriction:** See the subnet restrictions information for **subnetId**.
The OCID of the cloud Exadata infrastructure.
The cluster name for cloud VM cluster. 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.
The number of CPU cores enabled on the cloud VM cluster. Note: Numbers greater than Number.MAX_SAFE_INTEGER will result in rounding issues.
The percentage assigned to DATA storage (user data and database files). The remaining percentage is assigned to RECO storage (database redo logs, archive logs, and recovery manager backups). Accepted values are 35, 40, 60 and 80. The default is 80 percent assigned to DATA storage. See Storage Configuration in the Exadata documentation for details on the impact of the configuration settings on storage. Note: Numbers greater than Number.MAX_SAFE_INTEGER will result in rounding issues.
The data disk group size to be allocated in TBs. Note: Numbers greater than Number.MAX_SAFE_INTEGER will result in rounding issues.
The local node storage to be allocated in GBs. Note: Numbers greater than Number.MAX_SAFE_INTEGER will result in rounding issues.
The list of DB servers.
Defined tags for this resource. Each key is predefined and scoped to a namespace. For more information, see Resource Tags.
The type of redundancy configured for the cloud Vm cluster. NORMAL is 2-way redundancy. HIGH is 3-way redundancy.
The user-friendly name for the cloud VM cluster. The name does not need to be unique.
The domain name for the cloud VM cluster.
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 OCID of a grid infrastructure software image. This is a database software image of the type {@code GRID_IMAGE}.
A valid Oracle Grid Infrastructure (GI) software version.
The hostname for the cloud VM cluster.
The OCID of the cloud VM cluster.
If true, database backup on local Exadata storage is configured for the cloud VM cluster. If false, database backup on local Exadata storage is not available in the cloud VM cluster.
If true, sparse disk group is configured for the cloud VM cluster. If false, sparse disk group is not created.
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 cloud VM cluster. The default is LICENSE_INCLUDED.
Additional information about the current lifecycle state.
The current state of the cloud VM cluster.
The port number configured for the listener on the cloud VM cluster. Note: Numbers greater than Number.MAX_SAFE_INTEGER will result in rounding issues.
The memory to be allocated in GBs. Note: Numbers greater than Number.MAX_SAFE_INTEGER will result in rounding issues.
The number of nodes in the cloud VM cluster. 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 number of OCPU cores to enable on the cloud VM cluster. Only 1 decimal place is allowed for the fractional part. Note: Numbers greater than Number.MAX_SAFE_INTEGER will result in rounding issues.
The FQDN of the DNS record for the SCAN IP addresses that are associated with the cloud VM cluster.
The OCID of the DNS record for the SCAN IP addresses that are associated with the cloud VM cluster.
The OCID of the Single Client Access Name (SCAN) IP addresses associated with the cloud VM cluster. 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 TCPS 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 model name of the Exadata hardware running the cloud VM cluster.
The public key portion of one or more key pairs used for SSH access to the cloud VM cluster.
The storage allocation for the disk group, in gigabytes (GB). Note: Numbers greater than Number.MAX_SAFE_INTEGER will result in rounding issues.
The OCID of the subnet associated with the cloud VM cluster.
*Subnet Restrictions:** - For Exadata and virtual machine 2-node RAC systems, 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.
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 cloud VM cluster was created.
The time zone of the cloud VM cluster. For details, see Exadata Infrastructure Time Zones.
The OCID of the virtual IP (VIP) addresses associated with the cloud VM cluster. 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, the VIP is reassigned to another active node in the cluster.
*Note:** For a single-node DB system, this list is empty.
The OCID of the zone the cloud VM cluster is associated with.
Details of the cloud VM cluster. Applies to Exadata Cloud Service instances only.