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 IC84148 Status: Closed

DB2WDOG CAN ABORT (SEGV/CRASH) WHEN CLEANING UP A DB2FMP ENTRY

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
The db2wdog process can abnormally terminate with a signal #11 
(segmentation violation) and cause the DB2 instance to 
crash when cleaning up non-SQL stored procedures.  The 
probability of this crash occurring is low. 
 
One possible side effect of this APAR is that the DB2 
instance is NOT brought down after db2wdog dies leaving the DB2 
instance in an unusable state. 
 
The trap file will contain the 
following stack: 
 
SQLO_MEM_POOL::MemTreePut.fdpr.clone.128.chunk.4() at 
0x900000008603b60 
sqlofmblkEx() at 0x900000008603890 
sqlexAuditData.@136@sqlerRemoveFmpFromTable() at 
0x900000004fba560 
.sqlerRemoveFmpFromTable() at 0x900000004fba210 
sqlerRemoveFmpFromTable() at 0x900000004fbb37c 
sqlerReturnFmpToPool.fdpr.chunk.5() at 0x900000003d7f1a4 
sqleChildCrashHandler() at 0x100009640 
sqleWatchDog() at 0x100003910 
DB2main() at 0x1000015b0 
sqloEDUMainEntry() at 0x900000008680ac8 
sqloEDUEntry.fdpr.chunk.6() at 0x900000008680a4c
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All users of DB2                                             * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 10.1 Fix Pack 1 or higher.            * 
****************************************************************
Local Fix:
available fix packs:
DB2 Version 10.1 Fix Pack 1 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows

Solution
Problem first fixed in DB2 Version 10.1 Fix Pack 1
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
12.06.2012
08.04.2013
08.04.2013
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.1.0.1 FixList
10.5.0.1 FixList