Error: SQLCODE: -805, SQLSTATE: 51002, SQLERRMC: NULLID.SYSLH205 0X5359534C564C3031
in [DB2]
|
Prev: _ in LIKE
Next: Help me convince them this is bad!!!
From: misterutterbag on 4 Oct 2006 09:21 Stack trace below. Only happens in WebSphere 6.0. DB2 v 8.2. FP12. Only against 1 database. I have other databases in this database instance, but they don't seem to have this problem. Looked up SQLCODE: -805. It said either a) the client and server versions don't match (which doesn't make sense, because we've run the same versions since May with no problem) b) There was an SQL PKG missing, which doesn't seem right, because you'd think it would be missing from the other databases in the same instance. I also tried rebinding everything from SP 12 for DB2, and restarted the db, with no success. Any info would be appreciated. Joel -------------------------- 2006-10-04 09:03:15,263 ERROR [NodeHeartbeatThread] net.ubiquity.conference.server.confapp.nodeservices.NodeServiceController - DatabaseException: node service controller fails to update heart beat com.ibm.db2.jcc.b.SqlException: DB2 SQL error: SQLCODE: -805, SQLSTATE: 51002, SQLERRMC: NULLID.SYSLH205 0X5359534C564C3031 running com.ibm.db2.jcc.b.SqlException: DB2 SQL error: SQLCODE: -805, SQLSTATE: 51002, SQLERRMC: NULLID.SYSLH205 0X5359534C564C3031 at net.ubiquity.conference.server.confapp.dbcontrol.impl.NodeServiceDbControllerImpl.updateNodeLease(NodeServiceDbControllerImpl.java(Compiled Code)) at net.ubiquity.conference.server.confapp.nodeservices.NodeServiceController$NodeHeartbeatThread.run(NodeServiceController.java(Compiled Code)) ---------------------------------
From: Shashi Mannepalli on 4 Oct 2006 09:22 Try this bind command db2 "bind db2clipk.bnd blocking all grant public clipkg 30" cheers... Shashi Mannepalli misterutter...(a)yahoo.com wrote: > Stack trace below. > > Only happens in WebSphere 6.0. > DB2 v 8.2. FP12. > > Only against 1 database. I have other databases in this database > instance, but they don't seem to have this problem. > > Looked up SQLCODE: -805. It said either > a) the client and server versions don't match (which doesn't make > sense, because we've run the same versions since May with no problem) > b) There was an SQL PKG missing, which doesn't seem right, because > you'd think it would be missing from the other databases in the same > instance. > > I also tried rebinding everything from SP 12 for DB2, and restarted the > db, with no success. > > Any info would be appreciated. > > Joel > -------------------------- > > > 2006-10-04 09:03:15,263 ERROR [NodeHeartbeatThread] > net.ubiquity.conference.server.confapp.nodeservices.NodeServiceController > - DatabaseException: node service controller fails to update heart > beat > com.ibm.db2.jcc.b.SqlException: DB2 SQL error: SQLCODE: -805, SQLSTATE: > 51002, SQLERRMC: NULLID.SYSLH205 0X5359534C564C3031 > running com.ibm.db2.jcc.b.SqlException: DB2 SQL error: SQLCODE: -805, > SQLSTATE: 51002, SQLERRMC: NULLID.SYSLH205 0X5359534C564C3031 > at > net.ubiquity.conference.server.confapp.dbcontrol.impl.NodeServiceDbControllerImpl.updateNodeLease(NodeServiceDbControllerImpl.java(Compiled > Code)) > at > net.ubiquity.conference.server.confapp.nodeservices.NodeServiceController$NodeHeartbeatThread.run(NodeServiceController.java(Compiled > Code)) > ---------------------------------
From: Knut Stolze on 4 Oct 2006 09:33 misterutterbag(a)yahoo.com wrote: > Stack trace below. > > Only happens in WebSphere 6.0. > DB2 v 8.2. FP12. > > Only against 1 database. I have other databases in this database > instance, but they don't seem to have this problem. > > Looked up SQLCODE: -805. It said either > a) the client and server versions don't match (which doesn't make > sense, because we've run the same versions since May with no problem) > b) There was an SQL PKG missing, which doesn't seem right, because > you'd think it would be missing from the other databases in the same > instance. > > I also tried rebinding everything from SP 12 for DB2, and restarted the > db, with no success. You are using JDBC, right? JDBC is based on CLI. And if you do not close your statements properly, it may happen that you run out of CLI statement handles. There is an excellent article here that explains it in more detail: http://tinyurl.com/pwq66 -- Knut Stolze DB2 Information Integration Development IBM Germany
From: Purple-D on 4 Oct 2006 12:31 yes we had this issue a few days back. I did a rebind with clipkg 25 which solved it. Like Knut suggested, the base issue is that cursors are probably not being closed correctly and thus running out of handles. I found that monitring the applheapsz gives you a good indication of how you are using the resources in your application... Iam sure there are other ways, but this is what was helpful for me. Cheers! Knut Stolze wrote: > misterutterbag(a)yahoo.com wrote: > > > Stack trace below. > > > > Only happens in WebSphere 6.0. > > DB2 v 8.2. FP12. > > > > Only against 1 database. I have other databases in this database > > instance, but they don't seem to have this problem. > > > > Looked up SQLCODE: -805. It said either > > a) the client and server versions don't match (which doesn't make > > sense, because we've run the same versions since May with no problem) > > b) There was an SQL PKG missing, which doesn't seem right, because > > you'd think it would be missing from the other databases in the same > > instance. > > > > I also tried rebinding everything from SP 12 for DB2, and restarted the > > db, with no success. > > You are using JDBC, right? JDBC is based on CLI. And if you do not close > your statements properly, it may happen that you run out of CLI statement > handles. There is an excellent article here that explains it in more > detail: http://tinyurl.com/pwq66 > > -- > Knut Stolze > DB2 Information Integration Development > IBM Germany
From: Knut Stolze on 4 Oct 2006 13:45
Purple-D wrote: > yes we had this issue a few days back. I did a rebind with clipkg 25 > which solved it. Just be aware that this doesn't really solve the problem - it just delays the point when you run out of packages. Maybe the delay is big enough that you don't hit the issue any longer, but this is not a sure thing. -- Knut Stolze DB2 Information Integration Development IBM Germany |