Submit a ticketCall us

WebinarVisual Monitoring Tactics: Getting More Log Search Value from SolarWinds Log & Event Manager with nDepth Webcast

Do things seem to make more sense when they are visualized? Are you an IT professional or security expert with a wish for more cybersecurity tools that provide an intuitive visual experience? Join Alexis Horn and Jamie Hynds from SolarWinds as they demonstrate how the nDepth feature in LEM can help make visualizing log search results a reality.

Register now.

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