article Oracle database not responding in up.time interface

This article addresses the symptom of seeing Database Not Responding messages in the up.time 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;

Related Articles


Running up.time with an Oracle database

RatingViews
article

By: uptime Support | Date Created: 1-16-2006 | Last Modified: 7-22-2014 | Index: 053

  9663

Understanding your Oracle Connection Settings

RatingViews
article

This article outlines how you can use the information in the Oracle TNS connection string to populate database-specific fields that need to be set in the uptime.conf file.

By: uptime Support | Date Created: 2-27-2007 | Last Modified: 6-30-2011 | Index: 146

  5782

"Database Not Responding" Message Appears in Global Scan

RatingViews
article

When this issue occurs, check the uptime.log file for messages similar to the following: 011-03-29 11:40:48,873 ERROR (ProtocolHandler:79) - In command...

By: uptime Support | Date Created: 7-9-2011 | Last Modified: 10-26-2012 | Index: 539

  2160

Login screen returns Database not responding error after upgradin...

RatingViews
article

If you did not log out of the up.time UI before upgrading to up.time 6.0.1 (refer to step 6 of Upgrading and Applying up.time Service Packs), you may see the following error after attempting to...

By: uptime Support | Date Created: 12-21-2011 | Last Modified: 8-14-2013 | Index: 572

  2224

Migrating Your DataStore To a New Database

RatingViews
article

This article outlines how to move your DataStore between different database types.

By: uptime Support | Date Created: 2-21-2007 | Last Modified: 6-30-2011 | Index: 142

  4239

User Comments



No comments have been posted.

Copyright © 2021 IDERA, Inc.   Legal   Privacy Statement