DB2 FOR LUW / DB2FORLUW / 970 - DB2

When forceSingleBindIsolation is set to TRUE, it will create DB2 
package for only a single isolation level. It will not have 
number appended to the name of the package to indicate the 
isolation level. However CLI or .NET application as if oblivious 
to forceSingleBindIsolation option, will try to look for 
packages at multiple isolation levels, instead of finding all 
the statements in single package. This may result in SQL0805N 
package not found error.

**************************************************************** 
* USERS AFFECTED:                                              * 
* Users using PureQuery Client Optimization                    * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* First fixed in DB2 V9.7 Fixpack 9                            * 
****************************************************************

DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows
 

First fixed in DB2 V9.7 Fixpack 9

Do not use forceSingleBindIsolation with PQR. It will generate 
packages for each isolation level. Manually remove packages for 
all other isolation levels except the one which you want to use.

forerunner  : APAR is sysrouted TO one or more of the following: IC95044 IC95045 
follow-up : 

Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :

17.06.2013
16.12.2013
16.12.2013

9.7.FP9