Documentation forDatabase Performance Analyzer

DPA 2021.1.872 Release Notes

Release date: March 16, 2021

These release notes were last updated on May 3, 2021.

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

If you are looking for previous release notes for Database Performance Analyzer or the DPA Integration Module (DPAIM), see Previous Version documentation.

New features and improvements in DPA

Return to top

DPA 2021.1.872 provides bug fixes and security enhancements.

For more information about securing your DPA deployment, see DPA Secure Configuration Guide: Best Practices and Recommendations.


New customer installation

Return to top

For information about installing DPA, see the DPA Installation and Upgrade Guide. You can download a free trial from the SolarWinds website.

How to upgrade

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


Fixed issues in DPA 2021.1.872

Return to top

DPA 2021.1.872 fixes the following issues.

Case Number Description
00748237 DPA does not display new feature teasers when the advanced option COOKIE_BASED_POPUPS_ALLOWED is set to False.
00747082 DPA monitoring for PostgreSQL databases no longer fails to start if the DPA polling query returns empty rows. If the query returns empty rows, DPA logs a warning about the statistics that cannot be collected, but basic monitoring continues.
00664216 The JQuery JavaScript library that DPA uses has been updated.
00442447
00448723

In certain situations, when users attempted to restart monitoring on a large number of database instances, monitoring would fail to start and DPA would log messages such as "Task has been rejected by TaskExecutor." This issue has been resolved.


Known issues

Return to top

Database types supported for the DPA repository

Issue: In the Repository Creation Wizard, the line that lists variations of MySQL that are supported for the DPA repository includes MariaDB. However, MariaDB is not supported for the DPA repository. For DPA 2021.1.x, the list of MySQL variations should include only MySQL, Amazon RDS for MySQL, or Amazon Aurora for MySQL. 

Resolution/Work-around: For a complete list of the database types and versions supported for the DPA repository, see the System Requirements for your version of DPA.

The DPA Options page does not open

Issue: If the file containing the DPA SQL authentication password is misconfigured, the DPA Options page does not open. This file can become misconfigured when password protection for DPA features that allow custom SQL is configured, and a password containing '<' or '>' characters was not enclosed with CDATA when it was entered.

Resolution/Work-around:

  1. Open the following file in a text editor:

    <DPA-install-dir>\iwc\tomcat\ignite_config\iwc\security\sqlauth.xml

  2. Look for invalid XML such as the following (shown in red):

    <entry key="sql.authentication.password">
       <![USER_PASSWORD]]<
    >/entry>

  3. Reenter the password enclosed in CDATA, and edit the XML so that it is valid. For example:

    <entry key="sql.authentication.password">
      <![CDATA[MyPasswordWith<SpecialCharacters>]]>
    </entry>

  4. Save the file.

    Changes take effect immediately. The password in the sqlauth.xml file is encrypted the first time DPA prompts a user to enter it.

DPA cannot monitor a PostgreSQL database instance with multiple connection properties

Issue: If you enter multiple connection properties in the JDBC URL field (either in the Registration Wizard or the Update DB Instance Connection Wizard) for a PostgreSQL database instance, DPA cannot monitor the instance. DPA repeatedly attempts to start monitoring the instance, but monitoring fails to start.

Resolution/Work-around: Change the property separator in the COND table in the DPA repository database from & to ;. For details, see this article.

Creating the repository user when creating a MySQL 8.0 repository database

Issue: For MySQL 8.0, the default authentication plug-in has changed from mysql_native_password to caching_sha2_password. If you attempt to create a MySQL 8.0 repository database and allow DPA to create the repository user, the process fails because DPA cannot authenticate a user created with the default option.

Resolution/Work-around:

  1. Create the repository user manually and specify that the mysql_native_password plugin be used to authenticate that user. For example:

    CREATE USER 'userName'@'localhost' IDENTIFIED WITH mysql_native_password BY 'userPassword';

    You can verify user creation by querying the mysql.user table:

    select user,host,plugin from mysql.user;

  2. Grant the required privileges to the user. See the GRANT statements in the script available through the Repository Creation Wizard.
  3. On step 2 of the Repository Creation Wizard, select Provide the repository user. Then enter the user name and password of the user you created.
Alerts stop working after a database instance display name is changed

