You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Current »

This article addresses the symptom of seeing Database Not Responding messages in the Uptime Infrastructure Monitor User Interface. The message will typically be similar to the following error:

Database is not responding

<< java.lang.RuntimeException: java.sql.SQLException: ORA-00604: error occurred at recursive SQL level 1 
ORA-01000: maximum open cursors exceeded
at com.uptimesoftware.uptime.database.QueryDatabaseConnector.executeWork(QueryDatabaseConnector.java:24) 
at com.uptimesoftware.uptime.database.JdbcExecutor.execute(JdbcExecutor.java:34)
at com.uptimesoftware.uptime.dataservice.query.Query.getResultSet(Query.java:81)
at com.uptimesoftware.uptime.dataservice.QueryExecutor.getResultSet(QueryExecutor.java:30) 
at com.uptimesoftware.uptime.dataservice.QueryExecutor.executeQuery(QueryExecutor.java:13)
at com.uptimesoftware.uptime.dataservice.ProtocolHandler.handleQuery(ProtocolHandler.java:143) 
at com.uptimesoftware.uptime.dataservice.ProtocolHandler.run(ProtocolHandler.java:58)
at java.lang.Thread.run(Unknown Source)

This error indicates that the Oracle open cursor limit has been reached. To resolve this issue, try increasing the open_cursor limit by using the following command:

ALTER SYSTEM SET open_cursors = 1000 SCOPE=BOTH;


  • No labels