Table: oci_database_exadata_infrastructure - Query OCI Database Exadata Infrastructures using SQL
A Database Exadata Infrastructure is a specialized Oracle cloud service that provides high-performance and highly available database infrastructure for running Oracle Databases. Exadata Infrastructure is designed to deliver superior database performance and scalability by leveraging Oracle Exadata technology, which is optimized for Oracle Database workloads.
Table Usage Guide
The oci_database_exadata_infrastructure
table provides insights into Database Exadata Infrastructure within Oracle Cloud Infrastructure Database service. As a database administrator, you can explore specific details about each Exadata Infrastructure through this table, including its configuration, status, and associated metadata. Utilize it to uncover information about infrastructures, such as their database performance, making them suitable for demanding workloads such as OLTP (Online Transaction Processing), data warehousing, and analytics.
Examples
Basic info
Explore which infrastructures are in different stages of their lifecycle and when they were created. This allows you to assess the overall health and status of your infrastructures.
select display_name, id, lifecycle_state, time_created, time_zone, cpus_enabled, max_cpu_countfrom oci_database_exadata_infrastructure;
select display_name, id, lifecycle_state, time_created, time_zone, cpus_enabled, max_cpu_countfrom oci_database_exadata_infrastructure;
List failed exadata infrastructures
This query can be used to identify any infrastructures in the Oracle Cloud Infrastructure that have failed to initialize. By doing so, it allows users to quickly pinpoint and address any issues that may be disrupting their infrastructure operations.
select display_name, id, lifecycle_state, time_created, shapefrom oci_database_exadata_infrastructurewhere lifecycle_state = 'FAILED';
select display_name, id, lifecycle_state, time_created, shapefrom oci_database_exadata_infrastructurewhere lifecycle_state = 'FAILED';
List infrastructures older than 90 days
Discover the segments that consist of exadata infrastructure older than 90 days. This is useful for identifying potential areas for system optimization or data archiving.
select display_name, id, lifecycle_state, time_createdfrom oci_database_exadata_infrastructurewhere time_created <= (current_date - interval '90' day)order by time_created;
select display_name, id, lifecycle_state, time_createdfrom oci_database_exadata_infrastructurewhere time_created <= date('now', '-90 day')order by time_created;
List top 5 exadata infrastructures with max CPUs
Discover the top 5 Exadata Infrastructures with maximum CPU power, perfect for high-performance workloads.
select display_name, id, lifecycle_state, shape, cpus_enabled, max_cpu_countfrom oci_database_exadata_infrastructureorder by max_cpu_count desclimit 1;
select display_name, id, lifecycle_state, shape, cpus_enabled, max_cpu_countfrom oci_database_exadata_infrastructureorder by max_cpu_count desclimit 1;
Schema for oci_database_exadata_infrastructure
Name | Type | Operators | Description |
---|---|---|---|
_ctx | jsonb | Steampipe context in JSON form. | |
activated_storage_count | bigint | The requested number of additional storage servers activated for the Exadata infrastructure. | |
additional_compute_count | bigint | The requested number of additional compute servers for the Exadata infrastructure. | |
additional_compute_system_model | text | Oracle Exadata System Model specification. The system model determines the amount of compute or storage server resources available for use. | |
additional_storage_count | bigint | The requested number of additional storage servers for the Exadata infrastructure. | |
admin_network_cidr | text | The CIDR block for the Exadata administration network. | |
cloud_control_plane_server1 | text | The IP address for the first control plane server. | |
cloud_control_plane_server2 | text | The IP address for the second control plane server. | |
compartment_id | text | = | The OCID of the compartment in Tenant in which the resource is located. |
compute_count | bigint | The number of compute servers for the Exadata infrastructure. | |
contacts | jsonb | The list of contacts for the Exadata infrastructure. | |
corporate_proxy | text | The corporate network proxy for access to the control plane network. | |
cpus_enabled | bigint | The number of enabled CPU cores. | |
csi_number | text | The CSI Number of the Exadata infrastructure. | |
data_storage_size_in_tbs | double precision | Size, in terabytes, of the DATA disk group. | |
db_node_storage_size_in_gbs | bigint | The local node storage allocated in GBs. | |
db_server_version | text | The software version of the database servers (dom0) in the Exadata infrastructure. | |
defined_tags | jsonb | Defined tags for this resource. | |
display_name | text | = | The user-friendly name for the Exadata Cloud@Customer infrastructure. The name does not need to be unique. |
dns_server | jsonb | The list of DNS server IP addresses. Maximum of 3 allowed. | |
freeform_tags | jsonb | Free-form tags for this resource. | |
gateway | text | The gateway for the control plane network. | |
id | text | = | The OCID of the Exadata infrastructure. |
infini_band_network_cidr | text | The CIDR block for the Exadata InfiniBand interconnect. | |
is_cps_offline_report_enabled | boolean | Indicates whether CPS offline diagnostic report is enabled for this Exadata infrastructure. This will allow a customer to quickly check status themselves and fix problems on their end, saving time and frustration for both Oracle and the customer when they find the CPS in a disconnected state. You can enable offline diagnostic report during Exadata infrastructure provisioning. You can also disable or enable it at any time using the UpdateExadatainfrastructure API. | |
last_maintenance_run_id | text | The OCID of the last maintenance run. | |
lifecycle_details | text | Additional information about the current lifecycle state. | |
lifecycle_state | text | = | The current lifecycle state of the Exadata infrastructure. |
maintenance_slo_status | text | A field to capture ‘Maintenance SLO Status’ for the Exadata infrastructure with values ‘OK’, ‘DEGRADED’. Default is ‘OK’ when the infrastructure is provisioned. | |
maintenance_window | jsonb | Maintenance Window information. | |
max_cpu_count | bigint | The total number of CPU cores available. | |
max_data_storage_in_tbs | double precision | The total available DATA disk group size. | |
max_db_node_storage_in_gbs | bigint | The total local node storage available in GBs. | |
max_memory_in_gbs | bigint | The total memory available in GBs. | |
memory_size_in_gbs | bigint | The memory allocated in GBs. | |
monthly_db_server_version | text | The monthly software version of the database servers (dom0) in the Exadata infrastructure. | |
netmask | text | The netmask for the control plane network. | |
next_maintenance_run_id | text | The OCID of the next maintenance run. | |
ntp_server | jsonb | The list of NTP server IP addresses. Maximum of 3 allowed. | |
rack_serial_number | text | The serial number for the Exadata infrastructure. | |
region | text | The OCI region in which the resource is located. | |
shape | text | The shape of the Exadata infrastructure. The shape determines the amount of CPU, storage, and memory resources allocated to the instance. | |
sp_connection_name | text | =, !=, ~~, ~~*, !~~, !~~* | Steampipe connection name. |
sp_ctx | jsonb | Steampipe context in JSON form. | |
storage_count | bigint | The number of Exadata storage servers for the Exadata infrastructure. | |
storage_server_version | text | The software version of the storage servers (cells) in the Exadata infrastructure. | |
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 the Exadata infrastructure was created. | |
time_zone | text | The time zone of the Exadata infrastructure. | |
title | text | Title of the resource. |
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_exadata_infrastructure