|
Problem IC91952
|
Status: Closed |
SQL0119N RETURNED WHEN SQLCA USES DIFFERENT PARAMETER MARKERS FOR THE SAME CONSTANT |
| product: |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 |
| Problem description: |
The statement concentrator treats two constant literals
differently when
modifying a SQL statement, giving them two different parameter
markers. As an example, SELECT 'ABC' ... GROUP BY 'ABC' changes
to SELECT :L0 ... GROUP BY :L5, which when evaluated does not
match and thus causes SQL0119N.
An example of db2diag.log output is shown below:
2012-11-28-09.17.03.462896-300 I68985753A5579 LEVEL: Warning
PID : 10551386 TID : 217007 PROC : db2sysc
0
INSTANCE: XXXXX NODE : 000 DB : XXXXX
APPHDL : 0-36196 APPID:
204.61.147.207.18783.121127211130
AUTHID : L5358517
EDUID : 217007 EDUNAME: db2agent (XXXXX) 0
FUNCTION: DB2 UDB, access plan manager,
sqlra_statement_concentrator,
probe:140
MESSAGE : Bad modified statement
DATA #1 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes
sqlcaid : SQLCA sqlcabc: 136 sqlcode: -119 sqlerrml: 17
sqlerrmc: SHORT_DESCRIPTION
sqlerrp : SQLNQ16F
sqlerrd : (1) 0x801A006D (2) 0x00000000 (3)
0x00000000
(4) 0x00000000 (5) 0xFFFFFEF2 (6)
0x00000000
sqlwarn : (1) (2) (3) (4) (5) (6)
(7) (8) (9) (10) (11)
sqlstate:
DATA #2 : String with size, 4639 bytes
<<SQL STATEMENT GOES HERE>> |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* DB2 LUW version 10.1 *
****************************************************************
* PROBLEM DESCRIPTION: *
* The statement concentrator treats two constant literals *
* differently when *
* modifying a SQL statement, giving them two different *
* parameter *
* markers. As an example, SELECT 'ABC' ... GROUP BY 'ABC' *
* changes *
* to SELECT :L0 ... GROUP BY :L5, which when evaluated does *
* not *
* match and thus causes SQL0119N. *
* *
* An example of db2diag.log output is shown below: *
* *
* 2012-11-28-09.17.03.462896-300 I68985753A5579 LEVEL: *
* Warning *
* *
* PID : 10551386 TID : 217007 PROC : *
* db2sysc *
* 0 *
* INSTANCE: XXXXX NODE : 000 DB : *
* XXXXX *
* APPHDL : 0-36196 APPID: *
* 204.61.147.207.18783.121127211130 *
* AUTHID : L5358517 *
* EDUID : 217007 EDUNAME: db2agent (XXXXX) 0 *
* FUNCTION: DB2 UDB, access plan manager, *
* sqlra_statement_concentrator, *
* probe:140 *
* MESSAGE : Bad modified statement *
* DATA #1 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes *
* sqlcaid : SQLCA sqlcabc: 136 sqlcode: -119 *
* sqlerrml: 17 *
* *
* sqlerrmc: SHORT_DESCRIPTION *
* sqlerrp : SQLNQ16F *
* sqlerrd : (1) 0x801A006D (2) 0x00000000 (3) *
* 0x00000000 *
* (4) 0x00000000 (5) 0xFFFFFEF2 (6) *
* 0x00000000 *
* sqlwarn : (1) (2) (3) (4) (5) *
* (6) *
* (7) (8) (9) (10) (11) *
* sqlstate: *
* DATA #2 : String with size, 4639 bytes *
* <<SQL STATEMENT GOES HERE>> *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 LUW 10.1 fixpack 3 *
**************************************************************** |
| Local Fix: |
|
| available fix packs: |
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 |
|
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 29.04.2013
19.11.2013
19.11.2013 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.1.0.3
|
 |
| 10.1.0.3
|
|
