Submit a ticketCall us

Solarwinds & Cisco Live! Barcelona
Join us from the 29th of January to the 2nd of February at Cisco Live 2018 in Barcelona, where we will continue to show how monitoring the network with SolarWinds will keep you ahead of the game. At our booth (WEP 1A), we will demonstrate how SolarWinds network solutions can help. As a bonus, we are also hosting a pre-event webinar - Blame the Network, Hybrid IT Edition with our SolarWinds Head Geek™, Patrick Hubbard on January 24th - GMT (UTC+0): 10:00 a.m. to 11:00 a.m. There's still time to RSVP.

Home > Success Center > Database Performance Analyzer (DPA) > DPA 11.1 Administrator Guide > Troubleshooting tips

Troubleshooting tips

Created by Anthony.Rinaldi_ret, last modified by Anthony.Rinaldi_ret on Sep 15, 2016

Views: 573 Votes: 0 Revisions: 5

Updated: November 62017


DPA logs information about each monitored database instance. Use this information to help you determine why a database instance is not being monitored, or if data are missing.

Access log data through the DPA log viewer

Use the DPA Log Viewer to view log information for a specific database instance, or for all database instances and the DPA repository.

  1. Open the Log Viewer:
    • From the DPA homepage, click Action > Log next to a database instance.

      The Log Viewer displays the log for that database instance.

    • Click Options > Support tab. Then, under Utilities, click Log Viewer.

      The Log Viewer displays log messages for all monitored database instances and the DPA repository.

  2. Use any of the following options to locate information:
    • Use filters to help you find specific information. To change the filters, click Advanced and select the filter criteria. For example, you can filter by date range, a text string, or message level.
    • For any message above Info, click Details to view additional information from the log.
    • Click Log Files for Support to create a compressed file you can send to SolarWinds Support.

Open log files in a text editor

Log files are stored in the installDir/iwc/tomcat/logs/ directory.

Access to a database instance

If DPA cannot access the server that hosts a database instance you want to monitor:

  • Make sure a firewall is not running on the server.
  • Make sure another process is not using the default SolarWinds DPA ports.

If the ports are being used by another process, you can change the default ports of 8123, 8124, and 8127. To specify different ports for DPA to use:

    1. Open the following file in a text editor:


    2. Update the following lines with new port numbers:
      <Server port="8127" shutdown="SHUTDOWN">
          <Connector port="8123"/>
          <Connector port="8124"/>
    3. Save the file and restart DPA.

Issues after the Oracle PDB that stores the repository is moved

If the DPA repository is created on an Oracle pluggable database (PDB), you might experience the following issues after the PDB is moved to a different container database (CDB).

DPA returns a connection error

The PBD moved to a CDB on a different server, and the connection string is incorrect. Update the connection string in the file in the following location: 


DPA returns an invalid login error

Verify that the DPA monitoring user exists in the CDB. Common users (prefaced with C##) exist in only one CDB.

Last modified