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

TRAP IN DB2LOGMGR DUE TO UNEXPECTED CONDITION

Produkt:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problembeschreibung:
In HADR environment (Peer state), after several logmgr retrieval 
errors as below, it may finally result in a trap 
 
2009-10-06-11.58.16.120390-420 I1908225A357       LEVEL: Error 
PID     : 651462               TID  : 4042        PROC : db2sysc 
0 
INSTANCE: db2wp1               NODE : 000 
EDUID   : 4042                 EDUNAME: db2logmgr (WP1) 0 
FUNCTION: DB2 UDB, data protection services, 
sqlpgRetrieveLogFile, probe:3400 
MESSAGE : Unable to locate new retrieve request!
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All uers in HADR environment                                 * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* In HADR environment (Peer state), after several              * 
* logmgrretrieval errors as below, it may finally result in a  * 
* trap2009-10-06-11.58.16.120390-420                           * 
* I1908225A357LEVEL:ErrorPID     : 651462               TID  : * 
* 4042        PROC:db2sysc 0INSTANCE: db2wp1                   * 
* NODE : 000EDUID   : 4042                 EDUNAME: db2logmgr  * 
* (WP1) 0FUNCTION: DB2 UDB, data protection                    * 
* services,sqlpgRetrieveLogFile, probe:3400MESSAGE : Unable to * 
* locate new retrieve request!                                 * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Please upgrade to Version 9.7 Fixpak 2 or later              * 
****************************************************************
Local-Fix:
verfügbare FixPacks:
DB2 Version 9.7 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
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 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows

Lösung
Problem is first fixed in Version 9.7 Fixak 2
Workaround
keiner bekannt / siehe Local-Fix
Bug-Verfolgung
Vorgänger  : APAR is sysrouted TO one or more of the following: IC66897 
Nachfolger : 
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
19.11.2009
22.06.2010
22.06.2010
Problem behoben ab folgender Versionen (IBM BugInfos)
9.7.
Problem behoben lt. FixList in der Version
9.7.0.2 FixList