Documentation forDatabase Performance Analyzer

Database Performance Analyzer 11.1 Release Notes

Release date: November 7, 2017

These release notes describe the new features, improvements, and fixed issues in Database Performance Analyzer 11.1. They also provide information about upgrades and describe workarounds for known issues.

If you are looking for previous release notes for Database Performance Analyzer, see Previous Version documentation.

The Fixed Issues section of this article describes the fixes in DPA 11.1 and DPA 11.1 Service Release (SR) 1.

New features and improvements in DPA

Return to top

DPA 11.1 offers new features and improvements compared to previous releases of DPA.

Improved Monitoring of Availability Groups

When a SQL Server database instance includes Availability Groups (AGs), the DPA homepage provides the following information:

  • The AG status icon identifies database instances that include AGs. The color of the dot indicates the AG status.
  • An AG status summary box shows the number of database instances with partially healthy or unhealthy AGs. As with other status summary boxes, click the filter next to a status to display only those instances.

When you drill in to a database instance that includes AGs, click the AG Status tab to see the status of AGs, databases, and replicas, including synchronization and failover status information.

Annotation when an AG failover occurs

Annotations are automatically added to wait time charts when an AG failover occurs. The annotations allow you to compare changes in performance before and after a failover.

AG alerts

You can configure DPA to alert you when:

  • An AG status becomes Partially Healthy and Not Healthy
  • An AG failover occurs

>> Learn more about improved monitoring for AGs

Subscription licensing for AWS DPA servers

If you have databases in the Amazon cloud, you now have the choice to monitor them with subscription pricing. Simply deploy the DPA 11.1 server from the Amazon Web Services (AWS) Marketplace. As you register databases and monitor them, DPA charges your Amazon Subscription through the AWS Metering Service. DPA charges you based on the number of database instances you monitor each hour. See the AWS Marketplace for details and pricing.

If you want to use your individual DPA licenses in the Amazon cloud, simply deploy a regular EC2 instance, install DPA, and apply your license. You cannot mix using individual DPA licenses and subscription licensing on a single instance of DPA.

For more information about deploying DPA in AWS, see Launch SolarWinds DPA on Amazon AWS in a Linux AMI.

Improved wait time status meter

The following improvements have been made to the wait time status meter on the DPA homepage:

  • DPA evaluates status every 10 minutes instead of once an hour.
  • There are now three statuses instead of two.

DPA uses the same statuses as the Orion Platform: green (normal), yellow (tracking high), and red (tracking very high). When you integrate DPA with the Orion Platform, status information is displayed consistently.

DPA data in Performance Analysis (PerfStack™) dashboards

With version 11.1 of the DPA Integration Module (DPAIM), users can add DPA data to PerfStack dashboards, including wait time, database metrics, VM metrics, and custom metrics. When you identify a time period with significant wait times, you can use the Data Explorer to examine the SQL statements that were executed during that period. Both DBAs and non-DBAs can use this data to identify relationships between database wait times and other factors in the environment.

DPA users who do not own other SolarWinds products can access DPA data in PerfStack. You can install DPAIM 11.1 stand-alone (no other Orion products required), and use all of the Orion features available to DPA data.

>> Learn more about DPA data in PerfStack

>> Learn more about PerfStack

UI improvements

  • The database instance dropdown menu displays a status indicator.

  • When you search for a SQL statement while creating an alert or a report, the search results include each SQL statement's total wait time for the last 7 days. By default, the results are ordered by wait time.

    To configure the amount of wait time, change the value of the advanced option REPORT_SEARCH_WAIT_TIME_DAYS.

  • Icons have been updated.

Changes to system requirements

DPA 11.1 adds support for the following versions:

Monitored databases
  • Oracle 12.2
  • IBM DB2 11.1
  • MariaDB 10.0, 10.1, and 10.2
  • SQL Server 2017 (Windows and Linux)
Repository database
  • Oracle 12.2
  • SQL Server 2017
Virtual environment
  • vCenter Server 6.5
  • ESX/ESXi 6.5

DPA 11.1 removes support for the following versions:

Monitored databases IBM DB2 9.5
Virtual environment
  • vCenter Server 5.1
  • ESX/ESXi 5.1

For a complete list of DPA 11.1 system requirements, click here.

Integration with the Orion Platform

When you integrate DPA with the Orion Platform, you can view information from DPA in the Orion Web Console. For example, integration adds database information to AppStack views, and allows you to include database wait time metrics in PerfStack dashboards. To integrate:

  1. If necessary, install the DPA Integration Module (DPAIM):
    • DPAIM is automatically installed when you install SolarWinds SAM.
    • To install DPAIM without SolarWinds SAM, use the SolarWinds Orion Installer.
  2. Integrate DPAIM in the Orion Platform Settings.

