|
Problem IT19663
|
Status: Closed |
PROBLEM WITH THE GENERATED C/C++ CODE FROM THE DB2 PREP. IT CANNOT COMPILE WHEN IT CONTAINS THE ARRAY INSERT/UPDATE. |
| product: |
DB2 FOR LUW / DB2FORLUW / B10 - DB2 |
| Problem description: |
Problem with the generated C/C++ code from the db2 prep command.
It cannot compile the generated code.
There seems to be a difference between the FETCH and the
UPDATE/DELETE/INSERT.
FETCH generates the proper code, but UPDATE uses the invalid
variable, will get the following compilation error.
: error: '__sqla_loop_itr' was not declared in this scope
If we remove the indicator from the UPDATE statement, it is
generating the code correctly and compiling successfully.
Problem is only when we use indicator along with variable in
UPDATE statement. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* ALL *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 11.1 Mod 2 Fix Pack 2 or higher *
**************************************************************** |
| Local Fix: |
If we remove the indicator from the UPDATE statement, it is
generating the code correctly and compiling successfully.
Problem is only when we use indicator along with variable in
UPDATE statement. |
| available fix packs: |
DB2 Version 11.1 Mod 2 Fix Pack 2 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod2 Fix Pack2 iFix001 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod2 Fix Pack2 iFix002 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod 3 Fix Pack 3 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod3 Fix Pack3 iFix001 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod3 Fix Pack3 iFix002 for Linux, UNIX, and Windows
|
| Solution |
First fixed in DB2 11.1 Mod 2 Fix Pack 2 |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 13.03.2017
23.06.2017
23.06.2017 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
