DPA 12.1.701 Release Notes

Release date: May 15, 2019

These release notes describe the fixed issues in Database Performance Analyzer 12.1.701. 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.

Fixed issues

DPA 12.1.701 fixes the following issues.

Case number Description

00246472, 00287965

Updating the ActiveMQ library version used in DPA 12.1 resulted in intermittent data collection problems. DPA 12.1.701 resolves these issues by reverting to the ActiveMQ library version used in DPA 12.0.

00283334

Links from DPA Central to remote DPA servers work correctly.

00266170

The query to retrieve the status of SQL Server availability groups (AGs) no longer times out in deployments with a large number of AGs, and the AG status is displayed correctly.

00278967, 00280076

When DPA is running on Amazon Web Services and the embedded mail server is used, DPA now displays trends charts, storage I/O, and reports as expected.

00306712

DPA 12.1.701 includes security improvements.

New customer installation

Return to top

For information about installing DPA 12.1.701, see the DPA Installation Guide.

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

Attempting to launch DPA on a Linux server returns a Status 500 Internal Server Error

Issue: When DPA is installed on a Linux server, attempting to start it returns a Status 500 Internal Server Error. The 'Root Cause' section of the error message includes:

Error creating bean with name 'displayOptionsController'

This occurs because the fonts that DPA requires are no longer available from the JDK.

Resolution/Work-around: Install the required fonts. See this article for details.

 

DPA does not support MySQL 8.0
Issue: MySQL 8.0 is not supported for use as a DPA repository, and DPA cannot monitor MySQL 8.0 database instances.
Resolution/Work-around: Use DPA with supported versions of MySQL.

 

Incorrect metric values reported for SQL Server on Linux

Issue: When you are monitoring a SQL Server database instance that runs on a Linux server:

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

SQL Server reports these values.

Resolution/Work-around: Disregard these metric values.

 

Attempting to run a report returns the error DPA Unable to generate the chart

Issue: When the DPA server is running RHEL 7.4 (or its distributions, such as Oracle Linux 7.4), DPA returns the following error when you try to run a report:

DPA Unable to generate the chart: java.lang.ArrayIndexOutOfBoundsException: 0

Resolution/Work-around: Follow the instructions in this article to change the default font used by RHEL 7.4.

 

Incorrect execution counts for SQL statements
Issue: When SQL Server purges statistics from the previous cached query plan for a SQL Statement from the master.sys.dm_exec_query_stats table, the execution count that DPA shows can be incorrect. This count can be extremely high, and doesn't match the execution count retrieved by querying the DPA repository.
Resolution/Work-around: Disregard the incorrect execution counts.

 

DPA repository creation on Azure SQL fails when the user name contains an @ symbol

Issue: When you attempt to create the DPA repository on an Azure SQL database, repository creation fails if you enter the user name in a format that contains an @ symbol (for example, dpa@myserver) on the Enter Repository Connection Information panel. For more information see this KB article.

Resolution/Work-around: Enter the user name in a format without the @ symbol. For example, instead of dpa@myserver, enter only dpa.

 

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
Repository database Support for using SQL Server 2012 as the DPA repository database is deprecated. You can still use SQL Server 2012 as the repository database for DPA 12.1.701, but support will be removed in an upcoming release.
Monitored database instances

Support for monitoring SQL Server 2008 database instances is deprecated. You can still monitor SQL Server 2008 database instances with DPA 12.1.701, but this functionality will be removed in an upcoming release.


End of life

Return to top

Version EoL Annoucement EoE Effective Date EoL Effective Date
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

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