To enable DPA integration, the Orion Platform must use a SQL Server account to access the Orion database. If the Orion Platform uses Windows authentication, run the configuration wizard and change the authentication method to use a SQL Server account before you integrate DPA.

If the Orion Platform uses Windows authentication and you attempt to integrate DPA, you receive the following error message:

There was an error when trying to enable the integration with the DPA server: Establishing federation with jSWIS failed.

New customer installation

Return to top

For information about installing Database Performance Analyzer, see the DPA Installation and Upgrade Guide.

Before you upgrade!

If you are upgrading from a previous version, be aware of the following considerations:

  • DPA 11.1 requires JRE 1.8. If you configured DPA to use an external JRE, DPA verifies it is version 1.8 or later. If the verification fails, DPA attempts to use the JRE included with the installation.

  • If your repository database is MySQL and you are upgrading from DPA 10.2 or earlier, DPA drops the CON_ALERT_HISTORY and CON_ALERT_HISTORY_RESULT tables during the upgrade due to column resizing. Follow the instructions in this article to back up your repository before upgrading, and restore your alert history after upgrading.

How to upgrade

If you are upgrading from a previous version, use the following resources to plan and implement your upgrade:

Fixed issues

Return to top

DPA 11.1 fixes the following issues.

Case number Description

929798, 1082802, 1094705, 1166631, 1198885, 1213479, 1216265

Multiple security fixes have been applied.

956273, 1094689, 1112177, 1195869

By default, DPA uses NTLM to authenticate the DPA server to monitored database instances, but you can configure DPA to use Kerberos instead of NTLM. See this KB article for instructions.

1091237, 1185657

To improve the efficiency of the statistics query on Oracle instances, the default value for the ORACLE_STATS_POLL_V2 advanced option has been changed to TRUE.


An Active Directory group with a plus sign (+) in the name can be added to DPA. Escaping the plus sign is no longer necessary.


If you choose the wrong template during mass registration, DPA displays an error message that accurately describes the problem.


Newly created repositories will use the UTF-8 character set, which supports multi-byte characters (such as Chinese).


DPA now displays the correct time when the DPA server is located in a Turkish time zone.


Additional LDAP properties have been added to the file. You can use these properties to override the default AD/LDAP connection settings, such as the connection timeout value. For more information about the new properties, see Resolving AD/LDAP connection errors in DPA.


SQL Server database instances with Chinese collation can be registered for monitoring.


The query for the Distinct Machine Total metric has been updated to run on case-insensitive database instances, such as Sybase ASE 15.7 and later.


When a non-admin user creates an alert, the Create Alert page no longer displays the Add Contact and Add Contact Group buttons, which are features reserved for admin users.


Setting the QUICK_POLL_INTERVAL to more than 1 poll per second no longer causes errors in database summarization.


When a SQL Server database instance that contains Availability Groups (AGs) is registered and the license is not automatically allocated, DPA now correctly recognizes the instance as having AGs.
N/A When you are updating connection details for a SQL Server database instance, the Update Connection Info wizard no longer requires port information when the database instance is registered with the instance name.

1073989, 1103885, 1107496

Root blockers summarization no longer consumes large amounts of memory when DPA is monitoring a database instance that has very high amounts of blocking.


If a database requires SSL and the network uses NTLMv2, you no longer need to enter a value in the Advanced Connection Properties section to register the database.


When you are monitoring an Oracle 11.x or higher database instance, the plan poll query in DPA no longer fails with the error "Character string buffer too small."

DPA 11.1 Service Release (SR1) fixes the following issues.

Case number Description


This service release resolves an issue that caused DPA to stop monitoring all databases and deallocate licenses from all instances if a monitored Azure SQL database instance returned data in an unexpected format.

If you experience this issue, apply DPA 11.1 SR1 and then make sure all licenses are allocated as you expect.


The license activation page is now loaded properly when the connection to SolarWinds API takes longer than usual and does not time out.


If file names are reported as NULL by a monitored Oracle instance, DPA no longer logs a warning message that a unique constraint was violated.


The Configure AD/LDAP wizard no longer allows an invalid format for the user name. Invalid characters in the user name were causing LDAP searches to fail, even though the Test Connection in the Configure AD/LDAP wizard was successful.


Viewing deadlock details no longer returns a java.lang.NullPointerException error when the deadlock does not have a 'logused' entry.


Monitoring an Azure database no longer collects sessions of all databases on the given logical server.


When users with certain DNS configurations attempt to start DPA on an Amazon Web Services (AWS) image, DPA no longer fails to start because the image validation failed.

Known Issues

DPA does not support MySQL 8.0
Issue: MySQL 8.0 is not supported for use as a DPA repository, and DPA cannot monitor MySQL 8.0 database instances.
Resolution/Work-around: Use DPA with supported versions of MySQL.


