Submit a ticketCall us

Training ClassSign up for Network Performance Monitor (NPM) and Scalability instructor-led classes

Attend our instructor-led classes, provided by SolarWinds® Academy, to discuss the more advanced monitoring mechanisms available in NPM as well as how to tune your equipment to optimize its polling capabilities. NPM classes offered:
NPM Custom Monitoring and Polling
Orion Platform Scalability

Reserve your seat.

Home > Success Center > Database Performance Analyzer (DPA) > DPA Documentation > DPA 12.0 Release Notes

DPA 12.0 Release Notes



Last updated: August 28, 2018

These release notes describe the new features, improvements, and fixed issues in DPA 12.0. They also provide information about upgrades and describe workarounds for known issues.

New features and improvements

Query performance analysis

DPA 12.0 intelligently assembles the most relevant data about a query and displays it in one place: the new Query Details page. This page includes the following information:

  • A chart at the top of the page shows the query's execution time for the selected time period, color-coded by the type of wait. As you scroll to view other data on the page, this chart remains visible so you can correlate query wait times with other metrics during the same time period. 
  • The Query Advisors section shows the latest advice for the specified time period. Click the links to display detailed descriptions and resolution suggestions.
  • If any table tuning advisors included information about this query, you can click through for aggregated information about the table and all inefficient queries that ran on it. 
  • Metrics charts display additional data to help you find the root cause of performance issues. DPA uses the predominant type of wait to automatically select the most relevant charts. However, you can manually add other charts.  

>> Learn more about query performance analysis

Table tuning advisors

This feature is available for Oracle, SQL Server (2008 and above), and Azure SQL databases.

You must consider many factors when you're determining how to improve the performance of an inefficient query—that is, a query that reads a large number of rows but returns relatively few. To help you make informed decisions, DPA 12.0 introduces table tuning advisors. Each day, DPA identifies tables that had inefficient queries run against them. For each table, the Table Tuning Advisor page displays aggregated information about the inefficient queries, the table structure, and any existing indexes. This information can help you answer questions such as:

  • Which steps should I focus on when I review the plan for the query?
  • How many indexes currently exist on the table and what do they look like?
  • Can I add an index to improve performance?
  • Are statistics stale?
  • How much churn (inserts, updates, deletes) does the table undergo?

Use the information assembled by the Table Tuning Advisor to determine the most effective options for improving performance. 

>> Learn more about table tuning advisors

Aggregated tuning advice

The new Tuning tab displays all query advisors and table advisors for the selected database instance, so you can access both query and table tuning advice from one place. The advisors are ranked, and the most serious issues are listed first.  

Blocking session data in PerfStack

If you have integrated DPA with the Orion Platform, you can now add information about blocking sessions to PerfStack charts. No DPAIM upgrade is required.

Register an Oracle database instance for monitoring without the SYS password

In DPA 12.0 and later, you can register an Oracle database instance for monitoring when:

  • You don't have the Oracle SYS account password.
  • You don't have the Oracle SYS account password or the DPA account credentials. 

See Registering an Oracle Monitored Instance without SYS Password for details.

Registering multiple database instance types with mass registration

You can use a single mass registration template to register different types of database instances. In previous versions, you had to complete a separate registration template for each database type.

For more information, see Register multiple database instances.

Interface and navigation changes

DPA 12.0 includes some improvements to the interface and navigation:

  • On the homepage, the Query Advice status summary box has become the Tuning status summary box. It filters the list of database instances to show only instances with query or table advisors.


  • On the homepage, the Queries column has become the Tuning column. It indicates whether query or table advisors have been detected for this database instance. Clicking an icon in this column opens the new Tuning tab instead of the Trends tab. 


  • When you click a database instance on the homepage to drill in, the Tuning tab is included in the tab set at the top of the page.


  • Clicking a SQL hash or name link anywhere in DPA now opens the new Query Details page instead of the SQL Properties dialog box.

  • To access the SQL Properties dialog box, click SQL Properties at the top of the Query Details page.


  • The Analyze Query and View Historical Charts options have been replaced by the Query Details page. Use this page to view advisors and charts for any time period you select.

  • In previous versions, when you drilled down to a one-hour time slice, clicking a SQL hash or name filtered all tabs to display data about only that SQL statement.

    In DPA 12.0, clicking a SQL hash or name always opens the Query Details page. To filter the data, select the SQL hash or name from the Filter on this Query drop-down menu.


  • Click the Help button in the main menu to open the DPA Documentation page in the Success Center.


Changes to system requirements

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

DPA 12.0 adds support for the following platforms.

Repository database
  • Microsoft SQL Server 2017 Linux

DPA 12.0 no longer supports the following platforms.

DPA server OS
  • Windows Server 2008 R2
  • Windows 8.1
Repository database
  • Microsoft SQL Server 2008 R2 SP3
  • Microsoft SQL Server 2008 SP4
Virtual environment
  • vCenter Server 5.5
  • ESX/ESXi 5.5

New customer installation

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

Before you upgrade!

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

  • Review the changes to system requirements

  • If your repository database is MySQL and you are upgrading from DPA 10.2 or earlier, DPA drops the CON_ALERT_HISTORY and CON_ALERT_HISTORY_RESULT tables during the upgrade due to column resizing. Follow the instructions in this article to back up your repository before upgrading, and restore your alert history after upgrading.

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 12.0

Case number Description


