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

DB2DIAG -E RETURNS INCORRECT DB2DIAG.LOG ENTRY

Produkt:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problembeschreibung:
The following command returns incorrect log entry: 
 
$ db2diag -e DIA8309C 
 
2011-05-30-15.29.20.856163+000 E178071A468      LEVEL: Event 
PID     : 1089590              TID  : 19225     PROC : db2sysc 0 
INSTANCE: xxxxxx               NODE : 000       DB   : xxxxxx 
APPHDL  : 0-44441              APPID: 
10.215.247.174.40682.1105301529 
AUTHID  : xxxxxx 
EDUID   : 19225                EDUNAME: db2agent (idle) 0 
FUNCTION: DB2 UDB, base sys utilities, 
sqeLocalDatabase::TermDbConnect, probe:2000 
STOP    : DATABASE: xxxxxx   : DEACTIVATED: NO 
 
This entry does not match the error code DIA8309C. Moreover, 
DIA8309C is not present in db2diag.log. Therefore, the above 
command is not expected to return any output. 
 
The problem occurs when the following is true: 
 
- When it is the above probe 
- When the above entry is the last log entry in db2diag.log file 
 
Also, it does not matter what -e value is. For example, 
db2diag -e SAMPLESTRING also returns the same entry.
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 9.7 FP6 or subsequent fix pack.               * 
****************************************************************
Local-Fix:
n/a
verfügbare FixPacks:
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
Problem First Fixed in DB2 Version 9.7 Fix Pack 6
Workaround
keiner bekannt / siehe Local-Fix
Bug-Verfolgung
Vorgänger  : APAR is sysrouted TO one or more of the following: IC82053 IC84530 
Nachfolger : 
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
09.06.2011
10.12.2012
10.12.2012
Problem behoben ab folgender Versionen (IBM BugInfos)
9.7.FP6
Problem behoben lt. FixList in der Version
9.7.0.6 FixList