|
Problem IC84603
|
Status: Closed |
DATABASE CRASH DUE TO INCORRECT ROW WIDTH WHEN INSERTING INTO A TEMPORARY TABLE WITH XML COLUMNS IN A MERGE JOIN. |
| product: |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 |
| Problem description: |
The symptom of this problem is a database crash. The following
entries will be
logged in the db2diag.log before the crash:
2012-04-10-21.28.30.700425-240 I26566A556 LEVEL: Severe
PID : 4698234 TID : 1544 PROC : db2sysc
INSTANCE: jtnisbet NODE : 000 DB : TESTER
APPHDL : 0-7 APPID:
*LOCAL.jtnisbet.120411010306
AUTHID : JTNISBET
EDUID : 1544 EDUNAME: db2agent (TESTER)
FUNCTION: DB2 UDB, data management, sqldFastFormatFixedVar,
probe:489
MESSAGE : Record length > Maximum record length.
DATA #1 : Hexdump, 8 bytes
0x070000000EBF6BB8 : 0000 0000 0000 2733
......'3
2012-04-10-21.28.30.702859-240 I27123A545 LEVEL: Severe
PID : 4698234 TID : 1544 PROC : db2sysc
INSTANCE: jtnisbet NODE : 000 DB : TESTER
APPHDL : 0-7 APPID:
*LOCAL.jtnisbet.120411010306
AUTHID : JTNISBET
EDUID : 1544 EDUNAME: db2agent (TESTER)
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.
The db2dump directory will contain a stack traceback file with
something
like the following stack:
MarkDBBad + 0x30C
sqldDumpContext + 0x870
sqldRowInsert + 0x1670
sqlri_mgjnAppendToBuffer + 0x142C
sqlri_mj + 0x2414
sqlriExecThread + 0x584
This problem might happen if the following conditions are ALL
true:
- There is a merge join in the access plan, where the inner
columns (right
side of the join) consists of at least one XML column.
- The merge join's inner stream of rows feature duplicate values
of the inner join key
and it matches to the outer join key.
- There is a shortage of sort memory such that the merge join
can no longer
buffer the inner rows in memory and is forced to spill rows to a
temp table. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* DB2 V9.7 V10.1 *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 V10.1 FP1 *
**************************************************************** |
| Local Fix: |
Since the problem is specific to a merge join, it may be
possible to optimize the
query in a different way that chooses an alternate join method. |
| available fix packs: |
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
|
| Solution |
First fixed in DB2 V10.1 FP1 |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 14.06.2012
02.11.2012
02.11.2012 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.1.0.1
|
 |
| 10.5.0.1
|
|
