Performance Hub Features

Performance Hub consists of a number of tabs and options, and provides reports so you can monitor your databases.

Note:

These tabs displayed in Performance Hub depends on the Database Management option that is enabled for the database you are monitoring, if the database is running in a Base Database Service or Exadata Database Service on Dedicated Infrastructure system, or is managed with External Database.

When a database is set to:
  • Basic Management - Performance Hub displays only the ASH Analytics and SQL Monitoring tabs.

  • Full Management - Performance Hub displays all the tabs described in the subsequent sections.

For more information, see About Management Options in Enable Database Management for Oracle Cloud Databases.

Note:

Performance Hub currently does not support Pluggable Databases in Base Database Service systems.

The Performance Hub page includes the following tabs:
Additionally, Performance Hub provides options for:

Performance Hub is also available in another mode, namely Top Activity Lite. This mode is a simplified view of Performance Hub and focuses on fast response time to monitor the performance of database systems in real time.

You can explore these tabs and options to monitor a selected database and analyze its performance, which includes but is not limited to:

  • How much is a database waiting for a resource, such as CPU or disk I/O

  • Whether database performance degraded over a given time period, and what is the primary reason

  • Which specific modules are causing a load on the system, and where most of the time a database spends on the modules

  • Which SQL statements are the key contributors to changes in database performance, and which executions are causing them

  • Which user sessions are causing performance bottlenecks

  • Which sessions are currently blocking, and if outstanding requests exist for a lock

  • Whether any databases are interfering with the current database

  • Which databases, disks, and cells are causing high I/O load, and if the load is for Backup, Rebalance, or User I/O

  • What cells are CPU bound, and how to determine the cell offload

  • What a database's configuration is, including software version and disk status