can anyone give me any information about this message?

SQL State: 51002
Native: -805
Message: [IBM][CLI Driver][DB2/LINUXX8664] SQL0805N Package
"NULLID.SYSLH203 0X5359534C564C3031" was not found. SQLSTATE=51002
- Error state:51002 Error code:-805

obviously a system package can not be found. But I don't know why, where
has it gone? How do I get it back? I'm scared :'(

-R-

Jurgen Haan wrote:
[color=blue]
> can anyone give me any information about this message?
>
> SQL State: 51002
> Native: -805
> Message: [IBM][CLI Driver][DB2/LINUXX8664] SQL0805N Package
> "NULLID.SYSLH203 0X5359534C564C3031" was not found. SQLSTATE=51002
> - Error state:51002 Error code:-805
>
> obviously a system package can not be found. But I don't know why, where
> has it gone? How do I get it back? I'm scared :'(
>
> -R-[/color]

From DBForums:

"Previously, I encountered the same error but for the package SYSLH203.
I tried a solution found on the Internet:
db2jdbcbind -url jdbc:db2://LOCALHOST:50000/recon -user xxxxx -password
xxxxx -size 20
This command solved the problem for SYSLH203"

--
Anton Versteeg
IBM Netherlands

Anton Versteeg wrote:
[color=blue]
> "Previously, I encountered the same error but for the package SYSLH203.
> I tried a solution found on the Internet:
> db2jdbcbind -url jdbc:db2://LOCALHOST:50000/recon -user xxxxx -password
> xxxxx -size 20
> This command solved the problem for SYSLH203"
>[/color]

Hmz... this results in a:

DB2Binder stopped: Failure to create connection for binding
SQL code: -4499
SQL state: null
Message: A communication error has been detected. Communication
protocol being used: Reply.fill(). Communication API being used:
InputStream.read(). Location where the error was detected: insufficient
data. Communication function detecting the error: *. Protocol specific
error codes(s) TCP/IP SOCKETS



another issue that might be connected:

db2inst1@Data:/opt/IBM/db2/V8.1/bnd> db2 bind db2schema.bnd

LINE MESSAGES FOR db2schema.bnd
------ --------------------------------------------------------------------
SQL0061W The binder is in progress.
5048 SQL0101N The statement is too long or too complex.
SQLSTATE=54001
5236 SQL0101N The statement is too long or too complex.
SQLSTATE=54001
5429 SQL0101N The statement is too long or too complex.
SQLSTATE=54001
SQL0082C An error has occurred which has terminated
processing.
SQL0092N No package was created because of previous errors.
SQL0091N Binding was ended with "5" errors and "0" warnings.



any thoughts on this?
(I'm not even sure what to ask)

-R-

Well,

we've had something like that happen - though I don't recall the
0X5359534C564C3031 part of the package identifier. Anyway, per default
three packages of this particular flavor are created when you bind the
CLI packages - SYSLH200,201, and 202. Try going to the $BND directory
and issue

db2 bind @db2cli.lst blocking all grant public clipkg nn

where nn is some number greater than 3.

/T

Well,

we've had something like that happen - though I don't recall the
0X5359534C564C3031 part of the package identifier. Anyway, per default
three packages of this particular flavor are created when you bind the
CLI packages - SYSLH200,201, and 202. Try going to the $BND directory
and issue

db2 bind @db2cli.lst blocking all grant public clipkg nn

where nn is some number greater than 3.

/T

Tomas wrote:
[color=blue]
> db2 bind @db2cli.lst blocking all grant public clipkg nn
>
> /T
>[/color]

well that did the trick.. Great!! :)

Now that the critical part is over; what is this package used for?
SYSLH203. Is it used for exception handling in DB2?
Because the error occured when we were performing a rather large
transaction, and when the lock count reached around 1300, this package
is called. Furthermore, I understand the naming of these packages follow
certain rules, the H for hold en the 3 for cursor stability, but what
where they exactly?

-R-