|
Problem IC98900
|
Status: Geschlossen |
LOCKING EVENT MONITOR NOT POPULATING LOCK_ACTIVITY_VALUES_EVM_LOCK_FT1 ON DPF |
| Produkt: |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 |
| Problembeschreibung: |
The locking event monitor does not populate
LOCK_ACTIVITY_VALUES_EVM_LOCK_FT1 table on DPF systems.
EXAMPLE:
db2 connect to test
db2 "create event monitor evm_lock_ft1 for locking write to
table"
db2 "select substr(ngname,1,30) ngname, nodenum, in_use from
syscat.nodegroupdef where ngname='IBMDEFAULTGROUP'"
db2 "select substr(tabname,1,50) tabname, substr(tbspace,1,30)
tbspace from syscat.tables where create_time >= current date"
db2 "create table test_dl1 ( i int ) in userspace1"
db2 "create table test_dl2 ( i int ) in userspace1"
db2 "insert into test_dl1 values (1),(2)"
db2 "insert into test_dl2 values (1),(2)"
db2 SET EVENT MONITOR EVM_LOCK_FT1 STATE 1
db2 "SELECT evmonname, EVENT_MON_STATE(evmonname) as ENABLED
FROM syscat.eventmonitors"
# Session 1
1)
db2 +c "update test_dl1 SET i = 4 WHERE i = 1"
3)
db2 +c "update test_dl2 SET i = 2 where i = 1"
# Session 2
2)
db2 +c "update test_dl2 SET i = 2 where i = 1"
4)
db2 +c "update test_dl1 SET i = 4 WHERE i = 1"
db2 "select * from LOCK_ACTIVITY_VALUES_EVM_LOCK_FT1"
The above test is not valid. However, an application that
causes the deadlock should populate the
LOCK_ACTIVITY_VALUES_EVM_LOCK_FT1. |
| Problem-Zusammenfassung: |
****************************************************************
* USERS AFFECTED: *
* LOCKING EVENT MONITOR NOT POPULATING *
* LOCK_ACTIVITY_VALUES_EVM_LOCK_FT1 ON DPF *
****************************************************************
* PROBLEM DESCRIPTION: *
* The locking event monitor does not populate *
* LOCK_ACTIVITY_VALUES_EVM_LOCK_FT1 table on DPF systems. *
* *
* EXAMPLE: *
* *
* db2 connect to test *
* db2 "create event monitor evm_lock_ft1 for locking write to *
* table" *
* db2 "select substr(ngname,1,30) ngname, nodenum, in_use from *
* syscat.nodegroupdef where ngname='IBMDEFAULTGROUP'" *
* db2 "select substr(tabname,1,50) tabname, *
* substr(tbspace,1,30) *
* tbspace from syscat.tables where create_time >= current *
* date" *
* db2 "create table test_dl1 ( i int ) in userspace1" *
* db2 "create table test_dl2 ( i int ) in userspace1" *
* db2 "insert into test_dl1 values (1),(2)" *
* db2 "insert into test_dl2 values (1),(2)" *
* db2 SET EVENT MONITOR EVM_LOCK_FT1 STATE 1 *
* db2 "SELECT evmonname, EVENT_MON_STATE(evmonname) as ENABLED *
* FROM syscat.eventmonitors" *
* *
* # Session 1 *
* *
* 1) *
* db2 +c "update test_dl1 SET i = 4 WHERE i = 1" *
* 3) *
* db2 +c "update test_dl2 SET i = 2 where i = 1" *
* *
* *
* # Session 2 *
* *
* 2) *
* db2 +c "update test_dl2 SET i = 2 where i = 1" *
* 4) *
* db2 +c "update test_dl1 SET i = 4 WHERE i = 1" *
* *
* *
* db2 "select * from LOCK_ACTIVITY_VALUES_EVM_LOCK_FT1" *
* *
* The above test is not valid. However, an application that *
* causes the deadlock should populate the *
* LOCK_ACTIVITY_VALUES_EVM_LOCK_FT1. *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 LUW version 10.5 fp3 *
**************************************************************** |
| Local-Fix: |
|
| verfügbare FixPacks: |
DB2 Cancun Release 10.5.0.4 (also known as Fix Pack 4) for Linux, UNIX, and Windows
DB2 Version 10.5 Fix Pack 9 for Linux, UNIX, and Windows
|
| Lösung |
|
| Workaround |
keiner bekannt / siehe Local-Fix |
| Weitere Daten |
Datum - Problem gemeldet :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
| 22.01.2014
15.09.2014
15.09.2014 |
| Problem behoben ab folgender Versionen (IBM BugInfos) |
|
| Problem behoben lt. FixList in der Version |
| 10.5.0.4
|
 |
