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

WHEN ROW LENGTH EXCEEDS TEMPORARY TABLESPACE PAGE SIZE, RETURN -901 ERROR
INSTEAD OF MARKING DATABASE BAD

Produkt:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problembeschreibung:
A database is marked bad when a query requires a row length that 
exceeds the temporary tablespace page size. The database then 
goes down and crash recovery is required. 
 
The symptoms are similar to the existing APAR IC62238, but the 
error is slightly different. 
 
Messages similar to the following can be found in db2diag.log: 
 
 
2011-06-22-08.56.57.481905+120 I148242A566        LEVEL: Severe 
PID     : 17301512             TID  : 60846       PROC : db2sysc 
0 
INSTANCE: db2isnt1             NODE : 000         DB   : SAMPLE 
APPHDL  : 0-12572              APPID: 
53.190.240.210.34309.1106220643 
AUTHID  : db2inst1 
EDUID   : 60846                EDUNAME: db2agent (db2isnt1) 0 
FUNCTION: DB2 UDB, data management, sqldFastFormatFixedVar, 
probe:489 
MESSAGE : Record length > Maximum record length. 
DATA #1 : Hexdump, 8 bytes 
0x07000007C9FF7540 : 0000 0000 0000 0FBC 
........ 
 
2011-06-22-08.56.57.497824+120 I148809A555        LEVEL: Severe 
PID     : 17301512             TID  : 60846       PROC : db2sysc 
0 
INSTANCE: db2isnt1             NODE : 000         DB   : SAMPLE 
APPHDL  : 0-12572              APPID: 
53.190.240.210.34309.1106220643 
AUTHID  : db2inst1 
EDUID   : 60846                EDUNAME: db2agent (db2isnt1) 0 
FUNCTION: DB2 UDB, data management, sqldRowInsert, probe:871 
RETCODE : ZRC=0x87040055=-2029780907=SQLD_PRGERR "Unknown 
PROGRAM ERROR" 
          DIA8576C A data management services programming error 
occurred. 
 
2011-06-22-08.56.57.498122+120 I149365A534        LEVEL: Severe 
PID     : 17301512             TID  : 60846       PROC : db2sysc 
0 
INSTANCE: db2isnt1             NODE : 000         DB   : SAMPLE 
APPHDL  : 0-12572              APPID: 
53.190.240.210.34309.1106220643 
AUTHID  : db2inst1 
EDUID   : 60846                EDUNAME: db2agent (db2isnt1) 0 
FUNCTION: DB2 UDB, trace services, sqlt_logerr_string (secondary 
logging fu, probe:0 
MESSAGE : SQLD_TCB: 
DATA #1 : String, 53 bytes 
Temp Table(1:33)=<12572><db2inst1  >.TEMP (00001,00033)
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* When given a row larger than the maximum row size for a      * 
* table, DB2 marked the database bad. However, it is possible  * 
* to fail more gracefully here and simply throw an SQL0901N    * 
* error.                                                       * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 V9.7 Fix Pack 5.                              * 
****************************************************************
Local-Fix:
Workaround: 
- Alter the tablespaces to be all 32k. 
- Drop system temp tablespaces with small pagesizes.
verfügbare FixPacks:
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
This problem was first fixed in DB2 V9.7 Fix Pack 5.
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
08.07.2011
27.12.2011
27.12.2011
Problem behoben ab folgender Versionen (IBM BugInfos)
9.7.FP5
Problem behoben lt. FixList in der Version
9.7.0.5 FixList