db2 bind ...
может, после какого-то фикса этот пакет должен появиться? тебе же вроде ответили.

а ты поставь и посмотри. извини, но я не могу понять -- ты издеваешься или в самом деле не понимаешь?

вот тебе еще:
http://www.developer.ibm.com/tech/faq/individual?oid=2:81737


Frequently Asked Questions

FAQ help
Search tips


Why do I get an SQL0805N with NULLID.SYSLH203 when doing a select in JDBC using JCC type 4 driver in DB2 UDB version 8?

A: The JCC driver is a common platform driver that combines the features of the JDBC drivers previously available on multiple platforms, including Windows, Unix, z/OS, etc. The garbage collection is not freeing these resources in the JCC driver as a result of a requirement from the z/OS environment. In the case of z/OS, prepared statements must be re-prepared after a commit, so DB2 maintains a list of open statements associated with a connection in the abstract machine. Whenever a commit occurs, this list of open statements is used to mark the statement to be in the "unprepared" state.
As a result, when an object goes out of scope, it is not automatically garbage collected because it still has a reference to the connection's open statement list. Therefore, applications which rely on garbage collection, as opposed to explicitly closing the statements when they are no longer used, may eventually exhaust the available statement resources.

This is NOT considered a defect, but is currently a design limitation that is changed in fixpack 3. At present, all statements should be closed explicitly when they are no longer used. Fixpack 3 is currently available.

Reference: 81737 / 102251 Date: 28 Sep 2003 Keyword: General [ Return to main page ]