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

DB2 CRASHES ON RUNSTATS WITH SQLDINDEXSTATS 'NO COLSTAT STRUCTURE
FOUND FOR INDEX WITH ITOKEN' in DB2DIAG.LOG

Produkt:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problembeschreibung:
Running RUNSTATS on a Global Temporary Table after an index is 
created fails with the following errors: 
 
 db2diag.log shows: 
2014-02-10-14.05.45.097627+060 I6664665A552       LEVEL: Severe 
PID     : 9044336              TID  : 45055       PROC : db2sysc 
0 
INSTANCE: dbdevdwh             NODE : 000         DB   : DWH 
APPHDL  : 0-11231              APPID: 
10.1.50.140.60679.140210125441 
AUTHID  : MNEISEME 
EDUID   : 45055                EDUNAME: db2agent (DWH) 0 
FUNCTION: DB2 UDB, data management, sqldIndexStats, probe:20 
MESSAGE : No colstat structure found for index with itoken 
DATA #1 : Hexdump, 2 bytes 
0x0A00000020FE58D0 : 0000 
.. 
 
2014-02-10-14.05.45.098021+060 I6665218A520       LEVEL: Severe 
PID     : 9044336              TID  : 45055       PROC : db2sysc 
0 
INSTANCE: dbdevdwh             NODE : 000         DB   : DWH 
APPHDL  : 0-11231              APPID: 
10.1.50.140.60679.140210125441 
AUTHID  : MNEISEME 
EDUID   : 45055                EDUNAME: db2agent (DWH) 0 
FUNCTION: DB2 UDB, data management, sqldIndexStats, probe:20 
MESSAGE : Index type 
DATA #1 : Hexdump, 8 bytes 
0x0A0002002EFAFA00 : 0000 0000 0000 4340 
......C@ 
 
2014-02-10-14.05.45.098167+060 I6665739A532       LEVEL: Severe 
PID     : 9044336              TID  : 45055       PROC : db2sysc 
0 
INSTANCE: dbdevdwh             NODE : 000         DB   : DWH 
APPHDL  : 0-11231              APPID: 
10.1.50.140.60679.140210125441 
AUTHID  : MNEISEME 
EDUID   : 45055                EDUNAME: db2agent (DWH) 0 
FUNCTION: DB2 UDB, data management, sqldIndexStats, probe:40 
MESSAGE : Column number for index is 
DATA #1 : Hexdump, 4 bytes 
0x0A00000020FE550C : 0000 FFFF 
.... 
 
