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.
> 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.
> 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
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.
> > 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
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
> > 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