|
Problem IC69386
|
Status: Closed |
BIND FROM DB2SQLJCUSTOMIZE OR DB2SQLJBIND CAN CREATE PACKAGE DESPITE FAILURE |
| product: |
DB2 FOR LUW / DB2FORLUW / 980 - DB2 |
| Problem description: |
Binding a package via db2sqljcustomize or db2sqljbind can result
in a package being created even though the bind returns an
error.
If the package is executed after this has occurred, then
statements that failed to bind will fail with a -518 sqlcode |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* Any use of DB2SQLJCUSTOMIZE OR DB2SQLJBIND *
****************************************************************
* PROBLEM DESCRIPTION: *
* Package incorrectly saved at the end of a failed bind *
****************************************************************
* RECOMMENDATION: *
* move to db2 for luw v9.5, fixpack 6 *
**************************************************************** |
| Local Fix: |
N/A |
| available fix packs: |
DB2 Version 9.8 Fix Pack 4 for AIX and Linux
DB2 Version 9.8 Fix Pack 5 for AIX and Linux
|
| Solution |
Fixed in db2 for luw v9.5, fixpack 6 |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 22.06.2010
22.08.2011
22.08.2011 |
| Problem solved at the following versions (IBM BugInfos) |
9.5.FP6
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.8.0.4
|
 |
