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

DB2 Connect Server might crash if DCS directory is catalogued to use
map-file option

product:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problem description:
If the DCS directory is cataloged to use customized mapping file 
with map-file option and the directory cache is invalidated 
while DB2 Connect Server is still running, DB2 Connect gateway 
might crash with the following stack: 
 
2013-05-14-15.52.07.061757+060 I2358547A1860      LEVEL: Severe 
PID     : 9175070              TID  : 6684        PROC : db2sysc 
INSTANCE:             NODE : 000 
APPHDL  : 0-47711 
EDUID   : 6684                 EDUNAME: db2agent () 
FUNCTION: DB2 UDB, SQO Memory Management, 
sqloDiagnoseFreeBlockFailure, probe:10 
MESSAGE : Possible memory corruption detected. 
DATA #1 : ZRC, PD_TYPE_ZRC, 4 bytes 
0x820F0002 
DATA #2 : Corrupt block address, PD_TYPE_CORRUPT_BLK_PTR, 8 
bytes 
0x09001000a11c4368 
DATA #3 : Block header, PD_TYPE_BLK_HEADER, 24 bytes 
0x09001000A11C4350 : 0900 1000 A147 E308 0900 1000 A147 E320 
.....G.......G. 
0x09001000A11C4360 : 0900 1000 A147 E338 
.....G.8 
DATA #4 : Data header, PD_TYPE_BLK_DATA_HEAD, 48 bytes 
0x09001000A11C4368 : 0000 0000 0000 0000 0000 0000 0000 0000 
................ 
0x09001000A11C4378 : 0000 0000 0000 0000 0000 0000 0000 0000 
................ 
0x09001000A11C4388 : 0000 0000 0000 0000 0000 0000 0000 0000 
................ 
CALLSTCK: (Static functions may not be resolved correctly, as 
they are resolved to the nearest symbol) 
  [0] 0x0900000004278B6C pdLog + 0xC0 
  [1] 0x0900000006141404 
@78@sqloDiagnoseFreeBlockFailure__FP8SMemFBlkCb + 0x14C 
  [2] 0x090000000379B910 sqlofmblkEx + 0x424 
  [3] 0x090000000680624C sqljrTerm__FP14db2UCinterfaceb + 0x16C 
  [4] 0x09000000066C96D0 
sqljrDissociateTransport__FP14db2UCconHandleP13sqljrDrdaArCbi + 
0x124 
  [5] 0x09000000067C68F8 
sqljrDrdaArDisconnect__FP14db2UCinterface + 0x424 
  [6] 0x09000000067A9EB0 
sqleuUCagentDrdaArTermConnect__FP14db2UCinterface + 0x7C 
  [7] 0x09000000033E4D40 
sqleUCagentConnCleanup__FP8sqeAgentP14db2UCconHandlebT3 + 0xE8 
  [8] 0x09000000031E8FA4 
sqleUCagentConnCleanup__FP8sqeAgentP14db2UCconHandlebT3@glue9FB 
+ 0x7C 
  [9] 0x0900000005DD33FC 
@63@sqljsVerifyAgent__FP8sqeAgentP14db2UCconHandlePb + 0x11B0
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* DB2 Connect                                                  * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 version 10.5 fixpack 3                        * 
****************************************************************
Local Fix:
available fix packs:
DB2 Version 10.5 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.5 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Cancun Release 10.5.0.4 (also known as Fix Pack 4) for Linux, UNIX, and Windows
DB2 Version 10.5 Fix Pack 9 for Linux, UNIX, and Windows

Solution
Problem was first fixed in DB2 version 10.5 fixpack 3
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
27.09.2013
27.02.2014
27.02.2014
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.5.0.3 FixList
10.5.0.3 FixList