Documentation forDatabase Performance Analyzer

DPA troubleshooting tips


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:
    • To display log messages for a specific database instance: 

      From the DPA home page, click Action > Log next to the database instance.

    • To display messages for all monitored database instances and the DPA repository:

      From the DPA menu in the upper-right corner, click Options. Then, under Support > Utilities, click Log Viewer.

  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 DPA-install-dir/iwc/tomcat/logs/ directory on the DPA server.

Download log files to a DPA client

You can download some or all DPA log files from the Management Options page.

  1. Log in to DPA as a user with administrative privileges.

  2. From the DPA menu in the upper-right corner, click Options.

  3. Under Support > Downloads, click one of the following options:

    • To download all log files, click All Log Files (Zipped).

    • To download the idc.log file, click Data Collection Log File.

    • To download the iwc.log file, click Web Client Log File.

    • To download the wizard.log file, click Wizard Log File.

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