home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Neueste VersionenFixList
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
Haben Sie Probleme? - Kontaktieren Sie uns.
Kostenlos registrieren anmeldung-x26
Kontaktformular kontakt-x26

DB2 - Problembeschreibung

Problem IT01968 Status: Geschlossen

LOCK TIMEOUT INCREMENTS BEFORE ACTUAL TIMEOUT IN SYSIBMADM.SNAPDB WHEN
EVENT MONITOR IS ON.

Produkt:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problembeschreibung:
Increment in the lock timeout value can be noticed without the 
actual timeout occurs, There will be no SQL0911N error in the 
db2diag.log but querying db2 "select lock_timeouts from 
sysibmadm.snapdb" will show different results.Below given 
example explains the behavior 
 
1- First, create the SAMPLE database 
db2sampl 
 
2-Create a dummy table 
db2 connect to sample 
db2 "create table test (col1 char(1))" 
 
3-Change and verify your config. 
db2 "update db cfg using MON_LOCKWAIT HISTORY immediate" 
db2 "update db cfg for sample using LOCKTIMEOUT 60" 
 
db2 "get db cfg" 
 
 Lock timeout (sec)                        (LOCKTIMEOUT) = 60 
 Lock wait events                         (MON_LOCKWAIT) = 
HISTORY 
 Lock wait event threshold               (MON_LW_THRESH) = 
5000000 
 
 
4-Create the event monitor and start it. 
db2 "create event monitor mylockmon for locking write to 
unformatted event table autostart" 
db2 set event monitor mylockmon state 1 
 
5-Check the current value for lock_timeouts 
db2 "select lock_timeouts from sysibmadm.snapdb" 
 
 
6-SESSION A, create the lock situation 
db2 +c lock table test in exclusive mode 
 
 
7-SESSION B, create the lockwait situation 
db2 connect to sample 
db2 "select count(*) from test" 
 
 
8-Wait more then MON_LW_THRESH value (+5 sec) 
 
9-SESSION A, commit 
db2 commit 
 
10-Check the current value for lock_timeouts. The number should 
be increased by 1. 
db2 "select lock_timeouts from sysibmadm.snapdb"
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Update db2 version V10.5 to fixpack 5                        * 
****************************************************************
Local-Fix:
Use MON_GET_WORKLOAD routine
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
Update db2 version V10.5 to fixpack 5
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
22.05.2014
21.10.2014
21.10.2014
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version
10.5.0.4 FixList