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

STALE CF MANAGEMENT PORT RE-USED FOR COMMUNICATIONS.

Produkt:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problembeschreibung:
Improper handling of a communications error during CF structure 
resize can lead to re-using a stale connection handle.
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* DB2 pureScale                                                * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* Adverse network conditions can lead to the improper re-use   * 
* of a CF management port connection and a DB2 panic.  One     * 
* example stack of this situation is:                          * 
*                                                              * 
* CALLSTCK: (Static functions may not be resolved correctly,   * 
* as they are resolved to the nearest symbol)                  * 
*   [0] 0x09000000099BBD30 pdLog + 0x2D0                       * 
*   [1] 0x090000000A836C64                                     * 
* sqleCaConvertCaStatusToDB2Rc__F8CAStatus + 0x1C4             * 
*   [2] 0x090000000A836DA4                                     * 
* sqleMapManagementCAStatusToZRC__FC8CAStatusCb + 0xA4         * 
*   [3] 0x090000000A85BB2C                                     * 
* SAL_ManagementResize__26SAL_MANAGEMENT_PORT_HANDLEFCPCcCUlCb * 
* CUiCUsN25CPUiT8CP34SQLE_CA_MGMNT_EXTENDED_RESIZE_INFO +      * 
* 0x1A2C                                                       * 
*   [4] 0x090000000D200A28                                     * 
* SAL_CADoStructureResizeCommand__20SAL_CA_STRUCT_HANDLEFR22SA * 
* L_MANAGEMENT_HANDLESCUlCP29SQLF_CA_STRUCT_RESIZE_ELEMENTCUiC * 
* PUiT5 + 0x288                                                * 
*   [5] 0x090000001327ACF0                                     * 
* sqlfResizeStructureInCA__20SAL_CA_STRUCT_HANDLEFP29SQLF_CA_S * 
* TRUCT_RESIZE_ELEMENTPb + 0x770                               * 
*   [6] 0x090000001327BCE0                                     * 
* sqlfCAStructureResizeBackgroundTask__FP16sqeLocalDatabaseP18 * 
* SQLR_RPC_REPLY_HDR + 0x340                                   * 
*   [7] 0x090000001326DC60 sqleRPCSync + 0xCE0                 * 
*   [8] 0x0900000013261834                                     * 
* sqlePeriodicMain__FP16sqeLocalDatabaseP8sqeAgent + 0x374     * 
*   [9] 0x090000001324A808                                     * 
* sqleIndCoordProcessRequest__FP8sqeAgent + 0x9C8              * 
*   [10] 0x0900000009C85F4C RunEDU__8sqeAgentFv + 0x3AC        * 
*   [11] 0x0900000009C42BFC EDUDriver__9sqzEDUObjFv + 0x23C    * 
*   [12] 0x0900000009C42F3C sqlzRunEDU__FPcUi + 0x3C           * 
*   [13] 0x0900000009B237F4 sqloEDUEntry + 0x7B4               * 
*   [14] 0x0900000000771E10 _pthread_body + 0xF0               * 
*   [15] 0xFFFFFFFFFFFFFFFC ?unknown + 0xFFFFFFFF              * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 version 10.5.0.4                              * 
****************************************************************
Local-Fix:
Update to the fixpack that this is fixed in.
verfügbare FixPacks:
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

Lösung
The problem is first fixed in DB2 version 10.5.0.4
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
05.06.2014
22.09.2014
22.09.2014
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version
10.5.0.4 FixList