home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Latest versionsfixlist
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
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IC66897 Status: Closed

TRAP IN DB2LOGMGR DUE TO UNEXPECTED CONDITION

product:
DB2 FOR LUW / DB2FORLUW / 980 - DB2
Problem description:
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 Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All Users                                                    * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* TRAP IN DB2LOGMGR DUE TO UNEXPECTED CONDITION                * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to Version 9.8 Fixpak 3 or later                     * 
****************************************************************
Local Fix:
available fix packs:
DB2 Version 9.8 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.8 Fix Pack 4 for AIX and Linux
DB2 Version 9.8 Fix Pack 5 for AIX and Linux

Solution
Problem was first fixed in Version 9.8 Fixpak 3
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
04.03.2010
21.12.2010
21.12.2010
Problem solved at the following versions (IBM BugInfos)
9.8.
Problem solved according to the fixlist(s) of the following version(s)
9.8.0.3 FixList