Updated March 14, 2017
These release notes describe the new features, improvements, and fixed issues in this release. They also provide information about upgrades and describe workarounds for known issues.
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:
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.
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.
For information about installing DPA, see the DPA 11.0 Administrator Guide.
If you are upgrading from a previous version, be aware of the following considerations:
If you are upgrading from a previous version, use the following resources to plan and implement your upgrade:
DPA 11.0 fixes the following issues:
|1091237||Fixed an issue where DPA resource utilization was high during Stats Poll for Amazon RDS for Oracle databases.|
|929798||Added the secure attribute to the DPA userName cookie.|
|929798||Added Cross-site request forgery protection.|
|922107||Fixed an issue where DPA considered email addresses with special characters as invalid.|
|-||Fixed an issue with changing the encryption scheme in DPA Password Encryption Settings, and its effect on certain features in the DPA Integration Module.|
|Fixed an issue with incorrect date and time information.|
|1054883||Fixed an issue where the message body of a Deadlock Detail email was not transmitting.|
|1054943||Upgraded Tomcat to 8.0.36 to solve a FileUpload issue.|
|1048389||Text in tuning advice emails is no longer truncated.|
|1047631||Fixed an issue where plan advice only showed 10 plans for all previous days.|
|1041183||Fixed an issue where the queries for count, blocking, and locking could cause the Current page to hang.|
|1035158||Improved the error message displayed when unregistering a monitored database that is not running.|
|1031174||Added options to hide the domain name, DPA version, and repository name from the login screen.|
|1022154||Added input scrubbing for the Domain Name and custom Port fields in the AD/LDAP Configuration wizard.|
|1004881||Added a Tomcat option to prevent clickjacking.|
|876043||Fixed an issue where the text poll for SQL Server was truncated to 8000 characters.|
|1125981||Fixed an issue with MySQL Live plans on MariaDB.|
Issue: Using the Internet Explorer compatibility view may cause DPA to function incorrectly.
Workaround: Do not use IE compatibility view, or use another supported web browser.
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.
Workaround: Follow the instructions in this KB article.
Issue: The Blocking tab becomes unresponsive if there are more than 32,767 records on the Real Time Session page.
Issue: The Update Connection Info wizard requires port information for SQL Server, even if it is instance-based.
Workaround: Enter the correct port.
Issue: Stats Poll on SQL Server does not work correctly when counts disappear and reappear from
Issue: If your repository database is MySQL, DPA drops the
CON_ALERT_HISTORY_RESULT tables during the upgrade due to column resizing.
Workaround: Follow the instructions in this article to back up your repository before upgrading, and restore your alert history after upgrading.
Issue: DPA may require more memory to summarize root blocking data for intervals that contain many blocking events.
Workaround: Follow the instructions in this article to increase the amount of heap memory allocated to DPA.
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.
Workaround: Manually override the automatic PDB grouping.
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.
Workaround: Restart DPA.
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.
Workaround: Upgrade to MySQL 5.6.25 or later.
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.
Workaround: Upgrade to the latest service release of 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 may not run properly because it will fail to create the Extended Events Session.
Workaround: Update the
DEADLOCK_POLL_SQL_SERVER_SESSION_NAME advanced option value from
system_health for the affected instances.
Issue: In a Turkish environment where the hostname contains an uppercase "i", DPA integration to Orion fails.
Workaround: Change the Orion hostname to lowercase in the Websites table.
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.
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.
Workaround: Lower the value of the
CLEAN_DAYS_OF_DETAIL advanced option.
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
Workaround: 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.
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
For information about supported versions of SolarWinds products, see this article.
SolarWinds' policy is to support the current and two previous versions of DPA. SolarWinds does not support DPA 10.0 and earlier.
© 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 and documentation are and shall remain the exclusive property of SolarWinds and its respective licensors.
SOLARWINDS DISCLAIMS ALL WARRANTIES, CONDITIONS OR OTHER TERMS, EXPRESS OR IMPLIED, STATUTORY OR OTHERWISE, ON SOFTWARE AND DOCUMENTATION FURNISHED HEREUNDER INCLUDING WITHOUT LIMITATION THE WARRANTIES OF DESIGN, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE, AND NONINFRINGEMENT. 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 and other SolarWinds marks, identified on the SolarWinds website, as updated from SolarWinds from time to time and incorporated herein, are registered with the U.S. Patent and Trademark Office and may be registered or pending registration in other countries. All other SolarWinds trademarks may be common law marks or registered or pending registration in the United States or in other countries. All other trademarks or registered trademarks contained and/or mentioned herein are used for identification purposes only and may be trademarks or registered trademarks of their respective companies.