Issue: If you include a database instance in an alert and then change the display name of the database instance, the alert stops working for that instance and emails are not sent. Even though the instance name appears to be updated in the alert definition, it is not updated on the Alert Status tab.

Resolution/Work-around: Open the alert definition and save it again, without making any changes. Saving the alert definition updates the name on the Alert Status tab.

Validation of the LDAP/AD server host name fails because it doesn't match the subject of the certificate

Issue: Java validates that the host name of the LDAP server matches the LDAP certificate by checking the subjectAlternativeName's dNSName fields of the certificate. If the validation fails, you will see the following error when you are configuring DPA to use AD/LDAP:

The subject of the certificate doesn't match your AD/LDAP server.

Resolution/Work-around: Follow the instructions in this article to resolve the issue.
Adding a distributed AG to a server prevents DPA from monitoring non-distributed AGs on the server

Issue: If DPA is monitoring non-distributed SQL Server Availability Groups (AGs) on a server and you add a distributed AG to the server, DPA stops monitoring the non-distributed AGs.

Resolution/Work-around: Do not add a distributed AG to the server.
Microsoft reports incorrect metric values for SQL Server on Linux

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

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

When you monitor a SQL Server 2019 database instance that runs on a Linux server:

  • The O/S CPU Utilization resource always shows usage at 100%.

Microsoft reports these values.

Resolution/Work-around: Disregard the values that are incorrect on your version of SQL Server. Upgrade to SQL Server 2019 to resolve the issue for the Instance CPU Utilization and O/S Memory Utilization resources.
Monitoring a database instance in the Oracle Public Cloud
Issue: When DPA is monitoring a database instance in the Oracle Public Cloud, it sometimes reports incorrect values.
Resolution/Work-around: DPA does not support monitoring database instances deployed in the Oracle Public Cloud. Use DPA to monitor supported database instance types.
Creating the monitoring user when registering a MySQL 8.0 database instance

Issue: For MySQL 8.0, the default authentication plug-in has changed from mysql_native_password to caching_sha2_password. If you attempt to register a MySQL 8.0 instance and allow DPA to create the monitoring user, registration fails because DPA cannot authenticate a user created with the default option.

Resolution/Work-around:

  1. Create the monitoring user manually and specify that the mysql_native_password plugin be used to authenticate that user. For example:

    CREATE USER 'userName'@'localhost' IDENTIFIED WITH mysql_native_password BY 'userPassword';

    You can verify user creation by querying the mysql.user table:

    select user,host,plugin from mysql.user;

  2. Grant the required privileges to the user. See the GRANT statements in the script available through the Register Instance Wizard.
  3. On step 2 of the Register Instance Wizard, select I'll create the database user. Then enter the user name and password of the user you created.

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
Database-specific mass registration spreadsheets Mass registration spreadsheets specific type of database, such as Oracle or SQL Server, are still included in DPA 2021.1.872, but they will be removed in an upcoming release. When they are removed, mass registrations for any type of database will use the spreadsheet for all database types.
Repository database Support for using Oracle 11.2 as the DPA repository database is deprecated. Oracle 11.2 is still supported as a repository database in the DPA 2021.1.872 release, but support will be removed in an upcoming release.

End of life

Return to top

Version EoL Announcement EoE Effective Date EoL Effective Date
DPA 12.0

June 4, 2020 End-of-Life (EoL) announcement - Customers on DPA version 12.0 or earlier should begin transitioning to the latest version of DPA.

September 2, 2020 End-of-Engineering (EoE) - Service releases, bug fixes, workarounds, and service packs for DPA version 12.0 or earlier will no longer actively be supported by SolarWinds. September 2, 2021 End-of-Life (EoL) - SolarWinds will no longer provide technical support for DPA version 12.0 or earlier.
DPA 11.1

June 4, 2020 End-of-Life (EoL) announcement - Customers on DPA version 11.1 or earlier should begin transitioning to the latest version of DPA.

September 2, 2020 End-of-Engineering (EoE) - Service releases, bug fixes, workarounds, and service packs for DPA version 11.1 or earlier will no longer actively be supported by SolarWinds. September 2, 2021 End-of-Life (EoL) - SolarWinds will no longer provide technical support for DPA version 11.1 or earlier.

See the End of Life Policy for information about SolarWinds product lifecycle phases. For supported versions and EoL announcements for all SolarWinds products, see Currently supported software versions.


Legal notices

Return to top

© 2021 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.