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. |
****************************************************************
* 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: *
* Upgrade to Fixpack 3 *
**************************************************************** |
