Documentation forDatabase Performance Analyzer

DPA 2023.2.100 release notes

Release date: July 18, 2023

Here's what's new in Database Performance Analyzer 2023.2.100.

Learn more

New features and improvements in DPA

Additions to supported platforms and monitored instances

DPA 202.3.2.100 adds support for the following:

  • The DPA repository database can be created on Amazon Aurora for MySQL-compatible 8.0.

  • DPA can monitor the following database instances:

    • PostgreSQL 15
    • Postgres EDB 15
    • Amazon Aurora for MySQL-compatible 8.0

See the End of support section for information on removals. For information about all supported platforms and instances, see the System requirements and Database instances DPA can monitor.

Changes to resource metrics categories

In previous versions, the License Compliance tab displayed metrics related to the number of cores used and the number of connections (connected devices, users, and sessions).

DPA 2023.2.100 no longer includes the License Compliance tab. To categorize the information more clearly, metrics related to the number of connections are displayed on the Connections tab. The Core Count metric is displayed on the CPU tab.

New log file for DPA Central

The following file includes log entries that can help troubleshoot issues with DPA Central:

DPA-Install-Dir\iwc\tomcat\logs\central.log

Return to top

Fixes

Case number Description
01318760, 01174998, 01179091

Index advisors for Oracle database instances no longer recommend creating an index that already exists, and they do not provide index creation scripts that include table columns that do not exist.

N/A

DPA no longer runs out of memory when monitoring a PostgreSQL instance that is running large queries.

01312350

When you create an Oracle repository database, the privileged user (which creates the DPA repository user) no longer requires the UNLIMITED_TABLESPACE privilege. The privileged user must be granted QUOTA UNLIMITED on the tablespace where DPA will store performance data.
01333338

Previous versions of DPA did not consistently convert the display name to uppercase when connection information for a monitored SQL Server instance changed. Failure to convert the display name to uppercase caused connection issues.

DPA now consistently converts the display name to uppercase.

00111644, 00221947, 01270821

DPA 2023.2.100 does not use any of the deprecated SNAP* functions previously used to collect information from Db2 instances. These functions were causing IBM Db2 instances to have intermittent connection issues.

Because of this change:

  • On the Real Time Sessions page, the Sessions tab no longer displays the following columns:

    • INPUT_DB_ALIAS
    • CLIENT_DB_ALIAS
    • DB_NAME

  • On the Real Time Sessions page, the Locking tab no longer displays the DB_NAME column.

  • When you upgrade to DPA 2023.2.100 or later, you must update the permissions of the DPA monitoring user for each Db2 instance. See Before you upgrade for details.
N/A When a user with read-only privileges accesses the Reports page, the user can view reports as expected. An error message is not displayed, and the option to create a report is not enabled.
N/A This release includes security enhancements.

SolarWinds CVEs

SolarWinds would like to thank our Security Researchers below for reporting on the issue in a responsible manner and working with our security, product, and engineering teams to fix the vulnerability.

CVE-ID Vulnerability Title Description Severity Credit
CVE-2023-33231 XSS in SolarWinds Database Performance Analyzer (DPA) 2023.2 XSS attack was found to be possible in DPA 2023.2 due to insufficient input validation. High Shashank Chaurasia

Return to top

Installation or upgrade

For new installations, you can download the installer from the SolarWinds website or from the Customer Portal. For more information, see the DPA Installation and Upgrade Guide.

For upgrades, 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.

Return to top

Before you upgrade!

Before you upgrade, review the following sections to ensure continuous monitoring and accessibility.

Upgrading from DPA 2023.1 or earlier

If you are upgrading from a version earlier than DPA 2023.2.1, be aware that for security purposes, DPA 2023.2.1 and later no longer supports HTTP connections. Before you upgrade:

Update the permissions of the DPA monitoring user for each Db2 instance with privileges required for DPA 2023.2.100

If you monitor IBM Db2 database instances, DPA 2023.2.100 requires additional privileges to collect information from updated Db2 dictionaries and stored procedures.

