Database Management

Oracle 12c Monitoring Keeps Stopping in DPA 2025.4

Older Oracle 12c instances are not fully monitored in 2025.4, with the monitoring starting and stopping.

First published date

4/2/2026 4:27 PM

Last published date

4/2/2026 4:27 PM

Overview

Experiencing an issue where DPA 2025.4.0 repeatedly stops and restarts monitoring an Oracle 12c (non-CDB) instance.

Actions that have been completed:

  • Increased SESSIONS_PER_USER to 20

  • Granted SELECT ANY DICTIONARY privileges to the monitoring user

Product section

Database Performance Analyzer

Resolution

Oracle 12c is currently out of Oracle’s support lifecycle, and as a result, DPA engineering no longer tests or addresses issues specific to Oracle 12c.

Ref: Databases that each version of DPA can monitor 

While DPA may still be able to connect and collect data, if the collector encounters a version-specific issue (for example, related to a 12c view or package that newer DPA versions no longer handle), it may cause monitoring to stop and restart, similar to the behavior observed.

There are two possible options:

  1. Upgrade the database to a supported Oracle version (19c or later) and continue using DPA 2025.4. This is the only fully supported configuration.

  2. Use an older DPA version that previously listed Oracle 12c as supported. However, that DPA version may itself be outside mainstream support and would not receive fixes, so it may not be a viable long-term solution.

Possible workaround: The issue is due to a missing DPA-added object that is needed for polling. 

This is a common issue in Oracle monitoring. When you apply any Oracle patch, DPA views get removed by the Oracle patch and need to be added back.

The resolution is to rerun either of the two scripts referenced below. Rerun the first for on-prem Oracle, and rerun the second for RDS. Then restart the monitor. 

Create the DPA monitoring user for Oracle

downloads.solarwinds.com/solarwinds/Documentation/CreateMonUserAmazonOracle.sql

IMP: This Oracle version is not officially supported with this release of DPA; therefore, the above workaround is provided on a best-effort basis from the Support team.