DB2 - Problem description
Problem IC98772 | Status: Closed |
Queries using the XMLSERIALIZE function may not benefit from the statement concentrator | |
product: | |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 | |
Problem description: | |
A dynamic query using the XMLSERIALIZE function with a data type that includes a numeric size literal does not benefit from the statement concentrator (stmt_conc=LITERALS). For example: values XMLSERIALIZE(CONTENT XMLELEMENT(NAME "CHILD", 'A') as VARCHAR(50)) The statement concentrator erroneously replaces the literal 50 with a host variable. This results in SQLCODE -104 and the statement is recompiled without the statement concentrator. A warning is logged in db2diag.log: 2014-01-16-12.26.23.953416-300 I550887E1053 LEVEL: Warning PID : 6431 TID : 46913005021504 PROC : db2sysc INSTANCE: <instance> NODE : 000 DB : TESTDB APPHDL : 0-7 APPID: <appid> AUTHID : <authid> HOSTNAME: <hostname> EDUID : 18 EDUNAME: db2agent (TESTDB) 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: -104 sqlerrml: 33 sqlerrmc: :L1 D, :L0 ) as VARCHAR( <length> sqlerrp : SQLNP01F sqlerrd : (1) 0x801A006D (2) 0x00000000 (3) 0x00000000 (4) 0x00000000 (5) 0xFFFFFD3F (6) 0x00000000 sqlwarn : (1) (2) (3) (4) (5) (6) (7) (8) (9) (10) (11) sqlstate: DATA #2 : String with size, 74 bytes values XMLSERIALIZE(CONTENT XMLELEMENT(NAME CHILD, :L0 ) as VARCHAR(:L1 )) The statement will still compile and execute correctly but without the benefit of the statement concentrator. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * All Platforms * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 LUW v10.1 Fixpack 4 or Higher * **************************************************************** | |
Local Fix: | |
available fix packs: | |
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows | |
Solution | |
First Fixed in DB2 LUW v10.1 Fixpack 4 | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 16.01.2014 09.06.2014 09.06.2014 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) | |
10.1.0.4 |