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 IC64798 Status: Geschlossen

MULTIPLE AGENTS CALLING FLUSH OPTIMIZATION PROFILE CACHE WHILE A PROFILE IS
IN USE CAN RESULT IN A LOCK/LATCH DEADLOCK

Produkt:
DB2 FOR LUW / DB2FORLUW / 910 - DB2
Problembeschreibung:
An agent calling FLUSH OPTIMIZATION PROFILE CACHE and an agent 
using an OPT profile can get into a "deadlock" of sorts with one 
agent waiting on a latch while the other is waiting on a lock. 
This looks very similar to APAR IZ26477, but is the result of 
the FLUSH OPTIMIZATION PROFILE CACHE instead of an Online Reorg. 
 
In the latch tracking part of the stack files you will see: 
 
<<<< File = <thread_1> >>>> 
 
timestamp: 2009-09-16-14.56.27.914060 
Holding Latch type: (SQLO_LT_sqlrlc_anchor_common__anchor_latch) 
- Address: (256 
cd9b4c), Line: 71, File: 
/view/db2_v91fp3a_sun64_s070914/vbs/engn/include/sqlrlc 
_inlines.h 
Holding Latch type: (SQLO_LT_sqlrlc_anchor_common__lru_latch) - 
Address: (256cd9 
b50), Line: 239, File: sqlrlc_flush.C 
 
<<<< File = <thread_2> >>>> 
 
timestamp: 2009-09-16-14.51.15.944435 
Waiting on latch type: 
(SQLO_LT_sqlrlc_anchor_common__anchor_latch) - Address: ( 
256cd9b4c), Line: 1042, File: sqlrlc_request_usage.C 
 
timestamp: 2009-09-16-14.56.23.561822 
Waiting on latch type: 
(SQLO_LT_sqlrlc_anchor_common__anchor_latch) - Address: ( 
256cd9b4c), Line: 1042, File: sqlrlc_request_usage.C 
 
and the db2pd output will show: 
 
Applications: 
Address            AppHandl [nod-index] NumAgents  CoorPid 
Status                  C-AnchID C-StmtUID  L-AnchID L-StmtUID 
Appid 
 
0x00000002006FB860 236      [000-00236] 1         <thread_1> 
Lock-wait               155      1          228      1 
*LOCAL.db2inst1.090916045036 
 
0x00000002005DF800 192      [000-00192] 1         <thread_2> 
UOW-Executing           0        0          6        1 
*LOCAL.db2inst1.090916044452 
 
 
So, thread_1 is holding a latch thread_2 needs and thread_2 
needs the lock that thread_1 is holding.
Problem-Zusammenfassung:
Problem Summary: Multiple agents calling flush opt profile can 
deadlatch/deadlock. 
User affected: Any that are using the flush optimization profile 
command.
Local-Fix:
verfügbare FixPacks:
DB2 Version 9.1 Fix Pack 9  for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 10  for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 11  for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 12  for Linux, UNIX and Windows

Lösung
First fixed in DB2 v9.1 fixpak 9
Workaround
n/a
Bug-Verfolgung
Vorgänger  : APAR is sysrouted TO one or more of the following: IC65679 IC65801 
Nachfolger : 
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
25.11.2009
03.05.2010
03.05.2010
Problem behoben ab folgender Versionen (IBM BugInfos)
9.0.,
9.1.
Problem behoben lt. FixList in der Version
9.1.0.9 FixList