Submit a ticketCall us

AnnouncementsFace your biggest database issues head-on

Our new eCourse helps you navigate SQL Server performance blocks by teaching you how to recognize and deal with the three DBA Disruptors: Performance Hog, Blame Shifter, and Query Blocker. Register today to learn how to defend your environment and fend off menacing disruptions.

Register for your free eCourse.

Home > Success Center > Database Performance Analyzer (DPA) > DPA - Knowledgebase Articles > Oracle instance error: Max Allowed Monitored Database Sessions Exceeded

Oracle instance error: Max Allowed Monitored Database Sessions Exceeded

Updated March 29, 2017

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.

 

 

Environment

All DPA versions

 

Cause 

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

The change in limits in the statisticss 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.
 

 

Last modified

Tags

Classifications

Public