ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

AwE-5001 Database Query Error DBAccess: checkError 17010

book

Article ID: 237034

calendar_today

Updated On:

Products

CA Automic Applications Manager (AM)

Issue/Introduction

After upgrading Applications Manager, RMI does not process any Jobs and repeatedly throws the following errors:

There are many errors in RMI server logs:

19:52:11.492 OCh: .AxRmiServer$1: null ErrorMsg: AwE-5001 Database Query Error
Details: Closed Resultset: getMetaData
null
19:52:11.492 OCh: .DBAccess: checkError 17010
19:52:11.492 OCh: AwE-5001
19:52:11.492 OCh: SQL Error: 17010
ErrorMsg: AwE-5001 Database Query Error
Details: Closed Resultset: getMetaData
aw5.aw_wait_obj_changed
 0 timeout: IN:NUMERIC:java.lang.Integer:60
 1 seq: IN:NUMERIC:java.math.BigDecimal:2078236

  sID-2079585 
java.sql.SQLException: Closed Resultset: getMetaData
aw5.aw_wait_obj_changed
 0 timeout: IN:NUMERIC:java.lang.Integer:60
 1 seq: IN:NUMERIC:java.math.BigDecimal:2078236

 at oracle.jdbc.driver.InsensitiveScrollableResultSet.getMetaData(InsensitiveScrollableResultSet.java:229)
 at com.appworx.server.sql.DBAccess.parseResultSet(DBAccess.java:1097)
 at com.appworx.server.sql.DBAccess.getFunctionData(DBAccess.java:846)
 at com.appworx.server.sql.CommonDB.B(CommonDB.java:273)
 at com.appworx.server.sql.CommonDB.getFunctionData(CommonDB.java:321)
 at com.appworx.server.sql.CommonDB.waitObjChanged(CommonDB.java:1139)
 at com.appworx.server.data.JobsData$10.run(JobsData.java:2926)

Cause

Wrong ojdbc driver used during upgrade of the system

Environment

Release : 9.4

Component : Applications Manager

Resolution

Replace old ojdbc7.jar to the correct ojdbc8.jar in \web\classes and restart the Applications Manager

Additional Information

Applications Manager's Java processes will utilize the jar file that's in the \web\classes.

If there are multiple jar versions for example ojdbc7.jar and ojdbc8.jar in the directory, remove or rename the unused one from \web\classes.

There is only one ojdbc driver required in the %SQLOPER_HOME%\ojdbc directory. Having both could lead to some unexpected behaviors.