Documentation forDatabase Performance Analyzer

Database Performance Analyzer 11.0 Release Notes

Release date: March 14, 2017

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

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

New features and improvements in DPA

Return to top

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

Expanded database support

DPA 11.0 supports using the following database types as the permanent storage location for performance data captured by DPA from the monitored database instances. You can also monitor these databases:

  • Azure SQL
  • Amazon RDS for Aurora

Availability Group status

A new Availability Group (AG) Status tab shows AG summary and grouping information, including replica and database health, for SQL Server 2012 and later. You can register the AG Listener or instance, and see the status of all AGs in the instance.

Oracle adaptive plans

DPA 11.0 supports Oracle adaptive plans with notes, and marks steps that are no longer in use because they adapted. Stay informed as to how the Oracle optimizer is adjusting the execution plans for query optimization. DPA still captures actual execution plans to track the choices the optimizer is making.


DPA 11.0 better adapts to different screen resolutions, and improves filtering on the home page.

New customer installation

Return to top

For information about installing DPA 11.0, see the DPA 11.0 Administrator Guide.

Before you upgrade

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

  • Back up your current DPA deployment and repository database.
  • Java version: DPA 11.0 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.

How to upgrade

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

  • Use the DPA Installation and Upgrade Guide to help you plan and execute your upgrade.
  • When you are ready, download the upgrade package from the SolarWinds Customer Portal.
  • Upgrade your production server. If you are upgrading from DPA 9.0 or earlier, retrieve your license activation keys from the Customer Portal to complete the upgrade.

Fixed issues

Return to top

DPA 11.0 fixes the following issues.

Case number Description
1091237 DPA resource utilization is no longer high during Stats Poll for Amazon RDS for Oracle databases.
929798 The secure attribute was added to the DPA userName cookie.
929798 Cross-site request forgery protection was added.
922107 DPA no longer considers email addresses with special characters as invalid.
- Changing the encryption scheme in DPA Password Encryption Settings no longer affects certain features in the DPA Integration Module.



An issue with incorrect date and time information is fixed.
1054883 The message body of a Deadlock Detail email is transmitted correctly.
1054943 Tomcat is upgraded to 8.0.36 to solve a FileUpload issue.
1048389 Text in tuning advice emails is no longer truncated.
1047631 Plan advice no longer shows only 10 plans for all previous days.
1041183 The queries for count, blocking, and locking no longer cause the Current page to hang.
1035158 The error message displayed when you unregister a monitored database that is not running has been improved.
1031174 Options to hide the domain name, DPA version, and repository name from the login screen are now available
1022154 Input scrubbing for the Domain Name and custom Port fields was added to the AD/LDAP Configuration wizard.
1004881 A Tomcat option to prevent clickjacking was added.
876043 The text poll for SQL Server is no longer truncated to 8000 characters.
1125981 An issue with MySQL Live plans on MariaDB is fixed.

DPA 11.0.385 fixes the following issues:

Case number Description


Azure SQL databases that use a secured connection can be registered for monitoring with DPA.

