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

AGENT TRAPS WITH -901 WHILE ATTEMPTING TO CREATE A TEMPORARY TABLE FOR
SPILLING.

Produkt:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problembeschreibung:
Problem Description 
Under certain timing conditions in a DPF environment a query can 
get 
the below given error in the db2diag.log due to multiple SMP/DPF 
subagents trying to update the slestatus field and an update 
gets 
lost without latch protection. 
 
2014-08-26-16.49.46.664500-240 I341038535E644        LEVEL: 
Severe 
PID     : 5334                 TID : 46915722930496  PROC : 
db2sysc 21 
INSTANCE: db2inst1             NODE : 021            DB   : 
Sample 
APPHDL  : 1-32693              APPID: LOCAL.DB2.140819184249 
AUTHID  : Test              HOSTNAME: 
EDUID   : 82033                EDUNAME: db2agntp (Sample) 21 
FUNCTION: DB2 UDB, sort/list services, sqlsmergerec, probe:2050 
MESSAGE : Creating Temporary Table for sort spill, but one 
already exists. 
          Aborting sort operation. Contact IBM Support. 
slestatus = 0x50cc0, 
          poolID = 6, objectID = 2 
 
2014-08-26-16.49.46.687826-240 I341039180E18992      LEVEL: 
Severe 
PID     : 5334                 TID : 46915722930496  PROC : 
db2sysc 21 
INSTANCE: db2inst1             NODE : 021            DB   : 
Sample 
APPHDL  : 1-32693              APPID: LOCAL.DB2.140819184249 
AUTHID  : Test              HOSTNAME: 
EDUID   : 82033                EDUNAME: db2agntp (Sample) 21 
FUNCTION: DB2 UDB, trace services, sqlt_logerr_data (secondary 
logging function), probe:50 
MESSAGE : 
DATA #1 : Hexdump, 3648 bytes 
0x00002AABFFCB4F40 : 0000 0000 0000 0000 0000 0000 0000 0000 
................ 
0x00002AABFFCB4F50 : C00C 0500 0000 0000 0000 DD02 0000 0000 
................ 
0x00002AABFFCB4F60 : 0000 0000 0000 0000 0000 0000 0000 0000 
................ 
0x00002AABFFCB4F70 : 0000 0000 0000 0000 0000 0000 0000 0000 
................ 
0x00002AABFFCB4F80 : 0000 0000 0000 0000 0000 0000 0000 0000 
................ 
0x00002AABFFCB4F90 : 0000 0000 0000 0000 0000 0000 0000 0000 
................ 
0x00002AABFFCB4FA0 : 0000 0000 0000 0000 0000 0000 0000 0000 
................ 
 
Stack can be as given below:- 
 
Stack #1             Signal #12        Timestamp 
2014-09-04-03.29.35.434271 
0        ossDumpStackTraceInternal 
1        ossDumpStackTraceV98 
2        OSSTrapFile::dumpEx 
3        sqlo_trce 
4        sqloDumpDiagInfoHandler 
5        __pthread_mutex_cond_lock 
6        pthread_kill 
7        ossPthreadKill 
8        sqloDumpEDU 
9        sqldDumpContext 
10       sqlrr_dump_ffdc 
11       sqlzeDumpFFDC 
12       sqlzeMapZrc 
13       sqlrrMapZrc 
14       sqlrisr2 
15       sqldDataFetch 
16       sqliScanLeaf2NoLocking 
17       sqlifnxt 
18       sqlirdk 
19       sqldIndexFetch 
20       sqldRowFetch 
21       sqlriFetch
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 10.5 Fix Pack 5                               * 
****************************************************************
Local-Fix:
Lösung
First Fixed in DB2 10.5 Fix Pack 5
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
16.09.2014
09.05.2017
09.05.2017
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version
9.7.0.11 FixList