Submit a ticketCall us

AnnouncementsWeb Help Desk Integrations eCourse

Looking to reduce response times? Sign up for our eCourse to learn how integrating Web Help Desk with Dameware Remote Support, Network Configuration Manager, Network Performance Monitor, and Server & Application Monitor can improve communication efficiencies.

Register here.

Home > Success Center > Database Performance Analyzer (DPA) > DPA 11.1 Administrator Guide > Monitor database instances

Monitor database instances

Table of contents
No headers
Created by Melanie Boyd, last modified by Melanie Boyd on Nov 07, 2017

Views: 284 Votes: 0 Revisions: 2

Updated: November 62017

DPA uses an approach called wait-based analysis to help you focus on issues that provide the greatest performance improvements. See a walk-through of using DPA to investigate an application issue in the DPA Getting Started Guide.

The DPA homepage displays a table of the monitored database instances where you can see all of the database types. Click Action to start or stop monitoring.

Instance Groups

You can group monitored databases using the Instance Groups feature. Click File:Success_Center/New_Articles/DPA_11.1_Admin_Guide_Updates/0230-Monitor_database_instances/manage-instance-groups.png to add, modify, or delete an Instance Group.

SolarWinds DPA automatically groups Oracle Real Application Clusters (RAC) instances and Oracle multitenant container databases (CDB) containing pluggable databases (PDB). You can manually group other databases.


Monitoring is always active after it is started. It is not necessary to restart the SolarWinds DPA monitor if the repository instance or the monitored database instance was unavailable for a period of time. Monitoring resumes when both are available again.

If there is a period of time when monitoring should not occur, you can stop monitoring a database instance.

If you are having problems connecting to or monitoring a database instance, see Troubleshooting tips.

Last modified