Registering with a virtual IP address that routes to an AG listener

Issue: If you have a SQL Server that contains one or more AGs and you register it with a virtual IP address that routes to an AG listener, DPA does not detect that you have registered an AG via the listener. Because the registered IP address does not match an AG listener's IP address, DPA behaves as if it were monitoring an instance and does not expect that monitoring will fail over when a listener failover occurs.

As a result:

  • When the listener that you intended to register fails over, DPA does not detect that failover and might falsely detect other AG failovers. (To avoid this, see the Recommendations below.)
  • DPA does not automatically name the database instance in the format <PrimaryReplicaName> via <ListenerName>.
  • The listener name is not displayed where it normally would be, such as in the Availability Group Summary view.
  • The advanced option AG_STATUS_ROLLUP_USE_PRIMARY, which specifies how the AG status is calculated when an AG is registered via the listener, is not available.

All other AG monitoring functionality is available. DPA will follow the listener after a failover, and continue monitoring the primary replica.

Resolution/Work-around: SolarWinds recommends registering the AG with the IP address of the listener instead of the virtual IP. However, if you choose to register with the virtual IP address:

  • Do not set the SQL Server Availability Group Failover alert for this monitored instance.
  • Disable failover annotations for this monitored instance. To do so, change the value of the advanced system option AG_EVENT_ANNOTATIONS_ENABLED.


Incorrect metric values reported for SQL Server 2017 on Linux

Issue: When you are monitoring a SQL Server 2017 database instance that runs on a Linux server:

  • The O/S CPU Utilization resource and the Instance CPU Utilization resource always show usage at 100%.
  • The O/S Memory Utilization resource always shows usage at 0%.

SQL Server reports these values.

Resolution/Work-around: Disregard these metric values.


Limitations when monitoring AGs deployed on SQL Server 2017 on Linux

Issue: When you are monitoring a SQL Server 2017 AG that runs on Linux, some information or functionality might be unavailable:

  • If you register the AG via the listener, the listener name is not included in the instance name.
  • "Unknown" is displayed for the Failover Mode and the Cluster Name.
Resolution/Work-around: None.


Time zone selection
Issue: When you are registering a database instance that runs in the cloud, the time zone selected by default is the first one matching an offset of your browser session. This might be incorrect under some circumstances. Also, the drop-down menu for selecting the time zone contains a long list of selections that are loaded from the Java Virtual Machine.
Resolution/Work-around: Manually select the correct time zone for your environment.


Attempting to run a report returns the error DPA Unable to generate the chart

Issue: When the DPA server is running RHEL 7.4 (or its distributions, such as Oracle Linux 7.4), DPA returns the following error when you try to run a report:

DPA Unable to generate the chart: java.lang.ArrayIndexOutOfBoundsException: 0

Resolution/Work-around: Follow the instructions in this article to change the default font used by RHEL 7.4.


DPA has high CPU utilization for long periods when Embedded Mail Server is used
Issue: When Embedded Mail Server is selected as the mail server configuration option and an attempt to send email fails (for example, because of an environmental issue such as a firewall or the mail server configuration), DPA saves the email into a queue and tries to send the email again. If the problem persists, having a large number of emails in the queue causes high CPU utilization.
Resolution/Work-around: Change the mail server configuration, or fix the issue that is preventing mail from being sent. See this article for more information.


DB2 10.5 reporting wait time as type "NONE"
Issue: If you are monitoring a DB2 10.5 database instance, you might see wait times with the type "NONE."
Resolution/Work-around: Exclude this wait type from monitoring. To do this, open Advanced Options, click DB Instance Options, and select a database instance. Then click Wait Events in the upper-left corner.


CPU utilization for a large number of CPU cores
Issue: CPU utilization does not display properly for multi-core or -socket environments. DPA uses a deprecated view which does not provide consistent data for environments using a high number of cores or sockets.
Resolution/Work-around: Follow the instructions in this KB article.


Incorrect execution counts for SQL statements
Issue: When SQL Server purges statistics from the previous cached query plan for a SQL Statement from the master.sys.dm_exec_query_stats table, the execution count that DPA shows can be incorrect. This count can be extremely high, and doesn't match the execution count retrieved by querying the DPA repository.
Resolution/Work-around: Disregard the incorrect execution counts.


Registering an Oracle database instance that uses only SHA-2 to calculate checksums

Issue: If an Oracle database instance is configured to use only SHA-2 (Secure Hash Algorithm 2) to calculate checksums, the following error message is displayed when you try to register it as a monitored instance or as the DPA repository:

An unknown error has occurred. The provided message is "Could not get JDBC Connection; nested exception is java.sql.SQLException: Oracle Error ORA-12650".

Resolution/Work-around: To enable DPA to connect to Oracle databases that use only SHA-2, you must update the JDBC driver as described in this KB article.


