Release date: August 2, 2016
These release notes describe the new features, improvements, and fixed issues in Database Performance Analyzer 10.2. 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
DPA 10.2 offers new features and improvements compared to previous releases of DPA.
MySQL as a repository database
- DPA 10.2 supports using MySQL as the permanent storage location for performance data captured by DPA from the monitored database instances.
- You can use MySQL 5.6.10 and later or 5.7.9 and later as the repository database in DPA 10.2.
Detailed blocking and locking analysis for SQL Server, MySQL, Oracle, and Sybase
- A new Blocking tab shows the Top Root Blockers and Top Waiters to help you quickly identify what is causing the most blocking, and what is waiting the most due to blocking.
- Root blocker data identifies the top of the chain.
Idle blockers for SQL Server, MySQL, Oracle, and Sybase
- A new link is on the Blockers tab for idle blockers. It helps you find the last known activity before the blocking session went idle.
Deadlock support for SQL Server 2012 and later
- A new Deadlocks tab helps you correlate performance issues with the occurrence of deadlocks. You can also click a deadlock to see its details, including information about the deadlock survivors and victims.
Active Directory/LDAP configuration wizard
- Use the new wizard to configure DPA with your company's directory service so users can log in to DPA using their domain accounts.
- This easy-to-use wizard replaces the previous file-editing method, and helps you succeed in configuring DPA with your AD/LDAP server.
- After configuration, you can configure domain user logins by adding domain groups to the User Administration page.
Support for SQL Server 2016
- You can use SQL Server 2016 as the repository database.
- You can register a SQL Server 2016 database instance for monitoring.
New customer installation
For information about installing DPA 10.2, see the DPA 10.2 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 10.2 requires JRE 1.8. If you configured DPA to use an external JRE, DPA will verify it is version 1.8 or later. If the verification fails, DPA will use the JRE included with the installation.
- Integration with Orion: If DPA is installed on the same server as NPM or SAM, see this KB article for special upgrade instructions.
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.
DPA <Version> fixes the following issues.
DPA 10.2.579 fixes the following issue:
|1029422||Fixed an issue where emails were not sent using the Default Mail Server configuration.|
DPA 10.2 fixes the following issues:
|887726||In time zones where daylight saving occurs at 12 midnight, the cleaner job no longer fails and the dashboard charts will update after a time change.|
|910451||Fixed an issue where DPA may use a lower SSL security level if the connection to a SQL Server fails and the certificate of the server is not signed by a trusted certificate authority. This applies to creating a SQL Server repository database, and registering and updating the connection to a SQL Server monitored database instance.|
|914176||The Test Alert function now works for the following: Single Resource Metric, Metric Category, Custom alert with select #FREQUENCY#, and Custom Procedure.|
|909435||Fixed an issue with database instance sorting on the home page.|
|919007||Fixed an issue where the embedded email messages did not display properly.|
|929218||Fixed an issue where emails sent from the Analyze Query section did not display properly.|
|926047||Fixed an issue where the Disk I/O Access Time (ms) metric for Sybase was calculated incorrectly.|
|936210||DPA no longer adds an unnecessary self-signed certificate to the server trust store after upgrading DPA.|
|905196||Registration of a DB2 database instance no longer fails of the HADR with BLOCKNONLOGGED option is turned on.|
|953394||Custom Alerts that use
|965845||Plan Text dialog is properly formatted.|
|The Storage I/O tab displays information correctly for time zones where daylight saving time occurs at 12 midnight.|
|-||Default Thresholds on Resource Metrics were modified or removed to avoid potential false positives.|
|Parallel execution counts are not included in SQL statistics for Oracle 9 and later.|
994395, 999143, 999641
|New system identifier is generated for the DPA integration service to avoid identifier collision with Orion 2016.1.|
MySQL metric calculations
DPA 10.2 calculates two MySQL metrics as values instead of rates:
- 10.0 - 10.1: Connection Attempts, Threads Counted
- 10.2: Connection Attempts Count, Threads Created Count
These metrics are no longer calculated as rates. DPA now displays the number of connection attempts or created threads for a given time period.
You must update your thresholds for these metrics on the Resources tab.
|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
|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.|
|Orion integration errors after encryption scheme change|
|Issue: If you change the encryption scheme in DPA Password Encryption Settings, certain features in the DPA in Orion integration stop working. The Orion password remains encrypted, but it is not re-encrypted after you change the encryption scheme.|
|Resolution/Work-around: Re-establish the integration to Orion after changing the encryption scheme.|
|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.|
|No special characters in email addresses|
|Issue: DPA considers email addresses with special characters as invalid. These characters include:
|Resolution/Work-around: Do not use these characters.|
|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
|Root blockers memory consumption|
|Issue: DPA may require more memory to summarize root blocking data for intervals that contain many blocking events.|
|Resolution/Work-around: Follow the instructions in this article to increase the amount of heap memory allocated to DPA.|
End of support
This version of Database Performance Analyzer no longer supports the following platforms.
|Repository database||Oracle 10g|
|Monitored database instances||
|UNIX operating systems||
|Web browsers||Internet Explorer 9 and 10|
If you install DPA 10.2 on the Solaris operating system, Solaris 10 Update 9 (or Oracle 11) or later is required.
© 2019 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.
SOLARWINDS DISCLAIMS ALL WARRANTIES, CONDITIONS, OR OTHER TERMS, EXPRESS OR IMPLIED, STATUTORY OR OTHERWISE, ON THE DOCUMENTATION, INCLUDING WITHOUT LIMITATION NONINFRINGEMENT, ACCURACY, COMPLETENESS, OR USEFULNESS OF ANY INFORMATION CONTAINED HEREIN. IN NO EVENT SHALL SOLARWINDS, ITS SUPPLIERS, NOR ITS LICENSORS BE LIABLE FOR ANY DAMAGES, WHETHER ARISING IN TORT, CONTRACT OR ANY OTHER LEGAL THEORY, EVEN IF SOLARWINDS HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
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.