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

DB2 may crash while using MON_GET_TABLE or MON_GET_INDEX functio ns when a
system temp table is being created at the same time.

Produkt:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problembeschreibung:
Due to a rare timing hole, DB2 may crash in the function 
ossStrCompWithPads. This crash only occurs when using the 
MON_GET_TABLE or MON_GET_INDEX monitor SQL interfaces with a 
non-empty/non-null table name input parameter at the same time a 
system temporary table is being created. 
 
The stack for this crash should be similar to the following: 
 
Stack: 
 ====================== 
 
 0x0900000000059A90 rightmost + 0x8 
 0x090000000005A40C free_y + 0x23C 
 0x09000000000584FC free_common + 0x88 
 0x09000000028D1780 _ossMemFree + 0x60 
 0x09000000028DE8DC ossStrCompWithPads + 0x13C 
 0x0900000006DE7420 execute__26sqlrwFilteredTableIteratorFv + 
0x1C4 
 0x0900000006E32CE4 
sqlrwGetTableMetrics__FP8sqlrr_cbP24sqlrwGetTableMetricsArgsPPvP 
l 
+ 0x250 
 0x0900000006052044 
sqlrwGetWLMTableFunctionResult__FP8sqlrr_cbP20sqlrw_rpc_tf_reque 
stPPvPl 
+ 0x250 
 0x0900000006072B4C 
sqlrwReceiveGetWLMTableFunctionResult__FP8sqlrr_cbP18sqlrw_rpc_w 
lm_sendP15SQLR_RPCMESSAGE 
+ 0x5C 
 0x0900000006070DCC 
sqlrwWlmRPCRouter__FP8sqlrr_cbP16sqlkdRqstRplyFmtiPP15SQLR_RPCME 
SSAGE 
+ 0x1D4 
 0x0900000004F064A8 sqlrr_rpc_router__FP8sqlrr_cb + 0xA68 
 0x09000000041D5034 
sqlrr_subagent_router__FP8sqeAgentP12SQLE_DB2RA_T + 0x5DC 
 0x0900000004EFBE50 sqleSubRequestRouter__FP8sqeAgentPUiT2 + 
0x5F0 
 0x0900000003FAD510 sqleProcessSubRequest__FP8sqeAgent + 0x67C 
 0x090000000419ED24 RunEDU__8sqeAgentFv + 0x304 
 0x09000000076243C8 EDUDriver__9sqzEDUObjFv + 0xD8 
 0x090000000761BF18 sqloEDUEntry + 0x260
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* Customer using MON_GET_TABLE or MON_GET_INDEX monitor SQL    * 
* interfaces                                                   * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* Due to a rare timing hole, DB2 may crash in the function     * 
*                                                              * 
* ossStrCompWithPads. This crash only occurs when using the    * 
*                                                              * 
* MON_GET_TABLE or MON_GET_INDEX monitor SQL interfaces with a * 
*                                                              * 
* non-empty/non-null table name input parameter at the same    * 
* time a                                                       * 
* system temporary table is being created.                     * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2LUW version 9.7.fp4                            * 
****************************************************************
Local-Fix:
NA
verfügbare FixPacks:
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows

Lösung
Workaround
keiner bekannt / siehe Local-Fix
Bug-Verfolgung
Vorgänger  : APAR is sysrouted TO one or more of the following: IC89909 
Nachfolger : 
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
18.01.2011
02.05.2011
02.05.2011
Problem behoben ab folgender Versionen (IBM BugInfos)
9.7.FP4
Problem behoben lt. FixList in der Version
9.7.0.4 FixList