When you register an Azure SQL database, you must include the suffix when you enter the database name (for example, or


DPA works correctly when accessed through a Microsoft Internet Explorer browser with compatibility mode on.


The Oracle plan poll job no longer fails on databases running Oracle 11.1 or earlier.


DPA does not require large amounts of memory to summarize root blocking data for intervals that contain many blocking events. Users no longer need to increase the amount of heap memory allocated to DPA (as described in this article).


Authentication using SSO no longer performs slowly or returns an error.

DPA 11.0.387 fixes the following issue:

Case number Description


Upgrading to the latest version of DPA no longer fails if the DPA repository uses SQL Server 2008.

Known issues

Return to top

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.


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


SQL Server port required
Issue: The Update Connection Info wizard requires port information for SQL Server, even if it is instance-based.
Resolution/Work-around: Enter the correct port.


Stats Poll on SQL Server
Issue: Stats Poll on SQL Server does not work correctly when counts disappear and reappear from master.sys.dm_exec_query_stats.
Resolution/Work-around: N/A


Dropped tables in a MySQL repository
Issue: If your repository database is MySQL, DPA drops the CON_ALERT_HISTORY and CON_ALERT_HISTORY_RESULT tables during the upgrade due to column resizing.
Resolution/Work-around: Follow the instructions in this article to back up your repository before upgrading, and restore your alert history after upgrading.


Grouping of Oracle pluggable databases
Issue: Oracle pluggable databases (PDB) from two container databases (CDB) on two computers that were created by cloning the database are placed into a single group. DPA uses the group name from the host name of one of the CDBs, and ignores the other.
Resolution/Work-around: Manually override the automatic PDB grouping.


Offline deactivation not available
Issue: When your DPA server can connect to the SolarWinds licensing server, that status is cached for 60 minutes. If the connection is lost during that time, offline deactivation is not available.
Resolution/Work-around: Restart DPA.


MySQL users requiring SSL
Issue: You cannot create a MySQL repository database, or register a MySQL database instance for monitoring, with a user that requires SSL for MySQL 5.6.24 and earlier.
Resolution/Work-around: Upgrade to MySQL 5.6.25 or later.


Deadlock polling for SQL Server 2012 RTM
Issue: When polling deadlocks from SQL Server 2012 RTM, DPA may fail to collect deadlock information if it is configured to use the Event File target for deadlock polling. By default, this issue only occurs when monitoring Amazon RDS for SQL Server instance (2012 RTM only). This can also occur on a regular SQL Server instance (2012 RTM) if the Event File target is used instead of the default Ring Buffer target.
Resolution/Work-around: Upgrade to the latest service release of SQL Server.


Manually registered instance of Amazon RDS for SQL Server
Issue: If you manually registered an Amazon for SQL Server instance for monitoring before that database type was added to the Register Instance Wizard the deadlock poll might not run properly because it will fail to create the Extended Events Session.
Resolution/Work-around: Update the DEADLOCK_POLL_SQL_SERVER_SESSION_NAME advanced option value from dpa_deadlock_capture to system_health for the affected instances.


Orion integration fails in Turkish environment
Issue: In a Turkish environment where the hostname contains an uppercase "i", DPA integration to Orion fails.
Resolution/Work-around: Change the Orion hostname to lowercase in the Websites table.


VM CPU Ready Time in DPA is computed differently than in VMware
Issue: In DPA, VM CPU Ready Time is computed as the average of Ready Time of all CPU cores. In VMware, Ready Time is computed as the addition of Ready Time of all CPU cores.
Resolution/Work-around: N/A


Historical data not displayed
Issue: If data is collected sporadically and there are over 30 distinct days of CONSW data that span more than 95 days, the charting engine will switch to use weekly data to generate trend charts instead of detail data. This only applies for Oracle repository databases in regions where the beginning of the week is Monday.
Resolution/Work-around: Lower the value of the CLEAN_DAYS_OF_DETAIL advanced option.


Cannot add an Active Directory group if the group name includes a plus sign (+)

Issue: If you add an Active Directory or LDAP group whose name includes a plus sign (for example, "+Developers"), an error similar to the following is displayed:

Unable to get the Repository users: javax.naming.InvalidNameException: Invalid name: CN=+developers,CN=Users,DC=ignite,DC=local

Resolution/Work-around: Follow the instructions in this article to update the group name in the conusergroup table. Add a backslash (\) in front of the + character to escape it.


Cannot register a database if it requires SSL and the network uses NTLMv2

Issue: If a database requires SSL and the network uses NTLMv2, database registration fails with the following message:

Database connection failed: A connection to the database could not be established: Invalid user and/or password


  1. On the Enter Monitored Database Instance Connection Information step of the Register Instance wizard, click Advanced Connection Properties.
  2. In the JDBC URL Properties box, enter:
  3. Click OK and complete the wizard.


Frequent polling interval causes database summarization to fail with an error

Issue: If you are monitoring an instance that supports blocking and the polling interval is very frequent, summarization fails with the following error, and DPA cannot display trend data:

TrendSummarizerManager - Summarize database failed due to [/ by zero]
java.lang.ArithmeticException: / by zero

This issue occurs if the QUICK_POLL_INTERVAL is set to any of the following values:

  • 5 polls per second
  • 3 polls per second
  • 2 polls per second

Resolution/Work-around: Set the QUICK_POLL_INTERVAL value to a less frequent interval:

  1. Click Options.
  2. On the Administration tab, click Advanced Options.
  3. On the DP Instance Options tab, select the database instance that is experiencing the issue.
  4. Click the QUICK_POLL_INTERVAL option.
  5. Choose a less frequent polling interval (1 poll per second, 30 polls per minute, etc.).


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.


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.

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.