Submit a ticketCall us
Home > Success Center > Database Performance Analyzer (DPA) > DPA Documentation > DPA Integration Module 11.1 Release Notes

DPA Integration Module 11.1 Release Notes



Last updated: July 31, 2018

These release notes describe the new features, improvements, and fixed issues in version 11.1 of the DPA Integration Module (DPAIM) and version 2017.3 of the Orion Platform.

For information about DPA 11.1, see the DPA 11.1 release notes. For information about DPA 12.0, see the DPA 12.0 release notes.

New features and improvements

DPA data in Performance Analysis (PerfStack™) dashboards

You can add DPA data to PerfStack dashboards, including wait time, database metrics, VM metrics, and custom metrics. When you identify a time period with significant wait times, you can use the Data Explorer to examine the SQL statements that were executed during that period. 

Both DBAs and non-DBAs can use PerfStack to correlate database metrics with other Orion Platform metrics, and identify relationships between database wait times and other factors in the environment.

>> Learn more about DPA data in PerfStack

>> Learn more about PerfStack and the latest PerfStack improvements

Blocking and Deadlocks resource

When you drill in to view details about a monitored database instance, the summary view includes the Blocking and Deadlocks resource. Use this resource to determine if blocking sessions and deadlocks are affecting performance. It includes the following tabs:

  • The Top Waiters tab identifies the sessions that are affected by blocking. These sessions are idly waiting for a locked resource to be released by another session.
  • The Top Root Blockers tab shows what the root blocker transactions are doing and their impact on all sessions that they are directly or indirectly blocking.
  • (SQL Server and Azure SQL database instances only) The Deadlocks tab shows the number of deadlocks that occurred in each time period. Deadlocks occur when two sessions have a lock on different resources, and each session needs a resource held by the other to complete its task.

The Blocking and Deadlocks resource is not available for DB2 database instances.

Stand-alone DPAIM installation

DPA users who do not own other SolarWinds products can install DPAIM stand-alone and access DPA data from the Orion Web Console. Orion features such as PerfStack and customizable dashboards are available for use with DPA data. See New customer installation for more information.

Simplified and improved resources

DPAIM resources have been updated to make it easier for users to identify databases with performance issues. In DPAIM 11.0, the database instance status was changed to reflect only wait times. Other metrics (such as memory or CPU usage) might be high, but they don't indicate a database performance problem unless users are experiencing long wait times.

DPAIM 11.1 includes the following additional improvements.

All Database Instances resource (Database Summary view)

The  filters at the top now include all statuses. Use these to filter by one or more statuses. You can also use the drop-down menu to filter by database type. 

To keep the focus on database performance issues, the resource no longer displays status information for other metrics, such as memory or CPU usage. (If you want to display this information again, see Displaying metrics below.)


Database Response Time resource (Database Instance view)

Like the All Database Instances resource, the Database Response Time resource shows only the wait time status. Status information for other metrics has been removed. (If you want to display this information again, see Displaying metrics below.)

On the SQL tab, the legend now shows the SQL hash or the custom name assigned in DPA, instead of SQL text. You can click the hash or name to open the SQL Detail window, described in the following section. 


SQL Detail window

Click the SQL hash or name in any resource to view detailed information about a SQL statement, including:

  • Any advisors for the statement
  • The total response time in the past 2 hours
  • The number of executions in the past 2 hours
  • The SQL text

Click View in DPA to display historical information about the SQL statement in DPA. 


Displaying metrics

If you want the All Database Instances resource and the Database Response Time resource to display metrics again, you can change an Orion Advanced Configuration setting:

  1. Log in to the Orion Web Console using an account with administrative privileges.
  2. In the address field of the web browser, enter the following:


  3. Under DPA.DatabaseInstances.Settings, select ShowKpis.
  4. Click Save.

Improved wait time status information from DPA

DPA 11.1 uses the same statuses as the Orion Platform: green (normal), yellow (tracking high), and red (tracking very high). This allows DPA and DPAIM to display status information consistently. In addition, DPA updates status information once every 10 minutes instead of once an hour.

Compatibility checker

When you are integrating a DPA server, DPAIM checks to make sure that the DPAIM and DPA versions are compatible. If an incompatibility is detected, a message tells you what version of DPA or DPAIM is recommended or required, and provides information about the new features in that version.

