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

INCORRECT CLEANUP OF CLIENT SUPPORT STRUCTURE IN AGENT AFTER AN OUT OF
MEMORY FAILURE LEADS TO A DOUBLE FREE OF MEMORY

Produkt:
DB2 FOR LUW / DB2FORLUW / 950 - DB2
Problembeschreibung:
There is a potential of receiving a segmentation fault and a 
'Double free' error if the instance is running low on memory. 
 
db2diag.log will show messages like following: 
 
2009-12-13-13.39.31.438913+060 I9683530A467       LEVEL: Severe 
PID     : 3072108              TID  : 802032      PROC : db2sysc 
0 
INSTANCE: db2inst1               NODE : 000 
EDUID   : 802032               EDUNAME: db2agent 0 
FUNCTION: DB2 UDB, base sys utilities, sqeAgent::AgentUCSetup, 
probe:30 
RETCODE : ZRC=0x8B0F0000=-1961951232=SQLO_NOMEM 
          "No Memory Available (reason code is id of requested 
heap)" 
          DIA8300C A memory heap error has occurred. 
 
2009-12-13-13.39.32.019292+060 I9801817A345       LEVEL: Severe 
PID     : 3072108              TID  : 802032      PROC : db2sysc 
0 
INSTANCE: db2inst1               NODE : 000 
EDUID   : 802032               EDUNAME: db2agent 0 
FUNCTION: DB2 UDB, SQO Memory Management, 
sqloDiagnoseFreeBlockFailure, probe:30 
DATA #1 : String, 12 bytes 
Double free.
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* There is a potential of receiving a segmentation fault and   * 
* a'Double free' error if the instance is running low          * 
* onmemory.db2diag.log will show messages like                 * 
* following:2009-12-13-13.39.31.438913+060 I9683530A467        * 
* LEVEL:SeverePID    : 3072108              TID  : 802032      * 
* PROC :db2sysc0INSTANCE: db2inst1              NODE :         * 
* 000EDUID  : 802032              EDUNAME: db2agent 0FUNCTION: * 
* DB2 UDB, base sys                                            * 
* utilities,sqeAgent::AgentUCSetup,probe:30RETCODE :           * 
* ZRC=0x8B0F0000=-1961951232=SQLO_NOMEM"No Memory Available    * 
* (reason code is id ofrequestedheap)"DIA8300C A memory heap   * 
* error has occurred.2009-12-13-13.39.32.019292+060            * 
* I9801817A345      LEVEL:SeverePID    : 3072108               * 
* TID  : 802032      PROC :db2sysc0INSTANCE: db2inst1          * 
*     NODE : 000EDUID  : 802032              EDUNAME: db2agent * 
* 0FUNCTION: DB2 UDB, SQO Memory                               * 
* Management,sqloDiagnoseFreeBlockFailure, probe:30DATA #1 :   * 
* String, 12 bytesDouble free.                                 * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 version 9.5 FP6                               * 
****************************************************************
Local-Fix:
verfügbare FixPacks:
DB2 Version 9.5 Fix Pack 6a for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 10 for Linux, UNIX, and Windows

Lösung
First fixed in DB2 version 9.5 FP6
Workaround
keiner bekannt / siehe Local-Fix
Bug-Verfolgung
Vorgänger  : APAR is sysrouted TO one or more of the following: IC65726 
Nachfolger : 
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
04.01.2010
10.06.2010
10.06.2010
Problem behoben ab folgender Versionen (IBM BugInfos)
9.5.FP6
Problem behoben lt. FixList in der Version