DPA 2023.2.100 replaces the remaining deprecated SNAP* functions that were still present in DPA 2023.2.1. Previous DPA versions used these functions to monitor Db2 database instances. Because of this change, the DPA monitoring user requires additional privileges to collect information from updated Db2 dictionaries and stored procedures. In addition to SYSADM permissions, the user requires EXECUTE privileges on additional tables.

To monitor Db2 instances with DPA 2023.2.100 and later versions, modify the monitoring user's permission on each Db2 instance.

The required permissions can be granted in Db2 10.5 and later. DPA 2023.2.100 does not support monitoring earlier versions of Db2.

  1. Run the following commands to grant the DPA monitoring user EXECUTE privileges on the required tables:

    • If you are upgrading from DPA 2023.1 or earlier, run the following commands to grant all required EXECUTE privileges:

      grant execute on function SYSPROC.MON_GET_DATABASE to userName;
grant execute on function SYSPROC.MON_SAMPLE_WORKLOAD_METRICS to userName;
grant execute on function SYSPROC.MON_GET_ACTIVITY to <USER_NAME>;
grant execute on function SYSPROC.MON_GET_BUFFERPOOL to <USER_NAME>;
grant execute on function SYSPROC.MON_GET_TABLESPACE to <USER_NAME>;
grant execute on function SYSPROC.MON_GET_TRANSACTION_LOG to <USER_NAME>;
grant execute on function SYSPROC.MON_GET_APPL_LOCKWAIT to <USER>;
grant execute on function SYSPROC.MON_GET_LOCKS to <USER>;
grant execute on function SYSPROC.MON_FORMAT_LOCK_NAME to <USER>;
grant execute on function SYSPROC.MON_GET_UNIT_OF_WORK to <USER>;
grant execute on function SYSPROC.MON_GET_AGENT to <USER>;
grant execute on function SYSPROC.MON_GET_PKG_CACHE_STMT to <USER>;
grant execute on function SYSPROC.MON_GET_CONNECTION to <USER>;

    • If you are upgrading from DPA 2023.2.1 and you already granted the additional privileges required by that version, run the following commands to grant the additional EXECUTE privileges required by DPA 2023.2.100:

      grant execute on function SYSPROC.MON_GET_UNIT_OF_WORK to <USER>;
grant execute on function SYSPROC.MON_GET_AGENT to <USER>;
grant execute on function SYSPROC.MON_GET_PKG_CACHE_STMT to <USER>;
grant execute on function SYSPROC.MON_GET_CONNECTION to <USER>;

  2. To verify that the permissions were applied correctly, run the following command:

    select substr(authid,1,20) as authid
    , authidtype
    , privilege
    , grantable
    , substr(objectschema,1,12) as objectschema
    , substr(objectname,1,30) as objectname
    , objecttype
from sysibmadm.privileges
where objectschema ='SYSPROC' AND AUTHID='<USER_NAME>';

Return to top

Known issues

DPA does not always use the Microsoft JDBC driver by default

When you register a database instance for monitoring, DPA should use the Microsoft JDBC driver by default. However, it uses the jTDS JDBC driver by default if the system.properties file does not contain the following entry:

com.confio.ignite.jdbc.sqlserver.useJtdsDriver=false

This missing configuration is likely to happen on DPA servers where older versions of DPA were initially installed, before DPA began using the Microsoft Driver.

Resolution or Workaround: Open the system.properties file in a text editor, and determine if it contains the entry above. If not, manually add it and save the file.

PostgreSQL OS CPU utilization not showing data on a Windows installation

When PostgreSQL is installed on a server with a Windows operating system, the O/S CPU Utilization resource metric in DPA does not display any data. It displays the message Chart doesn't have data collected for selected time period.

If PostgreSQL OS CPU utilization data is missing in other environments, make sure the system_stats extension is installed. For instructions, see Register a PostgreSQL database instance and prepare for monitoring.

Resolution or Workaround: None.

REST API does not work when you access DPA with SAML login credentials

