|
Problem IC77123
|
Status: Closed |
ERROR IS NOT REPORTED FOR CALL STATEMENT WITH PARAMETER MARKER USING ARRAY INPUT SPECIFIED WITH SQL_ATTR_PARAMSET_SIZE. |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
Consider following testcase
sqlprepare 1 "call test1(?)" -3
getmemarray 1 1 3 sql_c_long
updateelem 1 0 value 1
updateelem 1 1 value 2
updateelem 1 2 value 3
sqlbindparameter 1 1 sql_param_input sql_c_long sql_integer 0 0
1 memarray
sqlsetstmtattr 1 sql_attr_paramset_size 3
sqlexecute 1
SQLExecute shows success executing call statement with only
first element of array.
This is misleading since call statement doesn't support array
input.
So for sql_attr_paramset_size > 1, error should be thrown. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* ALL *
****************************************************************
* PROBLEM DESCRIPTION: *
* ERROR IS NOT REPORTED FOR CALL STATEMENT WITH PARAMETER *
* MARKER *
* USING ARRAY INPUT SPECIFIED WITH SQL_ATTR_PARAMSET_SIZE. *
****************************************************************
* RECOMMENDATION: *
* Upgrade to db2 v97fp5 or later. *
**************************************************************** |
| Local Fix: |
|
| available fix packs: |
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 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
|
| Solution |
Fixed in db2 v97fp5.
ERROR WILL BE REPORTED FOR CALL STATEMENT WITH PARAMETER MARKER
USING ARRAY INPUT SPECIFIED WITH SQL_ATTR_PARAMSET_SIZE. |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 23.06.2011
08.12.2011
08.12.2011 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.FP5
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.5
|
 |
