Great!

First I installed FixPack 4 but that did not help. Then i checked that
there was

SYSLH200
SYSLH201
SYSLH202
SYSLH203

Packages in my system. After that I ran that db2jdbcbind with -size 20
and now I have packages from SYSLH200 to SYSLH413. And now the system is
working well so far...

I have absolutely no idea what I just did... This seemed to be stuff
normal developer should not usually be involved with. Do I have to be
woried about of something related to this operation?

Is this the think I have to do with every DB2 database when start to use
it with Java applications?

I'll be eternally gratefull.

PM (pm3iinc-nospam) wrote:
>>Unfortunately, I don't know what kind of package SYSLH203 is...
>
>
> ... having to do with the db2jdbcbind command...
> L : large package (385 sections)
> H : with hold
> 2 : some isolation level i think (rr, rs, cs, ur, ...)
> 03 is a sequence number
>
> Doc describes them as :
> Table 35. DB2 CLI Bind Files and Package Names
>
> Dynamic Placeholders - Large Package WITH HOLD
>
>
> Using db2jdbcbind with the -size 20 option may solve the problem?
>
> Do you have packages like this in your db?
> SYSLH200
> SYSLH201
> SYSLH202
> SYSLH203
> SYSLH204
> SYSLH205
> SYSLH206
> SYSLH207
> SYSLH208
> SYSLH209
> SYSLH20A
> SYSLH20B
> SYSLH20C
> SYSLH20D
> SYSLH20E
> SYSLH20F
> SYSLH210
> SYSLH211
> SYSLH212
> SYSLH213
>
> Also verify that someone bound db2schema.bnd on the server. (this may also
> be missing if the packages are not there.)
>
> PM
>
>