Dashboards and widgets

The new Customize Page significantly simplifies and streamlines how you build your dashboards or views. Drag and drop resources, now known as widgets, exactly where you want them on your page, including on to blank areas to create new columns.

  • Start searching for widgets in two clicks from any customizable page.
  • Mark favorite widgets so you can quickly add them to new dashboards or pages.
  • Drag and drop widgets directly on to the pages or move widgets to new locations.

» Read more about dashboards

Secure the connection between your Orion server and your SQL server

Increase your security compliance by using Windows authentication for both day-to-day data storage and retrieval between your Orion server and your SQL server and during the initial setup of your database server in the Configuration Wizard. 

Do not use a Windows account with a password policy applied.

You can also enable SSL directly in the Configuration Wizard to encrypt the information exchanged between your Orion server or additional polling engines and your SQL server, independent of SSL settings on your SQL server.

SSL must be configured on your SQL server to utilize this feature.

New customer installation

DPAIM can be installed in either of the following ways:

  • With SolarWinds SAM

    DPAIM is automatically installed with SolarWinds SAM 6.2.1 or later. If you have SAM 6.2.1 or later, you do not need to install DPAIM. All you have to do is set up the integration module.

    To install SAM, use the SolarWinds Orion Installer.

  • Standalone (SAM not required)

    If you do not plan to install SAM, download and run the SolarWinds Orion Installer to install DPAIM as a separate product. You can install DPAIM alone, or you can install DPAIM with other Orion Platform products such as SolarWinds SRM.

After you install DPAIM, you must set up the DPA Integration Module

Before you upgrade!

DPAIM 11.1 no longer supports Windows OS 2008 and 2008 R2 and Microsoft SQL Server 2008 R2 for Orion Platform installations. Upgrade to Windows Server 2012, 2012 R2, or 2016 before you upgrade DPAIM. For more information, see End of support notices.

How to upgrade

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

Fixed issues

DPAIM 11.1 fixes the following issues.

Case number Description


You can mute or resume alerts in the Orion Web Console even if the associated DPA server is down.


DPAIM resources display data correctly even if the Orion Platform setting UnionDegreeOfParallelism is set to 1.


DPA integration no longer fails when a node's DNS property contains a square bracket ([). 


DPAIM can be upgraded or uninstalled on a server that does not have .NET 3.5 installed.


Custom resources are rendered correctly when the Business Layer is down.


You can create a new group with database instances even when one or more DPA servers are down.

Orion Platform 2017.3 fixes the following issues.

Case number Description

1170324, 1135026, 1164963, 







1147767, 1143080, 1138560,   1137648, 1138009, 1124158, 1163713 

The global navigation menu bar is missing.


Netpath cannot access the requested path.

1136599, 1143676, 1133928, 1110258 

Netpath times out and only shows a single point in time.


A CPU utilization issue on multi-core nodes running Microsoft® Windows Server® 2008 R2 when using WMI or the agent polling method.


Orion agent Debian-based Linux packages are missing a space in the version information.


Agents appear connected on the Manage Agents page, but cannot send information back to the server after an upgrade.

1081143, 1113910

Linux-based Orion agents fill the /tmp folders with TaskProperties files.


The Orion agent cannot differentiate between two nodes with the same IP address when one node is behind a NAT.


Cannot add SNMPv3 credentials to poll a Windows node with the Orion agent.


When deploying an Orion agent, the Application Event log has the following error:

The job schedule database file is corrupt....

1199142, 1103578, 1092273, 1139529 

IPv6 nodes polled with ICMP do not return correct values or are unreachable.

955013, 1024495, 1138773, 1202980 

Incorrect time zone information for the southern hemisphere and the alerts are scheduled one hour earlier than intended.


Repeated alert actions stop working after one of the following occurs:

  • restarting Alerting Service v2
  • modifying an alert action
  • losing the connection to the database or Information Service v3
1164854, 1196999, 1190898

Domain users or groups added after an upgrade cannot log in with a error:

SolarWinds.Orion.Web.OrionMixedModeAuth - (null) Failed to retrieve WindowsIdentity for user <user>: System.Security.Authentication.AuthenticationException Cannot logon '<user>' via Interactive/Default.

1082111, 1009462, 1073184, 1102489, 1116840, 1113529, 
1164723, 1195031, 1147707, 1130235, 

