Documentation forDatabase Performance Analyzer

Database Performance Analyzer 12.1 Release Notes

Release date: March 12, 2019

These release notes describe the new features, improvements, and fixed issues in Database Performance Analyzer 12.1. 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

Return to top

DPA 12.1 offers new features and improvements compared to previous releases of DPA.

Anomaly detection

DPA makes it easy to find the big bars that represent long waits. But in some cases, a big bar is not a problem. The wait time is normal and expected. What you need to know is when something changes and wait times suddenly become much longer than normal.

DPA 12.1 introduces an anomaly detection algorithm to identify unexpected increases in wait time. DPA collects historical data and uses it to "learn" what normal is. DPA's proprietary algorithm makes predictions based on this data. The predictions take into account the day of the week and the time of day. (For example, the expected wait time for 2 PM on a Wednesday might be different than the expected wait time for 2 AM on Saturday.)

A new alert and an updated wait time meter (described below) let you know when wait times are significantly higher than expected. When you view information about the database instance that is experiencing unexpectedly high wait times, the Anomaly Detection chart below the Top SQL Statements chart shows you when anomalies occurred.

You can drill in to a day for a more detailed view. Click the name or hash value of a query that ran during an interval with high wait times to open the Query Details page, where you can view historical information about the query and get statistics for the selected time period.

DPA also detects when wait times are lower than expected. For these time periods, the bar is below the baseline on the chart. Lower wait times are not assigned a Warning or Critical status, and DPA does not alert on them.

>> Learn more about anomaly detection


DPA 12.1 includes a REST API, which can be used to automate management of the DPA server. You can use the API to securely connect to the DPA server and retrieve information or provision database resources. For example, you can make API calls to:

  • Register or unregister a database instance
  • Allocate or deallocate licenses
  • Start or stop monitoring
  • Add or remove annotations
  • Get information about licenses, monitored database instances, and annotations

>> Learn more about the DPA REST API

Wait time meter changes

  • The color of the wait time meter is based on DPA's anomaly detection algorithm. When a wait time meter is yellow or red, it indicates that wait times for the associated database instance are significantly higher than expected for the current week day and time period.

  • The wait time meter provides much more current status information for each database instance. The status is calculated every 10 minutes. The wait time meter indicates the amount of wait time during the six most recent 10-minute intervals (a rolling one-hour time period).

    In previous versions, the status was updated daily. Therefore, unusually long waits at 3 AM (for example) would cause the wait meter to stay yellow or red for the rest of the day, even though wait times were no longer high.

Alerting improvements

  • Values that are included in DPA alerts can now contain up to four decimal places. With this change, you can configure sub-second thresholds for DPA alerts.
  • A new alert, Database Instance Wait Time Anomaly, is available. This alert uses DPA's anomaly detection algorithm. It is triggered if the wait time of an instance was abnormally high during the most recently completed hour.

Redesigned Management Options page

The tabs have been removed from the Management Options page. The Monitor Setup, Administration, and Support options are all shown on one page for easier access.

Changes to system requirements

DPA 12.1 adds support for the following versions:

Monitored database instances
  • Oracle 18.3.x
  • Microsoft SQL Server 2017 on Amazon RDS
Repository database
  • Oracle 18.3.x (on-premises only)
  • Microsoft SQL Server 2017 on Linux
DPA server OS
  • Windows Server 2019
Virtual environment
  • vCenter Server 6.7
  • ESX/ESXi 6.7

For a complete list of supported platforms, see the DPA 12.1 system requirements.

New customer installation

Return to top

For information about installing DPA 12.1, see the DPA Installation and Upgrade Guide.

Before you upgrade!

If you are upgrading from a previous version, be aware of the following considerations:

  • If you have specified that DPA use a Java installation other than the default version that DPA installs, you must update it to a supported version. (See End of Support for more information.)
  • In previous versions of DPA, SQL Server 2005 repository databases functioned (even though they were not supported). In DPA 12.1, SQL Server 2005 repository databases will no longer function. If you are still using a SQL Server 2005 database as the DPA repository, you must upgrade to a supported repository database version before you upgrade to DPA 12.1.

How to upgrade

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

Fixed issues

Return to top

DPA 12.1 fixes the following issues.

Case number Description


When a SQL Server database is issuing queries with table variables, DPA no longer returns errors similar to Insert failed for CON_INDEX_ANALYSIS_350.

00218510, 00217926, 00190095, 00197874

Table Tuning Advisors no longer display internal server errors when a table includes more than 2,147,483,647 rows, or when a plan step uses over 4 billion rows in the query.


DPA is able to monitor an Oracle database when PLANPOLL_ENABLED is set to False.

00206303, 00200609, 00203379

Table Tuning Advisors no longer display internal server errors when the DPA repository is on a MariaDB database.

Using MariaDB as the DPA repository database is not supported. SolarWinds encourages users to move the DPA repository to a supported version of MySQL. For more information, see the DPA 12.1 System Requirements.


If the server name for the primary replica in a SQL Server availability group (AG) is reported as NULL, DPA is now able to retrieve the correct name and continue monitoring the AG.


A special character has been removed from default-metrics-queries.xml. In some environments, this character prevented DPA from displaying CPU, page life, or read/write latency metrics.


Index analysis no longer fails with a null pointer exception error when a dot (.) is used in a table or database name.


Activating a license offline now works as expected.


Information is no longer missing from the Top Plans by SQL report.

1010458, 1325085

An issue with the DPA plan poll that caused DPA to return the following error and stop monitoring a database instance has been fixed:

Duplicate Key in object 'ignite.CONSPA_X'.


The performance of DPA's index analysis and table tuning advisor features have been improved. In some cases, users were reporting high CPU usage and wait times on the DPA server, performance degradation on monitored instances, and Table Tuning Advisors showing errors such as Data not found.

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

End of support

Return to top

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

Type Details
DPA server OS

Out-of-the box support for installing DPA on an Oracle Solaris operating system is no longer supported. The DPA installer does not install the Java JRE required by Oracle Solaris. However, you can manually install the required Java JRE and specify which Java installation DPA should use.

For a list of supported operating systems, see the DPA 11.1 system requirements.

Monitored databases DPA no longer monitors Oracle 9.x database instances.

DPA 12.1 does not run with JDK 8 or earlier versions. By default, DPA installs and uses OpenJDK 11, but you can also use Oracle JDK 11.

If you have specified that DPA use a Java installation other than the default version that DPA installs, you must update it to a supported version. See either of the following articles for instructions:

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.


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.