2014-02-10-14.05.45.098278+060 I6666272A523       LEVEL: Severe 
PID     : 9044336              TID  : 45055       PROC : db2sysc 
0 
INSTANCE: dbdevdwh             NODE : 000         DB   : DWH 
APPHDL  : 0-11231              APPID: 
10.1.50.140.60679.140210125441 
AUTHID  : MNEISEME 
EDUID   : 45055                EDUNAME: db2agent (DWH) 0 
FUNCTION: DB2 UDB, trace services, sqlt_logerr_string (secondary 
logging fu, probe:0 
MESSAGE : SQLD_CCB: 
DATA #1 : String, 53 bytes 
pool(TID)=3644, obj(FID)=2, indexid(IID)=0, class=128 
 
2014-02-10-14.05.45.098405+060 I6666796A168       LEVEL: Severe 
PID:9044336 TID:45055 NODE:000 Title: SQLD_CCB 
Dump File: /db2/dump/dbdevdwh/9044336.45055.000.dump.bin 
 
2014-02-10-14.05.45.116682+060 I6666965A178       LEVEL: Severe 
PID:9044336 TID:45055 NODE:000 Title: SQLD_CCB_DPARTINFO 
Dump File: /db2/dump/dbdevdwh/9044336.45055.000.dump.bin 
 
Crash stack shows as: 
<StackTrace> 
-------Frame------ ------Function + Offset------ 
0x09000000007EDF54 pthread_kill + 0xD4 
0x090000002543A030 sqloDumpEDU + 0x34 
0x09000000259FF800 sqldDumpContext__FP9sqeBsuEduiN42PCcPvT2 + 
0xCC 
0x090000002543C760 
sqldDumpContext__FP9sqeBsuEduiN42PCcPvT2@glue5BA + 0x98 
0x0900000026193AC0 sqlrr_dump_ffdc__FP8sqlrr_cbiT2 + 0x370 
0x0900000025FAE290 sqlzeDumpFFDC__FP8sqeAgentUiP5sqlcai + 0x30 
0x0900000025FAE370 sqlzeDumpFFDC__FP8sqeAgentUiP5sqlcai@glue542 
+ 0x80 
0x0900000025FAE87C 
sqlzeMapZrc__FP8sqeAgentUiUlT2P5sqlcaiPC12sqlzeContextb + 0x1A8 
0x0900000026C4D35C 
sqlrLocalRunstats__FP8sqlrr_cbP11sqlrrstringN22UcUsT6PP8sqlrg_pd 
iN39P16sqlrl_stats_colsPPsUiPPUsT15_d 
T15_T6PP20sqlr_runstats_resultPsUlT23_N26CUiT15_lP17sqlrlc_stats 
_infoPCUc + 0xC10 
0x0900000027B2C588 
sqlrrsta__FP8sqlrr_cbP11sqlrrstringN22UcT5P17sqlrl_stats_parmsPC 
UcPs + 0x288 
0x0900000027B52D00 sqlrr_runstats_DA__FP5sqldaP5sqlca + 0xA74 
0x09000000265BC4BC 
sqlerKnownProcedure__FiPcPiP5sqldaT4P13sqlerFmpTableP8sqeAgentP5 
sqlca + 0x4E0 
0x0900000025D382A8 sqlerCallDL__FP14db2UCinterfaceP9UCstpInfo + 
0x580 
0x0900000025D38880 
.sqljs_ddm_excsqlstt.fdpr.clone.253__FP14db2UCinterfaceP13sqljDD 
MObject + 0xE4 
0x0900000025EF645C 
sqljsParseRdbAccessed__FP13sqljsDrdaAsCbP13sqljDDMObjectP14db2UC 
interface + 0x110 
0x0900000025EF5D50 
.sqljsParse.fdpr.clone.234__FP13sqljsDrdaAsCbP14db2UCinterfaceP8 
sqeAgentb + 0x324 
0x0900000025EF9884 @63@sqljsSqlam__FP14db2UCinterfaceP8sqeAgentb 
+ 0x2C0 
0x0900000025F3A6E0 
sqljsDrdaAsSPDriver__FP14db2UCconHandleP17SQLCC_COMHANDLE_TPPUcl 
+ 0x1F8 
0x0900000025F3EA84 sqlerInvokeFencedRoutine__FP13sqlerFmpParms + 
0x6F8 
0x0900000025F35D80 sqlriInvokeInvoker__FP10sqlri_ufobb + 0x508 
0x0900000025F35068 sqlricall__FP8sqlrr_cb + 0x13C 
0x0900000025E8BEA4 sqlriSectInvoke__FP8sqlrr_cbP12sqlri_opparm + 
0x24 
0x0900000025EDE6E4 sqlrr_process_execute_request__FP8sqlrr_cbib 
+ 0xC40 
0x0900000025EF4628 
.sqlrr_execute.fdpr.clone.1958__FP14db2UCinterfaceP9UCstpInfo + 
0xB4 
0x0900000025EF4FD0 
.sqljs_ddm_excsqlstt.fdpr.clone.253__FP14db2UCinterfaceP13sqljDD 
MObject + 0x658 
0x0900000025EF645C 
sqljsParseRdbAccessed__FP13sqljsDrdaAsCbP13sqljDDMObjectP14db2UC 
interface + 0x110 
0x0900000025EF6104 
.sqljsParse.fdpr.clone.234__FP13sqljsDrdaAsCbP14db2UCinterfaceP8 
sqeAgentb + 0x6D8 
0x0900000025EF9884 @63@sqljsSqlam__FP14db2UCinterfaceP8sqeAgentb 
+ 0x2C0 
0x090000002604F048 
@63@sqljsDriveRequests__FP8sqeAgentP14db2UCconHandle + 0xB4 
0x090000002604ED38 
@63@sqljsDrdaAsInnerDriver__FP18SQLCC_INITSTRUCT_Tb + 0x2D4 
0x090000002604E7BC sqljsDrdaAsDriver__FP18SQLCC_INITSTRUCT_T + 
0xFC 
0x0900000025CCD93C RunEDU__8sqeAgentFv + 0x280 
0x0900000025CC8DA8 EDUDriver__9sqzEDUObjFv + 0xDC 
0x0900000025CF59EC sqloEDUEntry + 0x254 
</StackTrace> 
 
 
This is caused by a silent failure on the CREATE INDEX command 
instead of generating a SQL0901N error.
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All users                                                    * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 version 10.5.0.4.                             * 
****************************************************************
Local-Fix:
Use  'DECLARE GLOBAL TEMPORARY TABLE' instead of 'CREATE GLOBAL 
TEMPORARY TABLE', 
or do not create the index on the table.
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:
03.04.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