|
Problem IC84396
|
Status: Closed |
GIVES SEGMENTATION FAULT WHEN SQLEXECUTE CALLED TO INSERT STRING VALUE IN INTEGER FIELD WITH ARRAYINPUTCHAIN |
| product: |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 |
| Problem description: |
When 1st SQLExecute called after setting SQL_ATTR_CHAINING_BEGIN
statement attribute then it gives proper error message but in
2nd SQLExecute it gives segmentation fault instead of proper
error message. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* DB2 Connect users *
****************************************************************
* PROBLEM DESCRIPTION: *
* When SQLEXECUTE called to insert string value in the *
* integer field with arrayinputchain. *
* 1st SQLExecute called after setting SQL_ATTR_CHAINING_BEGIN *
* statement attribute then it gives proper error message but *
* in *
* 2nd SQLExecute it gives segmentation fault instead of proper *
* error message. *
****************************************************************
* RECOMMENDATION: *
* Upgrade to db2_v101fp1 or later releases. *
**************************************************************** |
| Local Fix: |
not to bind string value to integer inside chaining. |
| available fix packs: |
DB2 Version 10.1 Fix Pack 1 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 2 for Linux, UNIX, and Windows
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 |
DB2 V101 Fix Pack 1 |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 14.06.2012
06.11.2012
06.11.2012 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.1.0.1
|
 |
| 10.5.0.1
|
|
