|
Problem IC69385
|
Status: Closed |
BIND FROM DB2SQLJCUSTOMIZE OR DB2SQLJBIND CAN CREATE PACKAGE DESPITE FAILURE |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - 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.7, fixpack 3 *
**************************************************************** |
| Local Fix: |
N/A |
| available fix packs: |
DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows
|
| Solution |
Fixed in db2 for luw v9.7, fixpack 3 |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 22.06.2010
23.09.2010
23.09.2010 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.FP3
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.3
|
 |
| 9.7.0.3
|
|
