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 IC66933 Status: Closed

THE MON_GET_LOCKS TABLE FUNCTION SOMETIMES REPORTS CACHED, UNUSED LOCK
STRUCTURES

product:
DB2 FOR LUW / DB2FORLUW / 980 - DB2
Problem description:
The MON_GET_LOCKS table function sometimes reports cached, 
unused lock structures.  This seems to only happen when the 
LOCKLIST is sufficiently high. 
 
Looking at the output of the MON_GET_LOCKS table function, the 
records showing LOCK_MODE='N' are the cached lock structures 
which should not be reported. 
 
$ db2 +c "SELECT LOCK_NAME,LOCK_MODE FROM TABLE (MON_GET_LOCKS( 
NULL, -2))" 
LOCK_NAME                        LOCK_MODE 
-------------------------------- --------- 
01000000010000000100A06156       S 
41414141415A425A7F4760B841       S 
434F4E544F4B4E3128DD630641       S 
02000400000000000000000054       N 
FAFF0080000000000000080054       N 
FAFF0080000000000000070054       N 
FAFF0080000000000000060054       N
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* Users of the MON_GET_LOCKS table function.                   * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* The MON_GET_LOCKS table function sometimes reports           * 
* cached,unused lock structures.  This seems to only happen    * 
* when theLOCKLIST is sufficiently high.Looking at the output  * 
* of the MON_GET_LOCKS table function,therecords showing       * 
* LOCK_MODE='N' are the cached lock structureswhich should not * 
* be reported.$ db2 +c "SELECT LOCK_NAME,LOCK_MODE FROM        * 
* TABLE(MON_GET_LOCKS(NULL, -2))"LOCK_NAME                     * 
*    LOCK_MODE--------------------------------                 * 
* ---------01000000010000000100A06156                          * 
* S41414141415A425A7F4760B841      S434F4E544F4B4E3128DD630641 * 
*      S02000400000000000000000054                             * 
* NFAFF0080000000000000080054      NFAFF0080000000000000070054 * 
*      NFAFF0080000000000000060054      N                      * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Ignore the records with LOCK_MODE='N' or exclude them        * 
* fromtheselect query.  This is first fixed in DB2 v9.8 fix    * 
* pack 3.                                                      * 
****************************************************************
Local Fix:
Ignore the records with LOCK_MODE='N' or exclude them from the 
select query.
available fix packs:
DB2 Version 9.8 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.8 Fix Pack 4 for AIX and Linux
DB2 Version 9.8 Fix Pack 5 for AIX and Linux

Solution
Ignore the records with LOCK_MODE='N' or exclude them from the 
select query.  This is first fixed in DB2 v9.8 fix pack 3.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
05.03.2010
17.01.2011
17.01.2011
Problem solved at the following versions (IBM BugInfos)
9.8.,
9.8.FP3
Problem solved according to the fixlist(s) of the following version(s)
9.8.0.3 FixList