SQL error on Blocking tab
Issue: The Blocking tab becomes unresponsive if there are more than 32,767 records on the Real Time Session page.
Resolution/Work-around: N/A


Repository growth when monitoring a VM with many disks
Issue: When DPA is monitoring a database instance on a VM with a large number of disks, the CONV_METRIC_DETAIL tables grow rapidly, resulting in a large repository.

Resolution/Work-around: Do one of the following:

  • Lower the sampling interval.
  • Disable the VM Disk Device metrics. (For instructions, see this KB article.)
  • Lower the value of the VSPHERE_METRICS_CLEAN_DAYS options to reduce the amount of data being stored. (For instructions, see this KB article.)


The ApplicationIntent flag is ignored when you are registering an AG listener
Issue: If you are registering a secondary replica in an AG cluster and you specify the ApplicationIntent=ReadOnly flag, this flag is ignored and DPA connects to the primary replica.
Resolution/Work-around: To specify the ApplicationIntent flag, register a database instance and not the listener. To specify the flag, follow the instructions in this KB article.


Unable to name a SQL statement from the Blockers tab
Issue: On the Blockers tab in the "SQL Statements Executed by Blocking Session" chart, you can click a SQL statement to open the SQL Properties dialog. The dialog includes the Name and Description fields, but they are read-only.
Resolution/Work-around: Name the SQL statement from a different location in DPA.


Unable to change tabs on the Real Time Sessions page in Internet Explorer
Issue: When you use certain versions of Internet Explorer to view the Real Time Sessions page for a monitored database instance, you cannot always change between the Sessions, Blocking, and Locking tabs. Clicking a different tab might work the first time, but subsequent clicks do not work. This issue has been seen on IE 11.431.16299.0 and 11.48.17134.0.
Resolution/Work-around: If you experience this issue, open DPA in a different browser.

Deprecation notices

Return to top

This version of Database Performance Analyzer deprecates the following platforms and features.

Deprecated platforms and features are still supported in the current release. However, they will be unsupported in a future release. Plan on upgrading deprecated platforms.

Type Details
VMware DPA will be ending support for VMware vCenter Server 5.5 and VMware ESX/ESXi Host 5.5 in an upcoming release. DPA 11.1 still supports VMware 5.5, but SolarWinds encourages users to upgrade to VMware 6.0 or 6.5 at their earliest convenience.
DPA server DPA 11.1 is the last version to support Windows Server 2008 R2 as a platform for the DPA server.
Repository database DPA 11.1 is the last version to support SQL Server 2008 R2 as a database repository for the DPA server.  DPA will continue to monitor SQL Server 2008 R2 database instances.

End of support

Return to top

This version of Database Performance Analyzer no longer supports the following platform.

Type Details
DPA server OS Solaris is no longer a supported operating system for the DPA server. For a list of supported operating systems, see the DPA 11.1 system requirements.

End of life

See End of Life Policy for information about end of life and end of engineering for SolarWinds products.

Version EoL Announcements EoE Effective Dates EoL Effective Dates
10.1 March 15, 2017 End-of-Life (EoL) announcement - Customers on DPA version 10.1 or earlier should begin transitioning to the latest version of DPA. June 15, 2017 End-of-Engineering (EoE) - Service releases, bug fixes, workarounds, and service packs for DPA version 10.1 or earlier will no longer actively be supported by SolarWinds. June 15, 2018 End-of-Life (EoL) - SolarWinds will no longer provide technical support for DPA version 10.1 or earlier.
10.0 March 15, 2017 End-of-Life (EoL) announcement - Customers on DPA version 10.0 or earlier should begin transitioning to the latest version of DPA. June 15, 2017 End-of-Engineering (EoE) - Service releases, bug fixes, workarounds, and service packs for DPA version 10.0 or earlier will no longer actively be supported by SolarWinds. June 15, 2018 End-of-Life (EoL) - SolarWinds will no longer provide technical support for DPA version 10.0 or earlier.

Legal notices

Return to top

© 2017 SolarWinds Worldwide, LLC. All rights reserved.

This document may not be reproduced by any means nor modified, decompiled, disassembled, published or distributed, in whole or in part, or translated to any electronic medium or other means without the prior written consent of SolarWinds. All right, title, and interest in and to the software, services, and documentation are and shall remain the exclusive property of SolarWinds, its affiliates, and/or its respective licensors.


The SolarWinds, SolarWinds & Design, Orion, and THWACK trademarks are the exclusive property of SolarWinds Worldwide, LLC or its affiliates, are registered with the U.S. Patent and Trademark Office, and may be registered or pending registration in other countries. All other SolarWinds trademarks, service marks, and logos may be common law marks or are registered or pending registration. All other trademarks mentioned herein are used for identification purposes only and are trademarks of (and may be registered trademarks) of their respective companies.