If you access DPA with SAML login credentials and you generate a refresh token, the following message is displayed when you attempt to use that refresh token to access the REST API:

You are not authorized to perform this action. Contact your DPA administrator.

Resolution or Workaround: Access DPA with a local login when you generate the refresh token.

Importing an alert definition without the associated database assignment rule

In some situations, the log file shows the status of an imported alert definition as both Imported and Failed. This occurs when the alert definition uses a database assignment rule, but the rule was not imported and did not already exist on the server.

The two statuses indicate that the alert definition was imported but the attempt to associate the database assignment rule failed.

Resolution or Workaround: When you import an alert definition that uses a database assignment rule, either import the rule or ensure that it already exists on the server.

If you imported an alert definition and the associated rule is missing, you must edit the alert definition to specify the database instances. (You can specify instances by manually selecting them or by applying a rule.)

Return to top

End of life

Version EoL Announcement EoE Effective Date EoL Effective Date
DPA 2022.2

April 18, 2023 End-of-Life (EoL) announcement - Customers on DPA version 2022.2 or earlier should begin transitioning to the latest version of DPA.

 August 18, 2023 End-of-Engineering (EoE) - Service releases, bug fixes, workarounds, and service packs for DPA version 2022.2 or earlier will no longer actively be supported by SolarWinds. April 18, 2024 End-of-Life (EoL) - SolarWinds will no longer provide technical support for DPA version 2022.2 or earlier.
DPA 2022.1

January 18, 2023 End-of-Life (EoL) announcement - Customers on DPA version 2022.1 or earlier should begin transitioning to the latest version of DPA.

 April 18, 2023 End-of-Engineering (EoE) - Service releases, bug fixes, workarounds, and service packs for DPA version 2022.1 or earlier will no longer actively be supported by SolarWinds. April 18, 2024 End-of-Life (EoL) - SolarWinds will no longer provide technical support for DPA version 2022.1 or earlier.
DPA 2021.3

October 18, 2022 End-of-Life (EoL) announcement - Customers on DPA version 2021.3 or earlier should begin transitioning to the latest version of DPA.

 January 18, 2023 End-of-Engineering (EoE) - Service releases, bug fixes, workarounds, and service packs for DPA version 2021.3 or earlier will no longer actively be supported by SolarWinds. January 18, 2024 End-of-Life (EoL) - SolarWinds will no longer provide technical support for DPA version 2021.3 or earlier.
DPA 2021.1

October 18, 2022 End-of-Life (EoL) announcement - Customers on DPA version 2021.1 or earlier should begin transitioning to the latest version of DPA.

 January 18, 2023 End-of-Engineering (EoE) - Service releases, bug fixes, workarounds, and service packs for DPA version 2021.1 or earlier will no longer actively be supported by SolarWinds. January 18, 2024 End-of-Life (EoL) - SolarWinds will no longer provide technical support for DPA version 2021.1 or earlier.
DPA 2020.2

October 18, 2022 End-of-Life (EoL) announcement - Customers on DPA version 2020.2 or earlier should begin transitioning to the latest version of DPA.

 January 18, 2023 End-of-Engineering (EoE) - Service releases, bug fixes, workarounds, and service packs for DPA version 2020.2 or earlier will no longer actively be supported by SolarWinds. January 18, 2024 End-of-Life (EoL) - SolarWinds will no longer provide technical support for DPA version 2020.2 or earlier.

See the End of Life Policy for information about SolarWinds product life cycle phases. To see EoL dates for earlier DPA versions, see DPA release history.

Return to top

End of support

This version of Database Performance Analyzer no longer supports the following platforms and features.

Type Details
Monitored database instances Monitoring IBM Db2 10.1 database instances is no longer supported.

Return to top

Deprecation notice

The following platforms and features are still supported in the current release. However, they will be unsupported in a future release. Plan on upgrading deprecated platforms, and avoid using deprecated features.

Type Details
DPA server OS Installing DPA on a server with a Windows Server 2012 R2 operating system is still supported in 2023.2.100, but support will be removed in an upcoming release.

Return to top

Legal notices

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