|
Problem IC66567
|
Status: Closed |
DATA_PARTITION_ID COLUMN FROM SYSIBMADM.MON_LOCKWAITS ADMIN VIEW IS INCORRECT |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
When locks on a partitioned table exist, and you query the
SYSIBMADM.MON_LOCKWAITS ADMIN VIEW, the values in the
DATA_PARTITION_ID, TABSCHEMA and TABNAME in the admin view
COLUMN may return a blank "-" value.
Example:
Session 1: db2 "create table test (dt date) PARTITION BY RANGE
(dt) (STARTING '2009-01-01' ENDING '2009-01-20' every 1 days)"
Session 2: db2 +c "select * from test with rr"
Session 3: db2 "load from /dev/null of del replace into test
nonrecoverable"
Session 1: db2 "select tabschema, tabname,
DATA_PARTITION_ID,LOCK_MODE,LOCK_CURRENT_MODE,LOCK_MODE_REQUESTE
D
from sysibmadm.mon_lockwaits"
TABSCHEMA TABNAME DATA_PARTITION_ID LOCK_MODE
LOCK_CURRENT_MODE LOCK_MODE_REQUESTED
----------------------------------------------------------------
--------------------------------
- - - S
- Z
- - - S
- Z
- - - S
- Z
3 record(s) selected.
From the InfoCenter, we state the "DATA_PARTITION_ID" column
element is only applicable to partitioned tables and partitioned
indexes. Otherwise, the value of this monitor element is NULL.
When returning lock level information, a value of -1 represents
a lock which controls access to the whole table.
In the above case, the value should be -1, which this APAR will
fix to correct the output.
For the fix to take effect, you must run db2updv97 after
applying the fixpack |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* NA *
****************************************************************
* PROBLEM DESCRIPTION: *
* When locks on a partitioned table exist, and you query the *
* *
* SYSIBMADM.MON_LOCKWAITS ADMIN VIEW, the values in the *
* *
* DATA_PARTITION_ID, TABSCHEMA and TABNAME in the admin view *
* *
* COLUMN may return a blank "-" value. *
****************************************************************
* RECOMMENDATION: *
* Fixed in V9.7 FP2 *
**************************************************************** |
| Local Fix: |
You can use MON_FORMAT_LOCK_NAME table function by passing in
the lockname to get the table name and schema.
schema of the table |
| 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 |
Fixed in V9.7 FP2 |
| Workaround |
not known / see Local fix |
| BUG-Tracking |
forerunner : APAR is sysrouted TO one or more of the following: IC66991
follow-up : |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 22.02.2010
08.07.2010
08.07.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
|
 |
