|
Problem IC77428
|
Status: Closed |
WHEN ROW LENGTH EXCEEDS TEMPORARY TABLESPACE PAGE SIZE, RETURN -901 ERROR INSTEAD OF MARKING DATABASE BAD |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
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 Summary: |
****************************************************************
* 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. |
| available fix packs: |
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
|
| Solution |
This problem was first fixed in DB2 V9.7 Fix Pack 5. |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 08.07.2011
27.12.2011
27.12.2011 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.FP5
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.5
|
 |
