DB2 - Problem description
Problem IT22606 | Status: Closed |
A LOCKING EVENT MONITOR CAN INCORRECTLY CAPTURE STATIC STMT TEXTAND REPORT INCORRECT NUMBER OF INPUT VARIABLES | |
product: | |
DB2 FOR LUW / DB2FORLUW / B10 - DB2 | |
Problem description: | |
When a LOCKING event monitor captures events that involve STATIC sql, the stmt_text may not be properly captured. Furthermore, when that statement includes parameter markers the event monitor output can show a mismatching number of parameter markers to the stmt text. For example here is an output snippet from the output of the db2evmonfmt tool illustrating the problem: ... Stmt text : declare TESTCURSOR cursor for select t1.COL1, t1.COL2, t1.COL3, t1.TS from MYTAB t1 where COL2 = :H00058 and COL3 = :H00059 order by t1.COL1 ASC Input variable 1 Type : INTEGER Data : 3 Reopt : no Null : no Input variable 2 Type : VARCHAR Data : 2015-12-11 Reopt : no Null : no Input variable 3 Type : INTEGER Data : 7 Reopt : no Null : no Input variable 4 Type : INTEGER Data : 4 Reopt : no Null : no ... In the snippet above we see that statement has 2 input variables, while later on we list 4. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * ALL * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to v11.1 FP2 or later * **************************************************************** | |
Local Fix: | |
N/A | |
Solution | |
Workaround | |
not known / see Local fix | |
BUG-Tracking | |
forerunner : IT17287 follow-up : | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 02.10.2017 13.10.2017 13.10.2017 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) |