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

LOAD INTO MDC TABLE FAILS WITH SQL0902C OR SQL0990C

Produkt:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problembeschreibung:
Loading into an MDC table (i.e. a table created with the 
ORGANIZE BY DIMENSION clause) might fail when the sum of 
the lengths of the columns listed in the 
ORGANIZE BY DIMENSIONS clause is greater than 1024 bytes 
in total.  When calculating the length of each column, there is 
the following overhead to consider: 
- 1 byte of overhead for any nullable column 
- 2 bytes of overhead for any variable length column (example: 
VARCHAR) 
 
There are at least two possible errors that LOAD might 
encounter. 
 
1) Load fails with: 
      SQL0902C  A system error occurred. Subsequent SQL 
statements cannot be 
      processed. IBM software support reason code: "84". 
SQLSTATE=58005 
 
And the following error can be seen in the db2diag.log: 
 
2014-03-18-16.12.47.006044-240 I244959E2743      LEVEL: Severe 
PID     : 2765             TID : 46912845637952  PROC : db2sysc 
INSTANCE: dbusr1           NODE : 000            DB   : TESTDB 
APPHDL  : 0-49             APPID: *LOCAL.ztoth.140318201310 
AUTHID  : DBUSR1           HOSTNAME: hotel76 
EDUID   : 141              EDUNAME: db2lrid 
FUNCTION: DB2 UDB, index manager, spoint, probe:2419 
MESSAGE : ZRC=0x87090054=-2029453228=SQLI_PRG_ERR "Program 
error" DIA8575C An index manager programming error occurred. 
 
2) Load fails with: 
      SQL0990C  An index error occurred.  Reorganize the table. 
 
And the following errors can be seen in the db2diag.log: 
 
2014-03-18-16.19.34.281706-240 I244959E587       LEVEL: Error 
PID     : 19167            TID : 46912845637952  PROC : db2sysc 
INSTANCE: dbusr1           NODE : 000            DB   : TESTDB 
APPHDL  : 0-49             APPID: *LOCAL.ztoth.140318201956 
AUTHID  : DBUSR1           HOSTNAME: hotel76 
EDUID   : 141              EDUNAME: db2lrid 
FUNCTION: DB2 UDB, database utilities, sqluReportErrToDiag, 
probe:0 
DATA #1 : String, 127 bytes 
LOADID: 18.2014-03-18-16.19.33.865046.0 (4;4) 
 , -2063007729, 0xffffffff8509000f, Detected in 
file:sqlu_cell_table.C, Line:1825 
 
2014-03-18-16.19.34.281990-240 I245547E573       LEVEL: Error 
PID     : 19167            TID : 46912845637952  PROC : db2sysc 
INSTANCE: dbusr1           NODE : 000            DB   : TESTDB 
APPHDL  : 0-49             APPID: *LOCAL.ztoth.140318201956 
AUTHID  : DBUSR1           HOSTNAME: hotel76 
EDUID   : 141              EDUNAME: db2lrid 
FUNCTION: DB2 UDB, database utilities, sqluReportErrToDiag, 
probe:0 
DATA #1 : String, 113 bytes 
LOADID: 18.2014-03-18-16.19.33.865046.0 (4;4) 
 , -2063007729, (nil), Detected in file:sqlu_mdc_cache.C, 
Line:1756 
 
2014-03-18-16.19.34.282190-240 I246121E573       LEVEL: Error 
PID     : 19167            TID : 46912845637952  PROC : db2sysc 
INSTANCE: dbusr1           NODE : 000            DB   : TESTDB 
APPHDL  : 0-49             APPID: *LOCAL.ztoth.140318201956 
AUTHID  : DBUSR1           HOSTNAME: hotel76 
EDUID   : 141              EDUNAME: db2lrid 
FUNCTION: DB2 UDB, database utilities, sqluReportErrToDiag, 
probe:0 
DATA #1 : String, 113 bytes 
LOADID: 18.2014-03-18-16.19.33.865046.0 (4;4) 
 , -2063007729, (nil), Detected in file:sqlu_mdc_cache.C, 
Line:1112 
 
2014-03-18-16.19.34.282359-240 I246695E572       LEVEL: Error 
PID     : 19167            TID : 46912845637952  PROC : db2sysc 
INSTANCE: dbusr1           NODE : 000            DB   : TESTDB 
APPHDL  : 0-49             APPID: *LOCAL.ztoth.140318201956 
AUTHID  : DBUSR1           HOSTNAME: hotel76 
EDUID   : 141              EDUNAME: db2lrid 
FUNCTION: DB2 UDB, database utilities, sqluReportErrToDiag, 
probe:0 
DATA #1 : String, 112 bytes 
LOADID: 18.2014-03-18-16.19.33.865046.0 (4;4) 
 , -2063007729, (nil), Detected in file:sqlu_mdc_cache.C, 
