Exadata Fleet Dashboards

The Exadata Dashboards are a set of Oracle-defined dashboards that distill Exadata component hardware and software metric data for individual Exadata (on-premises and Cloud-based) and Recovery Appliance systems into integrated, detailed fleet-level visualizations.

These dashboards are part of the Exadata Management Pack and Zero Data Loss Recovery Appliance Management Pack, and will include data only for Database Machine, Exascale Infrastructure, and Recovery Appliance targets for which the corresponding pack is enabled. Some of the dashboards incorporate database target information for the databases running on the Engineered Systems. Since such data will only be shown for databases monitored by Oracle Enterprise Manager, it is recommended that all Oracle Enterprise Manager databases be discovered in Oracle Enterprise Manager in order to leverage the full capability of the dashboards.

Example Scenario to Analyze Capacity and Resource Usage With the Dashboards

  • Get a high-level overview of resource usage across the fleet: Start with the Exadata Fleet Aggregated Capacity dashboard, using the filters to narrow down the results to a subset of the fleet, say all Engineered System Type = Exadata with Lifecycle Status = Production and Location = Chicago. If a trend of high storage utilization is noted, then the next step would be to consult the Exadata Fleet Capacity dashboard to view the bubble charts representing individual Engineered Systems and compare their metrics.

  • Identify which Exadata systems need attention: After navigating to the Exadata Fleet Capacity dashboard, the filter settings set on the previous dashboard are automatically carried over and the dashboard displays each Exadata system as a bubble on the Storage charts. This makes it easy to identify which Exadata systems are contributing towards the high storage utilization. If filtering with Group By = Department shows that the Exadata targets in the sales department have higher storage utilization than the others, then filtering by Target Property: Department = Sales would focus attention only on the systems with higher storage utilization.
  • Analyze usage for components within an Exadata system: The next step is to consult the Exadata Fleet Component Capacity dashboard. With the same filters automatically applied, the bubble charts would show the usage patterns of ASM Data and Recovery disk groups for the production Exadata systems in Chicago serving the sales department. The growth for these disk groups could be analyzed further in the adjacent bubble charts and tables.

  • Analyze metric trends: If the analysis shows that the high storage utilization is isolated to one Database Machine (DBM1), this can be further isolated by going back to the Exadata Fleet Aggregated Capacity dashboard to view the storage utilization metric history for this Exadata by specifying filter Engineered System Target Name = DBM1.

Filters for Dashboards

A common filter section is available across all Exadata Fleet Dashboards to customize the data displayed, allowing for a more focused and manageable data set in each dashboard. These filters are sticky, in that they retain their values when navigating across different Exadata Fleet Dashboards, as applicable.


Filters for Dashboards

The Engineered System Target Name, Engineered System Type, and Engineered System Deployment Type filters are applied at the Engineered System target level. When applied, they refine the dashboard content, displaying results from the matched Engineered Systems as well as their hierarchy. The Group By filter is applicable only to the Exadata Fleet Capacity and Exadata Component Capacity dashboards.

The remaining filters are applied at the individual component level. When the filter criteria are met for at least one component of an Engineered System, the entire Engineered System and all its components are considered a match and rendered along with all other matched systems on the dashboard.

The following supported filters are common across all Exadata Fleet Dashboards:

Filter Supported Operators Supported Values
Engineered System Target Name
  • Equal to
  • Not equal to
  • Contains
  • Does not contain
  • Starts with
  • Does not start with
  • Ends with
  • Does not end with
Any valid Oracle Enterprise Manager target name pattern.
Engineered System Type Equal to
  • Exadata
  • Recovery Appliance
Engineered System Deployment Type Equal to
  • Cloud@Customer
  • On-Premises
  • Oracle Cloud Infrastructure
Exadata Generation Equal to

The Exadata hardware rack generation; for example, X8-2, X7-2.

The Exadata generation is derived from the storage server make/model or the database server rack identifier; for example:

  • If the storage server make/model value is Oracle Corporation ORACLE SERVER X8-2L High Capacity, then the generation is inferred to be X8-2.
  • If the database server rack identifier is Exadata Database Machine X8-2 AK00831126, then the generation is inferred to be X8-2.
Host Operating System Major Version Equal to

The host operating system version in the format X.Y; for example, 8.9, 7.9.

The major version is derived from the full version by extracting the first two numbers in the dotted notation. Usually, the host OS version contains five numbers separated by dots; for example, 8.9.0.0.0 would yield a major version of 8.9.

Exadata Software Major Version Equal to

The Exadata software version in the format X.Y; for example, 21.0, 23.0.

The major version is derived from the full version by extracting the first 2 numbers in the dotted notation; for example, if the full version of the storage server is 21.0.0.0.0, the major version is 21.0.

Target Properties:

  • Contact

  • Cost Center

  • CSI

  • Comment

  • Department

  • Downtime Contact

  • Lifecycle Status

  • Line of Business

  • Location

  • Site

Equal to

Filters will be populated based on the values set for the target properties.

Targets within the hierarchy of the Exadata or Recovery Appliance topology can have different properties set at the target level. If any of the targets in the hierarchy match the filter criteria, the dashboard will include results from the parent Exadata or Recovery Appliance.

Group By Equal to This option is available only for the Exadata Fleet Capacity and Exadata Component Capacity dashboards. It helps to categorize results based on the selection, and renders them with different colors. For instance, if Group By = Department is set and the results contain three departments (HR, Finance, Sales), then the bubbles on the Exadata Fleet Capacity dashboard is rendered in three colors, each corresponding to one department.
  • All filters described above are applied using the AND condition. For example, specifying the filters as Engineered System Target Name = abc with Target Property:Location = Austin customizes the dashboard content with results that match both these criteria.
  • The Host Operating System Major Version filter and the Exadata Software Major Version filter are applied to the appropriate child component targets under the parent Engineered System target. An Engineered System and all its components are considered a match if any one of the version filter criteria is met. For example, a filter on Host Operating System Major Version = 8.7 and Exadata Software Major Version = 24.1 selects Engineered Systems and all their components if at least one of their hosts has operating system major version 8.7 or if at least one of their storage servers has Exadata software version 24.1.