Table: oci_database_cloud_vm_cluster - Query OCI Database Cloud VM cluster using SQL
Oracle Cloud Database services, which can be deployed on virtual machines (VMs). A Database Cloud VM Cluster in OCI refers to a specific configuration or deployment option for hosting Oracle databases within a virtualized environment.
Table Usage Guide
The oci_database_cloud_vm_cluster
table provides insights into Database Cloud VM cluster within Oracle Cloud Infrastructure Database service. As a database administrator or developer, explore specific details about these VM clusters, including their configurations, statuses, and associated metadata. Utilize this table to manage and monitor your databases, ensuring they are optimized, secure, and functioning as expected.
Examples
Basic info
Gain insights into the lifecycle state and creation time of your database cloud VM cluster to better understand their status and duration of existence. This is particularly useful for database management and auditing purposes.
select cluster_name, display_name, lifecycle_state, time_created, shapefrom oci_database_cloud_vm_cluster;
select cluster_name, display_name, lifecycle_state, time_created, shapefrom oci_database_cloud_vm_cluster;
List clusters that are not available
Discover the clusters that are currently not available. This can be useful to identify potential issues or disruptions in your cloud database services.
select cluster_name, display_name, lifecycle_state, time_created, availability_domainfrom oci_database_cloud_vm_clusterwhere lifecycle_state <> 'AVAILABLE';
select cluster_name, display_name, lifecycle_state, time_created, availability_domainfrom oci_database_cloud_vm_clusterwhere lifecycle_state <> 'AVAILABLE';
List VM clusters with core CPUs greater than 4
Identify databases with more than 4 core CPUs. This query is valuable because the number of core CPUs in a computer or server system depends on the specific tasks and processes it executes.
select cluster_name, display_name, lifecycle_state, time_created, availability_domain, subnet_id, shape, cpu_core_countfrom oci_database_cloud_vm_clusterwhere cpu_core_count > 4;
select cluster_name, display_name, lifecycle_state, time_created, availability_domain, subnet_id, shape, cpu_core_countfrom oci_database_cloud_vm_clusterwhere cpu_core_count > 4;
Get node details of clusters for cloud exadata infrastructures
Queries can assist in making scaling decisions. By analyzing the data from queries, you can determine whether you need to add more nodes to the cluster or remove underutilized nodes to optimize costs and performance.
select c.cluster_name, c.lifecycle_state as cluster_lifecycle_state, c.subnet_id, i.shape as infra_shape, i.cpus_enabled, i.storage_countfrom oci_database_cloud_vm_cluster as c, oci_database_exadata_infrastructure as iwhere c.cloud_exadata_infrastructure_id = i.id;
select c.cluster_name, c.lifecycle_state as cluster_lifecycle_state, c.subnet_id, i.shape as infra_shape, i.cpus_enabled, i.storage_countfrom oci_database_cloud_vm_cluster as c, oci_database_exadata_infrastructure as iwhere c.cloud_exadata_infrastructure_id = i.id;
Schema for oci_database_cloud_vm_cluster
Name | Type | Operators | Description |
---|---|---|---|
_ctx | jsonb | Steampipe context in JSON form. | |
availability_domain | text | The name of the availability domain that the cloud Exadata infrastructure resource is located in. | |
backup_network_nsg_ids | jsonb | A list of the OCIDs of the network security groups (NSGs) that the backup network of this DB system belongs to. | |
backup_subnet_id | text | The OCID of the backup network subnet associated with the cloud VM cluster. | |
cloud_exadata_infrastructure_id | text | = | The OCID of the cloud Exadata infrastructure. |
cluster_name | text | The cluster name for cloud VM cluster. | |
compartment_id | text | = | The OCID of the compartment in Tenant in which the resource is located. |
cpu_core_count | bigint | The number of CPU cores enabled on the cloud VM cluster. | |
data_collection_options | jsonb | The data collection options of the cloud VM cluster. | |
data_storage_percentage | bigint | The percentage assigned to DATA storage. | |
data_storage_size_in_tbs | double precision | The data disk group size to be allocated in TBs. | |
db_node_storage_size_in_gbs | bigint | The local node storage to be allocated in GBs. | |
db_servers | jsonb | The list of Db servers. | |
defined_tags | jsonb | Defined tags for this resource. | |
disk_redundancy | text | The type of redundancy configured for the cloud Vm cluster. | |
display_name | text | = | The user-friendly name for the cloud VM cluster. |
domain | text | The domain name for the cloud VM cluster. | |
freeform_tags | jsonb | Free-form tags for this resource. | |
gi_version | text | A valid Oracle Grid Infrastructure (GI) software version. | |
hostname | text | The hostname for the cloud VM cluster. | |
id | text | = | The OCID of the cloud VM cluster. |
iorm_config_cache | jsonb | The config cache details of the cloud VM cluster. | |
is_local_backup_enabled | boolean | If true, database backup on local Exadata storage is configured for the cloud VM cluster. | |
is_sparse_diskgroup_enabled | boolean | If true, sparse disk group is configured for the cloud VM cluster. If false, sparse disk group is not created. | |
last_update_history_entry_id | text | The OCID of the last maintenance update history entry. This value is updated when a maintenance update starts. | |
license_model | text | The Oracle license model that applies to the cloud VM cluster. The default is LICENSE_INCLUDED. | |
lifecycle_details | text | Additional information about the current lifecycle state. | |
lifecycle_state | text | = | The current state of the cloud VM cluster. |
listener_port | bigint | The port number configured for the listener on the cloud VM cluster. | |
memory_size_in_gbs | bigint | The memory to be allocated in GBs. | |
node_count | bigint | The number of nodes in the cloud VM cluster. | |
nsg_ids | jsonb | The list of OCIDs for the network security groups (NSGs) to which this resource belongs. | |
ocpu_count | double precision | The number of OCPU cores to enable on the cloud VM cluster. | |
region | text | The OCI region in which the resource is located. | |
scan_dns_name | text | The FQDN of the DNS record for the SCAN IP addresses associated with the cloud VM cluster. | |
scan_dns_record_id | text | The OCID of the DNS record for the SCAN IP addresses associated with the cloud VM cluster. | |
scan_ip_ids | jsonb | The OCID of the Single Client Access Name (SCAN) IP addresses associated with the cloud VM cluster. | |
scan_listener_port_tcp | bigint | The TCP Single Client Access Name (SCAN) port. The default port is 1521. | |
scan_listener_port_tcp_ssl | bigint | The TCPS Single Client Access Name (SCAN) port. The default port is 2484. | |
shape | text | The model name of the Exadata hardware running the cloud VM cluster. | |
sp_connection_name | text | =, !=, ~~, ~~*, !~~, !~~* | Steampipe connection name. |
sp_ctx | jsonb | Steampipe context in JSON form. | |
ssh_public_keys | jsonb | The public key portion of one or more key pairs used for SSH access to the cloud VM cluster. | |
storage_size_in_gbs | bigint | The storage allocation for the disk group, in gigabytes (GB). | |
subnet_id | text | The OCID of the subnet associated with the cloud VM cluster. | |
system_version | text | Operating system version of the image. | |
tags | jsonb | A map of tags for the resource. | |
tenant_id | text | =, !=, ~~, ~~*, !~~, !~~* | The OCID of the Tenant in which the resource is located. |
tenant_name | text | The name of the Tenant in which the resource is located. | |
time_created | timestamp with time zone | The date and time that the cloud VM cluster was created. | |
time_zone | text | The time zone of the cloud VM cluster. | |
title | text | Title of the resource. | |
vip_ids | jsonb | The OCID of the virtual IP (VIP) addresses associated with the cloud VM cluster. | |
zone_id | text | The OCID of the zone the cloud VM cluster is associated with. |
Export
This table is available as a standalone Exporter CLI. Steampipe exporters are stand-alone binaries that allow you to extract data using Steampipe plugins without a database.
You can download the tarball for your platform from the Releases page, but it is simplest to install them with the steampipe_export_installer.sh
script:
/bin/sh -c "$(curl -fsSL https://steampipe.io/install/export.sh)" -- oci
You can pass the configuration to the command with the --config
argument:
steampipe_export_oci --config '<your_config>' oci_database_cloud_vm_cluster