Documentation forDatabase Performance Analyzer

View information from remote servers on the DPA Central Server

In a DPA Central Server, the Central page displays summarized information about all connected DPA servers.

To connect to DPA Central, a remote DPA server must run the same version of DPA as DPA Central. DPA Central cannot display data from servers running a different DPA version.

Open the Central page

Open the Central page to see database information from all connected DPA servers.

  1. From the DPA menu in the upper-right corner, click Central.

View the number of alarms for each server

On the Central page, click the Alarm Summary tab to see a summary of how many critical or warning level alerts or alarms are reported by each DPA server. The number on each row represents the number of issues reported for all instances monitored by that DPA server.

The Alarm Summary displays the following information:

  • Alerts: The number of broken alerts, and the number of alerts at each level that are triggered but not acknowledged. When the table is sorted by the Alerts column in descending order, broken alerts have the highest severity, followed by high-level alerts, followed by each subsequent alert level.

    Alert information is available in DPA 2024.2 and later. For DPA servers running earlier versions, a question mark is displayed. Upgrade your DPA servers to 2024.2 or later to see alert information for all servers.

  • Wait: The number of database instances where the wait time during the last hour was higher or much higher than normal.

  • Tuning: The number of query, index, or table advisors with a warning or critical status.

  • CPU: The number of CPU metrics whose value exceeded the warning or critical threshold.

  • Mem: The number of memory metrics whose value exceeded the warning or critical threshold.

  • Disk: The number of disk metrics whose value exceeded the warning or critical threshold.

  • Sess: The number of session metrics whose value exceeded the warning or critical threshold.

  • Net: The number of network metrics whose value exceeded the warning or critical threshold.

To see more detailed information, click a DPA server name or IP address in the Server column to open the DPA home page for that server.

View the number of registered databases not being monitored

On the Central page, click the Monitoring Summary tab to see how many instances registered by each DPA server are running. Each column represents a database type. A green up arrow indicates that some or all of the registered instances are running, and a blue down arrow indicates that none of the registered instances are running.

To see more detailed information, click a DPA server host name or IP address in the Server column to open the DPA home page for that server.

View alarm information for each monitored database instance

On the Central page, click the DB Instances in Alarm tab to see which monitored database instances have triggered alerts or alarms. The color of the square or icon indicates severity.

The following columns indicate whether any alerts or alarms were detected for each monitored instance:

  • Alert: If the instance has any broken alerts, this column contains the broken alert icon . Otherwise, it contains an icon to indicate the highest severity alert that is triggered but not acknowledged. When the table is sorted by the Alerts column in descending order, rows with broken alerts are first, followed by rows with high alerts, followed by each subsequent alert level.

    Alert information is available in DPA 2024.2 and later. For DPA servers running earlier versions, a question mark is displayed. Upgrade your DPA servers to 2024.2 or later to see the alert status for all monitored instances.

  • Wait: A colored box to indicate whether anomalies (higher than usual waits) were detected for the instance during the last hour.

  • Tuning: An icon to indicate if query, index, or table advisors with a warning or critical status were detected for the instance.

  • CPU: An icon to indicate if the values of CPU metrics exceeded the warning or critical threshold.

  • Mem: An icon to indicate if the values of memory metrics exceeded the warning or critical threshold.

  • Disk: An icon to indicate if the values of disk metrics exceeded the warning or critical threshold.

  • Sess: An icon to indicate if the values of session metrics exceeded the warning or critical threshold.

  • Net: An icon to indicate if the values of network metrics exceeded the warning or critical threshold.

To see more detailed information, click a DPA server name or IP address in the Server column to open the DPA home page for that server. Or click the instance name in the DB Instance column to open the Trends charts for that instance.

View information about all database instances

On the Central page, click the My DB Instances tab to see all database instances that you have rights to view. The information on this page is similar to the DPA Home page, including whether the instance is on or off, the database type, and whether alerts or advisors have been issued.

Pagination is used to break up long lists of instances. Click the arrows to the right or left of the page number at the bottom of a list to navigate to another page.

Select Show Groups to display instances in groups defined on the DPA server.

Sort by alarm severity

By default, the tables on the DB Instances in Alarm tab and the My DB Instances tab are sorted by the DPA server name or IP address. To put the instances with the most severe issues at the top of the list, click Sort by Alarm Severity.

When multiple rows have the same severity score, issues in the Alert column are given more weight, followed by the Wait column, the Tuning column, and then all other columns.

Select columns

You can choose which columns you want to see on the DB Instances in Alarm tab and the My DB Instances tab. In addition to the default columns, you can add columns to display the values of custom properties that you have defined.

  1. In the top-left corner, click Select columns.

    The Edit columns dialog lists the default columns and any custom properties.

  2. Select or deselect columns in the list.

  3. Click Update columns.

Filter the list

To help you quickly find certain instances, you can filter the list of instances on the DB Instances in Alarm and My DB Instances tabs. You can filter by instance name, database type, or custom property values:

  • To filter the list by instance name, in the Filter by DB instance name box, enter a string that is included in the instance name as it is displayed in DPA.

  • To filter by database types or custom property values, select the types or the custom property values from the Filters pane on the left.

Change how often data is retrieved and refreshed

You can specify how often DPA Central retrieves data from remote servers, and how often the data displayed on DPA Central pages is updated when the Auto refresh option is on.

Change how often data is retrieved

At regular intervals, DPA Central retrieves information from all remote DPA servers. By default, the interval is one minute. You can change this default. For example, in large deployments you might need to increase the refresh rate. To change it, edit the advanced option CENTRAL_CACHE_REFRESH_FREQUENCY.

Change how often the display is refreshed

If the Auto refresh option is on, the data displayed on DPA Central pages is automatically refreshed at regular intervals with the latest data retrieved from remote DPA servers. By default, data is refreshed every 300 seconds. You can change the default refresh rate.

  1. From the DPA menu in the upper-right corner, click Options.

  2. Under Administration > Display, click Display Options.

    The Display Options page opens.

  3. In the DPA Central Page Refresh box, enter the number of seconds between DPA Central data refreshes.

Manually refresh the displayed data

To manually refresh the data on the on the DB Instances in Alarm and My DB Instances tabs at any time, click the refresh button .

Troubleshooting

Manually refresh cached data

If the displayed data seems inconsistent or outdated, flushing the cache ensures that fresh data is retrieved from the remote DPA servers.

  1. Log in to the server where DPA is running.

  2. Stop the DPA service.

  3. Navigate to:

    DPA-install-dir\iwc\tomcat\ignite_config\iwc\central

  4. Delete the following folders:

    • cache
    • lucent-index

  5. Start the DPA service.

Missing instances

If DPA Central is not displaying the expected instances from a remote DPA server, check the following: