|
Problem IC95044
|
Status: Closed |
CLI OR .NET APPLICATION WITH PUREQUERY CLIENT OPTIMIZATION MAY THROW SQL0805N WHEN USING FORCESINGLEBINDISOLATION OPTION. |
| product: |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 |
| Problem description: |
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. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* Users using PureQuery Client Optimization *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* First fixed in DB2 V10.1 Fixpack 3 *
**************************************************************** |
| Local Fix: |
|
| available fix packs: |
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows
|
| Solution |
First fixed in DB2 V10.1 Fixpack 3 |
| Workaround |
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. |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 20.08.2013
02.12.2013
02.12.2013 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.1.0.3
|
 |
| 10.1.0.3
|
|