Previous versions of DPA did not display historical data under a specific set of circumstances, including sporadic data collection, an Oracle repository database, and a region in which Monday is the beginning of the week. This issue is corrected.


The Blocking tab no longer becomes unresponsive if there are more than 32,767 records on the Real Time Session page.


DPA has improved its method for determining the DPA monitoring user on an Oracle database in order to exclude queries executed by this user from being polled.


DPA now shows the correct average wait time for queries that take more than one hour to execute.


Metrics cleaners now include a limit on the number of rows to include in each delete operation. This prevents them from consuming large amounts of memory and CPU resources when deleting a large amount of metrics data.


The advanced option VSPHERE_METRICS_CLEAN_DAYS_OF_DETAIL_DISK is now available. If you are monitoring a VM with many disks and the DPA repository is growing very large, you can use this and other VSPHERE_METRICS_CLEAN_DAYS options to decrease the amount of data being stored. See Repository growth when monitoring a VM with many disks for more information.


The syntax is correct for SQL statements displayed by DPA's query advisor. 


If the value for a Sybase metric exceeds 2,147,483,647, DPA no longer returns the error "Arithmetic overflow occurred."


When you view an explain plan in DPA, the first step of the access path is no longer omitted.


The DPA LDAP configuration wizard handles backslashes in passwords correctly. 

Deprecation notices

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, and avoid using deprecated features.

Type Details
Monitored databases Support for monitoring Oracle 9.x database instances is deprecated. You can still monitor Oracle 9.x database instance with DPA 12.0, but support will be removed in an upcoming release.
DPA server OS

Installing DPA on a server with an Oracle Solaris operating system is still supported in the current release, but upcoming releases will not provide out-of-the-box support  for Oracle Solaris.

When out-of-the-box support ends, the DPA installer will 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

Known issues

Cannot trace a session on an Amazon RDS instance running Oracle 12c

Issue: When you access the Real Time Sessions page for an Amazon RDS instance running Oracle 12c and select Action > Trace On for a session, the following error message is displayed: 

An Error Occurred
Unable to turn on tracing for session <SessionNumber>. Please check the DPA server logs for more information.

Work-around: None.

Oracle plan collection fails if a table name contains more than 50 characters

Issue: If an Oracle execution plan includes a table whose name contains more than 50 characters, DPA cannot collect the plan. The DPA column that stores the table name can store values of up to 50 characters. However, with Oracle 12c and later, table names can contain up to 128 characters. 

Work-around: Modify the table definition to allow the column to hold more characters. See this KB article for instructions. 

The Oracle Stale Statistics alert breaks if an object owner or table partition name contains more than 30 characters 

Issue: If the Oracle Stale Statistics alert retrieves an object owner or a table partition name that is over 30 characters, DPA cannot store the data and this breaks the alert. The DPA columns that store the object owner and table partition name can store values of up to 30 characters. However, with Oracle 12c and later, these names can contain up to 128 characters.

Work-around: Modify the table definition to allow the column to hold more characters. See this KB article for instructions. 

Top Plans for Single SQL report is missing statistics charts

Issue: The Top Plans for Single SQL report no longer includes statistics charts, such as Executions, Disk Reads, and Buffer Gets.

Work-around: None.

The SQL Server Error Log alert does not work correctly when the DPA server and monitored database instance are in different time zones

Issue: When the monitored database instance is in a time zone ahead of the DPA server, the SQL Server Error Log alert never fires. When the monitored database instance is behind the DPA server, the alert first x hours after the triggering event (x being the time difference between the DPA server and monitored instance). 

Work-around: Update the database server time to match the DPA server time.

Page Life Expectancy on servers with NUMA node architecture

Issue: DPA reports the average page life expectancy, not the page life expectancy of individual buffer pools. (For more information, see Page Life Expectancy isn't what you think.)

Work-around: Create a custom metric.

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.

Work-around: Use DPA with supported versions of MySQL.

Incorrect metric values reported for SQL Server 2017 on Linux

Issue: When you are monitoring a SQL Server 2017 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.

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

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

DPA has high CPU utilization for long periods when Embedded Mail Server is used

Issue: When Embedded Mail Server is selected as the mail server configuration option and an attempt to send email fails (for example, because of an environmental issue such as a firewall or the mail server configuration), DPA saves the email into a queue and tries to send the email again. If the problem persists, having a large number of emails in the queue causes high CPU utilization.

Work-around: Change the mail server configuration, or fix the issue that is preventing mail from being sent. See this article for more information. 

DB2 10.5 reporting wait time as type "NONE"

Issue: If you are monitoring a DB2 10.5 database instance, you might see wait times with the type "NONE."

Work-around: Exclude this wait type from monitoring. To do this, open Advanced Options, click DB Instance Options, and select a database instance. Then click Wait Events in the upper-left corner.

CPU utilization for a large number of CPU cores

Issue: The CPU utilization metric does not display the correct data for multi-core or -socket environments. DPA uses a deprecated view that does not provide consistent data for environments using a high number of cores or sockets.

Work-around: Follow the instructions in this KB article.

The ApplicationIntent flag is ignored when you are registering an AG listener

Issue: If you are registering a secondary replica in an AG cluster and you specify the ApplicationIntent=ReadOnly flag, this flag is ignored and DPA connects to the primary replica. 

Work-around: To specify the ApplicationIntent flag, register a database instance and not the listener. To specify the flag, follow the instructions in this KB article

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. 

Work-around: Disregard the incorrect execution counts.

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



Last modified