|
Problem IC66659
|
Status: Closed |
THE MON_GET_LOCKS TABLE FUNCTION SOMETIMES REPORTS CACHED, UNUSED LOCK STRUCTURES |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - 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,the records showing *
* LOCK_MODE='N' are the cached lockstructures which 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: *
* First fixed in DB2 v9.7 FP2 *
**************************************************************** |
| Local Fix: |
Ignore the records with LOCK_MODE='N' or exclude them from the
select query. |
| available fix packs: |
DB2 Version 9.7 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows
|
| Solution |
First fixed in DB2 v9.7 FP2 |
| Workaround |
not known / see Local fix |
| BUG-Tracking |
forerunner : APAR is sysrouted TO one or more of the following: IC66933
follow-up : |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 24.02.2010
25.05.2010
25.05.2010 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.FP2
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.2
|
 |
