Documentation forDatabase Performance Analyzer

DPA 2019.4.1058 Release Notes

Release date: February 2021

These release notes describe the new features in Database Performance Analyzer 2019.4.1058. 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.

New features and improvements in DPA

DPA 2019.4.1058 includes security enhancements and is signed with a new digital code-signing certificate.

For more information on the additional steps SolarWinds is taking to improve our security posture and policies please reference this blog by SolarWinds President and CEO Sudhakar Ramakrishna.


New customer installation

Return to top

For information about installing DPA 2019.4, 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:


Known issues

Return to top

Monitoring Db2 9.7 databases

Issue: When you attempt to monitor a Db2 9.7 database instance with DPA 2019.4, monitoring does not start and no data is returned.

Resolution/Work-around: To monitor a Db2 9.7 database instance, complete the following steps:

  1. From the DPA menu, click Options.
  2. Under Administration > Configuration, click Advanced Options.
  3. Click the DB Instance Options tab, and then select the Db2 9.7 database instance from the drop-down menu.
  4. In the upper-right corner, select Support Options.
  5. Click QUICKPOLL_FAKE_FROM_CLAUSE.

    The Edit Option dialog box opens.

  6. Enter the following in the New Value box and click Update:

    TABLE
    (snapshot_appl_info(CAST(NULL AS VARCHAR(1)),
    -2)) AS ai
    INNER JOIN TABLE
    (snapshot_statement(CAST(NULL AS VARCHAR(1)),
    -2)) AS s ON
    s.agent_id = ai.agent_id
    INNER JOIN TABLE
    (snap_get_appl_info_v95(CAST(NULL AS VARCHAR(1)),
    -2)) ai95 ON
    s.agent_id = ai95.agent_id
    AND ai.agent_id = ai95.agent_id
    WHERE
    s.agent_id = ai.agent_id
    AND s.stmt_type <> 4
    AND stmt_stop IS NULL
    AND ai.appl_id <> APPLICATION_ID()
    AND is_system_appl = 0
    AND ai95.agent_id = ai.agent_id
    AND ai95.agent_id = s.agent_id
    AND ai.appl_status NOT IN (0,
    2,
    4)
    ORDER BY
    agent_id,
    stmt_start DESC,
    stmt_type
    --
  7. Restart DPA.
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.
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.
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.
Real Time Sessions page

Issue: When you are monitoring an Azure SQL Managed Instance (ASMI) that is registered via the public endpoint, some of the connections are closed after three minutes. If you turn the DPA monitor off, open the Real Time Sessions page, and then refresh the page after three to four minutes, the Real Time Sessions page displays the following SQL Server exception:

The connection is closed.

Resolution/Work-around: If you experience this issue, complete the following steps to configure DPA to recreate connections every three minutes:

  1. Open the following file in a text editor:

    <dpaHome>\iwc\tomcat\ignite_config\idc\system.properties

  2. Update the value of the following parameter to 180000:

    com.confio.iwc.realtime.service.datasource.map.timeout=180000

    This is the timeout for idle connections, in milliseconds.

  3. Save the file and restart DPA.
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.

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
Self-managed DPA server Support for installing DPA on a self-managed Windows Server 2012 server is deprecated. Installing DPA on a Windows Server 2012 is still supported in the DPA 2019.4 release, but support will be removed in an upcoming release.
VMware DPA will be ending support for VMware vCenter Server 6.0 and VMware ESX/ESXi Host 6.0 in an upcoming release. DPA 2019.4 still supports VMware 6.0, but SolarWinds encourages users to upgrade to VMware 6.5 or 6.7 at their earliest convenience.

End of support

Return to top

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

Type Details
Repository database

SQL Server 2012 is no longer supported as the DPA repository database.

Monitored database instances

DPA can no longer be used to monitor SQL Server 2008 database instances.


End of life

Return to top

Version EoL Annoucement EoE Effective Date EoL Effective Date
DPA 11.0 November 5, 2019 End-of-Life (EoL) announcement - Customers on DPA version 11.0 or earlier should begin transitioning to the latest version of DPA. March 7, 2020 End-of-Engineering (EoE) - Service releases, bug fixes, workarounds, and service packs for DPA version 11.0 or earlier will no longer actively be supported by SolarWinds. March 7, 2021 End-of-Life (EoL) - SolarWinds will no longer provide technical support for DPA version 11.0 or earlier.
DPA 10.2 August 28, 2018 End-of-Life (EoL) announcement - Customers on DPA version 10.2 or earlier should begin transitioning to the latest version of DPA. November 26, 2018 End-of-Engineering (EoE) - Service releases, bug fixes, workarounds, and service packs for DPA version 10.2 or earlier will no longer actively be supported by SolarWinds. November 26, 2019 End-of-Life (EoL) - SolarWinds will no longer provide technical support for DPA version 10.2 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.