|
Problem IC95045
|
Status: Closed |
CLI OR .NET APPLICATION WITH PUREQUERY CLIENT OPTIMIZATION MAY THROW SQL0805N WHEN USING FORCESINGLEBINDISOLATION OPTION. |
| product: |
DB2 FOR LUW / DB2FORLUW / A50 - 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: *
* All DB2 Users using PureQuery *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to v105fp3 and later *
**************************************************************** |
| Local Fix: |
|
| available fix packs: |
DB2 Version 10.5 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.5 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Cancun Release 10.5.0.4 (also known as Fix Pack 4) for Linux, UNIX, and Windows
DB2 Version 10.5 Fix Pack 9 for Linux, UNIX, and Windows
|
| Solution |
Problem fixed in v105fp3 |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 20.08.2013
27.02.2014
27.02.2014 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.5.0.3
|
 |
| 10.5.0.3
|
|
