The problem is with DB2® (refer to DB2 APAR JR17023 for
more information).
To solve the problem, either:
- Upgrade DB2 to DB2 7.2 Fix Pack 7 (or higher)
or
- Add the following lines to the [COMMON] section in the
db2cli.ini on the client side:
PATCH2=30
DEFERREDPREPARE=0
There is also a workaround in WebSphere Application Server. The
workaround is to disable the WebSphere Prepared Statement Cache by setting
the Statement Cache Size to 0 for the data source. There is a
performance degradation with this workaround, so it is not
recommended.
|