AAoP in websphere and DB2 deleting users could throw an error 'result set is closed. ERRORCODE=-4470'
3 years ago
Originally Published: 2011-08-23
Article Number
000044546
Applies To
This issue was seen on Websphere 7.3 and DB2 9.5 customer tried to delete users from the scheduler webapp.
Environment: AIX 5.3, DB2 9.5 , web sphere 7.3  and AA 6.0.2.1 sp2 p1.
Issue

011-05-10 14:33:00,787 DEBUG [AAOPScheduler_Worker-3] DeleteUsersJdbcCursor - add to batch RBA_ENTITY_PROFILING

2011-05-10 14:33:00,811 DEBUG [AAOPScheduler_Worker-3] DeleteUsersJdbcCursor - stmtDeleteUsers first value =3472305

2011-05-10 14:33:00,812 DEBUG [AAOPScheduler_Worker-3] DeleteUsersJdbcCursor - add to batch stmtDeleteUsers

2011-05-10 14:33:00,853 ERROR [AAOPScheduler_Worker-3] DeleteUsersJdbcCursor - Exception deleting users :

com.ibm.db2.jcc.am.SqlException: [jcc][t4][10120][10898][3.59.81] Invalid operation: result set is closed. ERRORCODE=-4470, SQLSTATE=null

at com.ibm.db2.jcc.am.dd.a(dd.java:660)

at com.ibm.db2.jcc.am.dd.a(dd.java:60)

at com.ibm.db2.jcc.am.dd.a(dd.java:103)

at com.ibm.db2.jcc.am.qm.Db(qm.java:4381)

at com.ibm.db2.jcc.am.qm.c(qm.java:325)

at com.ibm.db2.jcc.am.qm.next(qm.java:304)

at com.ibm.ws.rsadapter.jdbc.WSJdbcResultSet.next(WSJdbcResultSet.java:3120)

at com.rsa.db.utils.impl.DeleteUsersJdbcCursor.execute(DeleteUsersJdbcCursor.java:189)

at com.rsa.db.utils.scheduler.DbUtilityScheduler.process(DbUtilityScheduler.java:25)

at com.rsa.db.utils.scheduler.DbUtilityScheduler.process(DbUtilityScheduler.java:31)

at com.rsa.csd.scheduler.BatchJobWrapper.process(BatchJobWrapper.java:94)

at com.rsa.csd.scheduler.BatchJobWrapper.executeInternal(BatchJobWrapper.java:72)

at org.springframework.scheduling.quartz.QuartzJobBean.execute(QuartzJobBean.java:86)

at org.quartz.core.JobRunShell.run(JobRunShell.java:202)

at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:525)

2011-05-10 14:33:00,855 INFO [AAOPScheduler_Worker-3] DeleteUsersJdbcCursor - Total users deleted : 1


Resolution

1) In Web Sphere  you need to modify all datasources  and change the parameter "resultSetHoldability"located in Data sources > RSADB2 > Custom properties

Its value should be changed from 2 to 1 which will have

 the same impact as the IBM workaround described in: https://www-304.ibm.com/support/docview.wss?uid=swg21461670

2) Once you changed this value from 2 ->1 you need to stop and restart.


Don't see what you're looking for?