Applications Systems

Oracle instance error: Max Allowed Monitored Database Sessions Exceeded

This article overviews what may resolve your issue if you are monitoring a Oracle instance and notice the "max allowed monitored database sessions exceeded" error

First published date

11/29/2018 11:00 PM

Last published date

11/29/2018 11:00 PM

Overview

The following error occurs when monitoring an Oracle instance: 

QuickPollJob failed [See nested exception: org.springframework.jdbc.CannotGetJdbcConnectionException: Could not get JDBC Connection; nested exception is java.sql.SQLException: An SQLException was provoked by the following failure: java.lang.Exception: max allowed monitored database sessions exceeded

 

The DPA logs show the following error:

SQL stats fetch for database 3 failed to complete within the specified time limit of [360] seconds. SQL stats may not be complete for this time slice. Please contact DPA Support if you regularly see this message.

Product section

Database Performance Analyzer

Cause

The statistics poll runs long, and then consumes the maximum amount of threads for the statistics poll.

The change in limits in the statistics poll, which should resolve the issue.

Resolution

  1. Go to the Options > Administration > DB Instance Options tab.
  2. Select the instance with issues from the drop-down menu.
  3. Select Support Options.
  4. Locate SQLSTATS_LIMITED.
  5. Set the value to TRUE.