SQL0805N affected by DB/DBM CFG ?

[TechWitch]

Are there any particular DB or DBM parameters that would cause more
occurrences of this SQL error:

[IBM][CLI Driver][DB2/AIX64] SQL0805N Package "NULLID.SYSLH106
0X5359534C564C3031" was not found. SQLSTATE=51002

I know I can make more packages available to the CLI interface, but I'm
just curious is our current configuration is allowing more applications
to execute than should be allowed. We haven't been able to re-produce
the error, as it only appears in our production environment.

Thanks in advance for any tips.
TW

[Mark A]

"TechWitch" <te********@gmail.comwrote in message
news:11*********************@51g2000cwl.googlegrou ps.com...

Are there any particular DB or DBM parameters that would cause more
occurrences of this SQL error:

[IBM][CLI Driver][DB2/AIX64] SQL0805N Package "NULLID.SYSLH106
0X5359534C564C3031" was not found. SQLSTATE=51002

I know I can make more packages available to the CLI interface, but I'm
just curious is our current configuration is allowing more applications
to execute than should be allowed. We haven't been able to re-produce
the error, as it only appears in our production environment.

Thanks in advance for any tips.
TW

Usually caused by programs not closing cursors when they should.

[TechWitch]

Mark A wrote:

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]

Is there any performance implication with making more bind packages
available?

--TW

[TechWitch]

On Jan 22, 5:11 pm, "Mark A" <[e-mail]:

[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