DB2 FOR LUW / DB2FORLUW / A10 - DB2

This problem can only occur when using MDC or ITC tables, and 
the DMB config parameter INTRA_PARALLEL is set to yes. 
 
This is an extremely small timing hole that occurs very 
infrequently. It occurs when doing a symmetric multiprocessing 
scan at the same time as growing a table from empty to 
non-empty. 
 
If you hit the problem, the following error will appear in the 
db2diag.log: 
 
2012-07-22-13.45.22.610712-240 I623300201A623       LEVEL: 
Severe 
PID     : 22216848             TID : 12433          KTID : 
67502215 
PROC    : db2sysc 11 
INSTANCE: dbinst1              NODE : 011           DB   : 
SAMPLEDB 
APPHDL  : 0-616                APPID: 
9.26.51.58.50500.120723045504 
AUTHID  : DBINST1              HOSTNAME: db2host 
EDUID   : 12433                EDUNAME: db2agnts (SAMPLEDB) 11 
FUNCTION: DB2 UDB, data management, sqldFetchNext, probe:0 
MESSAGE : EOF error: should've been checked by sqldGetNextRange 
DATA #1 : Hexdump, 4 bytes 
0x070000001B7FCCB0 : 8704 0055 
...U 
 
 
The stack trace looks like this: 
 
<StackTrace> 
-------Frame------ ------Function + Offset------ 
0x0900000000604910 pthread_kill + 0xB0 
0x090000002C5270BC ossPthreadKill__FCUiT1 + 0x5C 
0x090000002C5271B0 sqloDumpEDU + 0x90 
0x090000002E146904 sqldFetchNext__FP13SQLD_DFM_WORK + 0x724 
0x090000002E149C24 sqldfrd__FP13SQLD_DFM_WORK + 0xF64 
0x090000002F70579C 
sqldRowFetch__FP8sqeAgentP8SQLD_CCBUlT3PP10SQLD_VALUEP8SQLZ_RIDT 
3P12SQLD_ID_LISTP9SQLP_LSN8 + 0x1C1C 
0x09000000310D0C00 sqlriFetchPerm__FP8sqlrr_cbP9sqlri_taol + 
0x100 
0x09000000310D0F70 sqlritaSimplePerm__FP8sqlrr_cb + 0x2F0 
0x090000002CE08EA4 sqlriExecThread__FP8sqlrr_cbP12sqlri_opparm + 
0x5A4 
0x090000002CE0AFBC sqlriSectInvoke__FP8sqlrr_cbP12sqlri_opparm + 
0xD9C 
0x09000000325F80E8 sqlrr_smp_router__FP8sqlrr_cb + 0x388

**************************************************************** 
* USERS AFFECTED:                                              * 
* All users of symmetric multiprocessing                       * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 version 10.1.0.1.                             * 
****************************************************************

A workaround to problem is to disable INTRA_PARALLEL (set it to 
NO), ensuring the problem will not occur.

DB2 Version 10.1 Fix Pack 1 for Linux, UNIX, and Windows
 DB2 Version 10.1 Fix Pack 2 for Linux, UNIX, and Windows
 DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows
 DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
 DB2 Version 10.1 Fix Pack 3a for Linux, UNIX, and Windows
 DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows
 

The problem is first fixed in DB2 version 10.1.0.1.

keiner bekannt / siehe Local-Fix

Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:

10.08.2012
31.10.2012
31.10.2012