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

FCM CAN DOUBLE FREE A BUFFER WHICH LATER LEADS TO A TRAP

Produkt:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problembeschreibung:
If the FCM receive conduit rejects an authentication event where 
the data received was exactly the same size as a buffer header, 
and the buffer header is invalid, then it will double-free the 
FCM buffer. 
 
2015-07-21-20.40.38.298755-420 I61769726E413         LEVEL: 
Severe 
PID     : 29225                TID : 139633920829184     PROC 
:db2sysc 0 
INSTANCE: xxxx             NODE : 000            HOSTNAME: 
xxxxxxxxxx 
EDUID   : 19 
EDUNAME: db2fcmr 0 
FUNCTION: DB2 UDB, fast comm manager, 
sqkfRecvConduit::HandleAuthentEvent, probe:25 
RETCODE : ZRC=0x8159006B=-2124873621=SQLKF_CONN_CLOSED "FCM 
connection closed" 
 
The preceding db2diag.log probe indicates that this has 
occurred.  The result is a wide range of FODC_Panic's and 
FODC_Traps which can occur 
in any BDS/BQS messaging codepath.  Here is an example stack for 
a trap: 
 
         memcpy 
         sqlkd_rcv_data 
         sqlkdReceiveData 
         sqlrkrpc_nl 
         sqlrwSendGetWLMTableFunctionResult 
         sqlrwGetWLMTableFunctionMergedResult 
         sqlerTrustedRtnCallbackRouter 
         monGetMemoryPool 
         sqloInvokeFnArgs 
         sqlriInvokerTrusted 
         ...
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* DB2 UDB Version 10.5                                         * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to Version 10.5 FixPack 7.                           * 
****************************************************************
Local-Fix:
Lösung
Problem was first fixed in DB2 UDB Version 10.5 FixPack 7.
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
09.09.2015
21.06.2016
21.06.2016
Problem behoben ab folgender Versionen (IBM BugInfos)
9.7.
Problem behoben lt. FixList in der Version
10.5.0.7 FixList