Repeated alert actions do not trigger when an alert is edited or the alerting service is restarted.

1187535, 1126092, 1091068, 1126361, 1160693, 1034970, 1067830, 1075247, 1067457, 1086208, 1105612, 1124335, 1138711, 1146216, 1152348, 850464, 961469, 944283, 1005146, 1004940, 1023357, 1087128, 1090237, 1082382, 1108013, 1116804, 1112982, 1119012, 1113720, 1124724, 1134211, 1145831, 1109627, 1180971, 1187535, 1154647

The Node Reboot alerts and event-based alerts do not trigger.


1190180, 1167620, 1174631, 1175273, 1171806, 1180712, 1181381, 989718 

Scheduling for alerts and reports is one hour off.

1183756, 1032145, 1066438, 

Some alert actions cannot be simulated and return an error similar to the following:

2017-06-22 08:01:43,724 [140] INFO  AlertingLogger - NetObjectData for entity Alerting: swis://
ForecastCapacity/EntityType="Orion.Volumes",MetricId=3 (AlertObjectId =  ) does not exist. Alert action ###: 'Post to' will not be executed.


1148595, 1133531, 1135332, 1138622, 1142313, 1143110, 1138788, 1150043, 1152481, 1113579, 1113898, 1138326, 1153010, 1141811, 1153896, 1157577, 1171634, 1155356, 1147223, 1143539, 1153845, 1134872, 1148761, 1154253, 1128086, 1158176, 1124099, 1060558  

The Orion Web Console is slow after an upgrade due to SWIS v3 using a large amount of memory.

1180808, 1116741 

Account limitations applied to groups intermittently display unwanted nodes.

1094832, 1130773, 1159671, 1171385, 1171682, 1166910, 1116402, 

Some resources are not listed due to HEX-string values in the OIDs.

1139372, 1154482, 1156463, 1143611, 1118211, 1174841

Saved changes to Network Atlas maps do not display when your Orion server time zone is set to any negative time zone, such as UTC-5.

1126358, 1148560, 1144414, 1152358, 1159419, 1101641, 1118741, 1120297, 1107631, 1139310, 1130725, 1150164, 1175369, 1143012, 1155599

You are prompted to log in when viewing reports. PDF reports have a screenshot of the Orion Web Console login page or an Unexpected website error.

1148059, 1165475, 1166654, 1168955, 1171034, 1139724, 1156926, 1152091, 1148399, 1147728, 1146219, 1081084, 1148739 

Performance issues due to deadlock and locking in the OrionServers table.

1018994, 1084453, 1095223, 1113681, 1163514, 1083077, 1107391, 1123401, 1110556, 1130277, 1170228, 1033563, 1069910

Custom Object resources are very slow or time out when editing or creating them.


CPU is high for trap services.


Page loading times are high.

1103629, 1163273 

Cannot import custom properties for groups to a Worldmap.

1166215, 1166270 

When integrated with ServiceNow instances with a large number of customizations, alerts do not work as expected.

1165130, 1105005 

Devices do not poll when you are missing SNMP v3 credentials.

1155215, 1155352, 1058519, 1096595, 1106405, 1089958, 1140354, 1138870, 1112997, 1132300, 

Automatic monitoring settings are reset to the default after the Configuration Wizard runs.

1066550, 1100302, 1146412, 1124954 

Cannot open the Advanced Configuration page.


When copying the default Node Details view, the Quality of Experience and Asset Inventory sub pages do not copy the appropriate resources.

1136856, 1117267, 1116460, 1106393

SNMPv3 credentials are not correctly assigned to nodes.



The time does not update in the Orion Web Console.


The Managed Alerts page does not completely load, and you cannot filter alerts.

1132507, 1070372, 1056500, 1121349, 979463, 897210

Alerts created with a disabled user do not work as expected, and the Active Alerts page may be blank or have an error.

1118106, 1141738, 

ServiceNow integration stops working if you mass edit incidents.


Cannot advance to the next Manage SNMPv3 credentials page.

1092013, 1097173, 1112369, 1117267, 1125348

SNMPv3 credentials can be deleted or incorrectly updated when mass editing nodes that use different polling methods.

1100922, 1122034 

Cannot create ServiceNow incidents due to missing roles.


