Neueste VersionenFixList
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
Haben Sie Probleme? - Kontaktieren Sie uns.
Kostenlos registrieren anmeldung-x26
Kontaktformular kontakt-x26

DB2 - Problembeschreibung

Problem IC87870 Status: Geschlossen

MON_GET_LOCKS DOES NOT SHOW INFORMATION WHEN USING <TABLE_SCHEMA> AND
<TABLE_NAME>

Produkt:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problembeschreibung:
Even though there are locks held on a table the MON_GET_LOCKS 
table function shows no rows when queried using table_schema and 
table_name. 
 
To reproduce 
 
- db2 "create table test.test (a char(3))" 
- db2 +c "insert into test.test values('111')" 
- db2 +c "select * from sysibmadm.locks_held where tabschema = 
'TEST' and tabname = 'TEST' " 
==> 2 locks 
- db2 +c "select * from table 
(MON_GET_LOCKS(CLOB('<table_schema>TEST</table_schema><table_nam 
e>TEST</table_name>'),-1)) AS T " 
==> none 
 
The issue does not occur on Windows.
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 10.1 and Fix Pack 2                   * 
****************************************************************
Local-Fix:
The following query will show the locks (Substitute schema and 
table name appropriately) 
db2 +c "select * from table(MON_GET_LOCKS(CLOB(''),-2)) where 
tab_file_id = (select tableid from syscat.tables where 
tabname='TEST' and tabschema='TEST')"
verfügbare FixPacks:
DB2 Version 10.1 Fix Pack 2 for Linux, UNIX, and Windows
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

Lösung
Problem was first fixed in DB2 Version 10.1 and Fix Pack 2
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
04.11.2012
17.12.2012
17.12.2012
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version
10.1.0.2 FixList
10.5.0.2 FixList