> Are there any particular DB or DBM parameters that would cause more
> occurrences of this SQL error:
[quoted text clipped - 9 lines]
> Thanks in advance for any tips.
> TW
Usually caused by programs not closing cursors when they should.
TechWitch - 22 Jan 2007 23:31 GMT
> Usually caused by programs not closing cursors when they should.
Now that makes some sense. One of these days I'm gonna get that darn
code vetted before it goes to production. Ah well, guess I'll have to
open up my box of db2 bandaids again....
TW
TechWitch - 24 Jan 2007 16:22 GMT
Is there any performance implication with making more bind packages
available?
--TW
TechWitch - 07 Feb 2007 05:25 GMT
> > [IBM][CLI Driver][DB2/AIX64] SQL0805N Package "NULLID.SYSLH106
> > 0X5359534C564C3031" was not found. SQLSTATE=51002
< snip >
> Usually caused by programs not closing cursors when they should.
I've done a client trace, and reviewing the output. It's like trying
to find a needle in a haystack. I did notice that the client which
makes the call and has the application code is in 32 bit while the db2
instance is 64 bit. I wonder if this could be a factor? We did not
experience the problem before when both the client and instance were
32 bit...
TW