Line:886 
 
2014-03-18-16.19.34.282526-240 I247268E567       LEVEL: Error 
PID     : 19167            TID : 46912845637952  PROC : db2sysc 
INSTANCE: dbusr1           NODE : 000            DB   : TESTDB 
APPHDL  : 0-49             APPID: *LOCAL.ztoth.140318201956 
AUTHID  : DBUSR1           HOSTNAME: hotel76 
EDUID   : 141              EDUNAME: db2lrid 
FUNCTION: DB2 UDB, database utilities, sqluReportErrToDiag, 
probe:0 
DATA #1 : String, 107 bytes 
LOADID: 18.2014-03-18-16.19.33.865046.0 (4;4) 
 , -2063007729, (nil), Detected in file:sqlulrid.C, Line:4707 
 
2014-03-18-16.19.34.282693-240 I247836E567       LEVEL: Error 
PID     : 19167            TID : 46912845637952  PROC : db2sysc 
INSTANCE: dbusr1           NODE : 000            DB   : TESTDB 
APPHDL  : 0-49             APPID: *LOCAL.ztoth.140318201956 
AUTHID  : DBUSR1           HOSTNAME: hotel76 
EDUID   : 141              EDUNAME: db2lrid 
FUNCTION: DB2 UDB, database utilities, sqluReportErrToDiag, 
probe:0 
DATA #1 : String, 107 bytes 
LOADID: 18.2014-03-18-16.19.33.865046.0 (4;4) 
 , -2063007729, (nil), Detected in file:sqlulrid.C, Line:5044 
 
2014-03-18-16.19.34.282859-240 I248404E567       LEVEL: Error 
PID     : 19167            TID : 46912845637952  PROC : db2sysc 
INSTANCE: dbusr1           NODE : 000            DB   : TESTDB 
APPHDL  : 0-49             APPID: *LOCAL.ztoth.140318201956 
AUTHID  : DBUSR1           HOSTNAME: hotel76 
EDUID   : 141              EDUNAME: db2lrid 
FUNCTION: DB2 UDB, database utilities, sqluReportErrToDiag, 
probe:0 
DATA #1 : String, 107 bytes 
LOADID: 18.2014-03-18-16.19.33.865046.0 (4;4) 
 , -2063007729, (nil), Detected in file:sqlulrid.C, Line:1635 
 
2014-03-18-16.19.34.283026-240 I248972E566       LEVEL: Error 
PID     : 19167            TID : 46912845637952  PROC : db2sysc 
INSTANCE: dbusr1           NODE : 000            DB   : TESTDB 
APPHDL  : 0-49             APPID: *LOCAL.ztoth.140318201956 
AUTHID  : DBUSR1           HOSTNAME: hotel76 
EDUID   : 141              EDUNAME: db2lrid 
FUNCTION: DB2 UDB, database utilities, sqluReportErrToDiag, 
probe:0 
DATA #1 : String, 106 bytes 
LOADID: 18.2014-03-18-16.19.33.865046.0 (4;4) 
 , -2063007729, (nil), Detected in file:sqlulrid.C, Line:899 
 
2014-03-18-16.19.34.283193-240 I249539E702       LEVEL: Error 
PID     : 19167            TID : 46912845637952  PROC : db2sysc 
INSTANCE: dbusr1           NODE : 000            DB   : TESTDB 
APPHDL  : 0-49             APPID: *LOCAL.ztoth.140318201956 
AUTHID  : DBUSR1           HOSTNAME: hotel76 
EDUID   : 141              EDUNAME: db2lrid 
FUNCTION: DB2 UDB, database utilities, sqluLoadEDUDriver, 
probe:2766 
MESSAGE : ZRC=0x8509000F=-2063007729=SQLI_MAXLEVEL "Max tree 
level exceeded" 
          DIA8314C Maximum number of index levels was reached. 
DATA #1 : LOADID, PD_TYPE_LOADID, 45 bytes 
LOADID: 18.2014-03-18-16.19.33.865046.0 (4;4) 
DATA #2 : File name, 10 bytes 
sqluedus.C
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All users                                                    * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 version 10.1.0.4.                             * 
****************************************************************
Local-Fix:
verfügbare FixPacks:
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows

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