home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Latest versionsfixlist
11.1.0.7 FixList
10.5.0.9 FixList
10.1.0.6 FixList
9.8.0.5 FixList
9.7.0.11 FixList
9.5.0.10 FixList
9.1.0.12 FixList
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IT03890 Status: Closed

MON_GET_LOCKS FAILS WITH SQL0171N

product:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problem description:
$ db2 "SELECT count(*) FROM 
TABLE(MON_GET_LOCKS(CLOB('<table_schema>SCHEMA</table_schema><ta 
ble_name>TABLE</table_name><lock_mode>IN:IS:IX</lock_mode>'),-1 
))" 
 
1 
----------- 
SQL0171N  The data type, length or value of the argument for the 
parameter in position "1" of routine "MON_GET_LOCKS" is 
incorrect. Parameter name:  "SEARCH_ARGS/TABLE_SCHEMA". 
SQLSTATE=42815 
 
You can create a reproduction if you add a clause to the query 
that has a colon in it, such as <lock_mode>.  If you put it 
before the <table_schema> clause the query will work, but it you 
put it after the query will fail.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to  Version 10.5 Fix Pack 5.                         * 
****************************************************************
Local Fix:
N/A
Solution
First fixed in Version 10.5 Fix Pack 5.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
20.08.2014
02.09.2015
02.09.2015
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.5.0.5 FixList