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

SNAPSHOTS, LIST APPLICATIONS AND DB2PD MAY SHOW INCORRECT STATUS FOR
CERTAIN WLM APPLICATIONS.

Produkt:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problembeschreibung:
Get Snapshot and db2pd data for applications may show the 
application status of certain WLM applications as "UOW Queued" 
when in fact they are not queued, as shown by WLM functions like 
WLM_GET_QUEUE_STATS. 
 
Here is an example: 
 
These are the queued transactions according to WLM (looks 
correct): 
 
LOW_01_SC  SYSDEFAULTSUBCL TESTER_WL  18714   0 QUEUED   TESTER 
TESTER  db-unload.impl  0 
 
LOW_01_SC  SYSDEFAULTSUBCL TESTER_WL  24020   0 QUEUED   TESTER 
TESTER  db-unload.impl  0 
 
Here is the output of LIST APPLICATIONS on the user TESTER 
showing 3 queued applications (WLM only shows 2). 
 
 
TESTER  db-unload.impl  41842  123.45.67.89.62238.110613145923 
00001 1  0  71326  UOW Queued 
 
TESTER  db-unload.impl  24315  *N0.dbedw5p.110613152112 
00001 1  0  21114  UOW Queued 
 
TESTER  db-unload.impl  23933  *N0.dbedw5p.110613152114 
00001 1  0  57934  UOW Queued
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* Get Snapshot and db2pd data for applications may show the    * 
* application status of certain WLM applications as "UOW       * 
* Queued" when in fact they are not queued, as shown by WLM    * 
* functions like WLM_GET_QUEUE_STATS.                          * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 9.7 Fix Pack 5.                       * 
****************************************************************
Local-Fix:
verfügbare FixPacks:
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 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows

Lösung
First fixed in DB2 Version 9.7 Fix Pack 5.
Workaround
keiner bekannt / siehe Local-Fix
Kommentar
N/A
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
28.07.2011
09.12.2011
09.12.2011
Problem behoben ab folgender Versionen (IBM BugInfos)
9.7.FP5
Problem behoben lt. FixList in der Version
9.7.0.5 FixList