Limitations are not applied correctly to alerts.

1083182, 1142800, 1120175, 1118112, 1120175, 1109625 

Cannot add or search for domain accounts when using LDAP.

1110844, 1119752, 1100383, 1101723, 1112970, 

ServiceNow incidents re-active.

1109266, 1072704, 1056235, 1052510, 1118865 

Volume added using WMI stop polling.

1118901, 1076841, 1097612, 1089416, 1087776, 1024125, 968951,  

Network Atlas maps load slowly or not at all. You may receive an error similar to the following:

Operation in progress, waiting for a connection...


Device type is not completely recognized

1103781, 1097218, 1108197 

Some features, such as the Real-Time Process Explorer, stop functioning on you additional polling engines with the following error:

The Job Engine password files are out of sync.

1102878, 1102634 

The Settings page is blank when the default document is disabled in IIS.

1100794, 1058790, 993082 

The ServiceNow incident resource does not display data.

1097774, 1054466

HTML reports are embedded with What's New in the UI information.

705254, 993277, 1095107, 1081919, 1031691, 973096 

When you monitor multi-core devices with WMI, the polled results are inconsistent and may return errors.


The Orion Service Manager opens with the following message:

Error starting service manager


New Cisco switches (C 2990CX) display an incorrect Machine Type.


The Custom Query resources does not page correctly.

1074893, 1044414, 1013808, 977233, 1059448, 1046813, 1027885, 940870, 1017984

Cannot open Quality of Experience resources in the Orion Web Console or Network Atlas.


946894, 1018470 

L3 polling data is incorrect for some nodes.

869365, 1001732

The job engine for SNMP polling become unresponsive and polling does not complete.


Large spikes in the Data Transmitted metric on non-US English installations


Trigger conditions affect what is displayed in the Detected Objects window.

Known issues

Some DPA data is not displayed correctly in PerfStack

Issue: DPA data that represents a time series and can include multiple metrics is not displayed correctly in PerfStack charts. What should be shown as stacked graphs is displayed as a single line.

Work-around: None.

Date range is one day behind on Wait Time resources

Issue: The date on Wait Time Trends resources is one day behind for environments where the DPA and Orion servers are in different time zones. The affected resources are:

  • All Instances with the Highest Wait Times
  • Instances with the Highest Wait Times
  • Greatest Downward Wait Time Trends
  • Greatest Upward Wait Time Trends

Work-around: Set the DPA and Orion servers to the same time zone.

DPAIM stops working after failover

Issue: If you have High Availability configured, the DPA Integration Module stops working when a failover occurs after you re-integrate with a previously integrated DPA server.

Work-around: Re-integrate the DPA server.

Cannot integrate DPA servers when the Orion Platform uses Windows Authentication

Issue: When the Orion Platform uses Windows authentication to access the Orion database, attempts to integrate a DPA server fail with the following error: 

There was an error when trying to enable the integration with the DPA server: Establishing federation with jSWIS failed.

Work-around: Configure the Orion Platform to use a SQL Server account to access the Orion database. To do so, run the configuration wizard and specify that you want to update only the database. 

Report resource fails to initialize if any DPA server is down

Issue: If you attempt to create or run a report that includes DPA resources and any integrated DPA server is down, the following error is returned:

Report resource failed to properly initialize.

Work-around: To avoid this error, ensure that all integrated servers are up before creating or running reports that include information from DPA. Alternatively, remove the integration for a server and reintegrate it later.

Database instance limitations do not work properly with groups

Issue: If there are limitations on a user account to prevent the user from viewing information about certain database instances, and a group includes database instances that match the limitations, the limitations have no effect. When the user accesses the group, the user can see information about all database instances in spite of the limitations. 

Work-around: Be aware of this issue when you are setting up security. 

© 2017 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 and documentation are and shall remain the exclusive property of SolarWinds and its respective licensors.


The SolarWinds and other SolarWinds marks, identified on the SolarWinds website, as updated from SolarWinds from time to time and incorporated herein, are registered with the U.S. Patent and Trademark Office and may be registered or pending registration in other countries. All other SolarWinds trademarks may be common law marks or registered or pending registration in the United States or in other countries. All other trademarks or registered trademarks contained and/or mentioned herein are used for identification purposes only and may be trademarks or registered trademarks of their respective companies.

Last modified