Oracle Cloud Infrastructure Documentation

Analyze the Critical Exadata Systems

From the Exadata Insights dashboard, you easily identify systems that are projected to reach high utilization. You can then drill down into individual systems for a detailed look at system resources to identify specific issues.

From the Exadata Insights dashboard, you can identify systems that are projected to reach high utilization. To drill down into an individual system, click the name of the Exadata system.

For each Exadata system, you can get a detailed look at the following resources:

  • Details
  • Rack and key metrics
  • Metrics by database
  • Metrics by host
  • Exadata storage
  • Component details

Rack and key metrics

This provides a detailed view of the rack, including software inventory, hardware inventory, rack visualizations, component details, and key monitoring metrics for the system. Software inventory includes Oracle Databases, VM clusters, Autonomous VM clusters, and cluster ASMs. Hardware inventory includes storage servers, servers, switches, and power distribution units (PDUs).

Note

The rack view is not displayed for Exadata systems that contain only Autonomous VM clusters.

Use the Schematic and Physical options to switch between the schematic and physical rack views. The schematic view displays a logical representation of the rack and its components. The physical view displays front and rear images of the rack. Select a component in either view to open the Selected Component panel, which displays information such as the component name, component type, slot, model or description, and, for supported component types, resource usage metrics. If Resource usage details is available, click it to open the corresponding resource page for the selected component. For example, selecting Resource usage details for a storage server opens the Exadata storage tab.

Key metrics include CPU, memory, IOPS, and Exadata storage. The values shown represent the 90th percentile of the daily averages. If you select a time range of 7 days or less, the values represent the 90th percentile of the hourly averages.

Note

Exadata systems that contain only Autonomous VM clusters do not support IOPS. To view IOPS metrics for an Exadata system, onboard at least one non-autonomous VM cluster.

Metrics by database

This provides a detailed look at CPU, Storage, Memory, and I/O utilization across all databases in the system. The volume of resources used and the percentage change are represented visually through the size and color of the cells, respectively. Cells that are larger in size use more resources than smaller cells. The largest cell represents the databases using the most resources. The color of the cells is determined by the percent utilization of the selected resource.

To analyze resource utilization across a subset of databases, use the applied filters to filter databases by compartment, database entity, and tags. Use the Grouping applied filter to group databases according to CDB, Host, Database type, Utilization level, VM cluster, Free-form tags, or Defined tags. Click a specific group to view the trend and forecast for resource utilization for all databases within the group. For more information on group tags, see Group by Tags.

Note

For Ops Insights to forecast your resource utilization for a year, there must be at least 12 months of stored data. The forecast value is more accurate when there’s more data.

The 0–25% resource utilization is considered as low utilization, and 75–100% utilization of resources is considered as high utilization.

You can use the Trend & forecast utilization chart to plan your database resource capacity.

Note

To verify trend accuracy for both Exadata databases and hosts, you can compare historical data with forecasted trends using Forecast Backtesting. For more information, see Forecast Backtesting.
Note

When analyzing database memory, Ops Insights displays database tablespace allocation in terabytes (TB) instead of disk storage, potentially causing a discrepancy between the memory capacity and the DBaaS value.

Metrics by host

This provides you with a detailed look at CPU and Memory (logical memory) utilization across all hosts in the system. The utilization chart and Trend & forecast chart are functionally similar to those used for Metrics by database.
Note

For Virtualized Exadata systems, the CPU and Memory metrics shown are for the Virtual Machine.
Note

When analyzing host memory, Ops Insights displays database tablespace allocation in terabytes (TB) instead of disk storage, potentially causing a discrepancy between the memory capacity and the DBaaS value.

Exadata storage

This provides different views based on the inventory available in the Exadata system.

  • Exadata storage server: Displayed for Exadata systems with only non-autonomous VM clusters. This view provides a detailed look at individual clusters and diskgroups that comprise the Exadata Storage Server. Total usable storage is shown for each cluster, along with IOPS and Throughput.

    You can view data as Individual data series to view trends for separate diskgroups or storage servers, or Aggregate data series to view a summed total of diskgroup or storage server data that provides insight into the overall performance of the cluster instead of individual diskgroups or storage servers.

  • AVMC and storage server: Displayed for Exadata systems with both Autonomous VM clusters (AVMC) and non-autonomous VM clusters. This view provides a detailed look at individual clusters and diskgroups that comprise the Exadata Storage Server. Total usable storage is shown for each cluster, along with IOPS and Throughput.

    It also provides detailed storage usage for Autonomous VM clusters. Total usable storage is shown for each Autonomous VM cluster; IOPS and Throughput are not supported for Autonomous VM clusters.

    For storage-server data, you can view data as Individual data series to view trends for separate diskgroups or storage servers, or Aggregate data series to view a summed total of diskgroup or storage server data that provides insight into the overall performance of the cluster instead of individual diskgroups or storage servers. Autonomous VM cluster storage data is displayed as a separate chart for each Autonomous VM cluster in both views.

  • AVMC storage: Displayed for Exadata systems with only Autonomous VM clusters. This view provides detailed information about storage usage for Autonomous VM clusters. Total usable storage is shown for each Autonomous VM cluster; IOPS and Throughput are not supported for Autonomous VM clusters. There is only one view available for Autonomous VM cluster storage, with a separate chart for each Autonomous VM cluster.

Component details

This provides a tabular view of the hardware and software components in the selected Exadata system. Use the Search field or the Component type filter to locate components of interest.

The table displays information such as the component name, component type, category, model or description, CPU, memory, storage, I/O, IOPS, and throughput. The information displayed varies by component type. If View usage details is available in the Resource usage details column, click it to open the corresponding resource page for the selected component. For example, selecting View usage details for a storage server opens the Exadata storage tab.

Analyzing an Exadata System

You can analyze the CPU, memory, and I/O resources that are capacity bottleneck using the forecasted data. Use this information to identify the top databases consuming host CPU, memory, storage disk, or I/O resources.

To resolve a capacity bottleneck:

  1. Relocate the high resource consuming databases.
  2. Find if the CPU usage increment is caused by bad SQL.
  3. Consider adding more servers.