|
Problem IT04177
|
Status: Closed |
CONCURRENT INSERT AND REORG RECLAIM EXTENT ON MDC TABLE MAY ABEND SERVER WITH DIA8737C |
| product: |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 |
| Problem description: |
An INSERT into a MDC table may abend server starting with the
following messages in the db2diag.log file:
2014-08-25-00.22.23.439952+120 I25944289A609 LEVEL:
Severe
PID : 3735836 TID : 45492 PROC :
db2sysc 0
INSTANCE: xxxx NODE : 000 DB : yyy
APPHDL : 0-100 APPID:
10.10.0.126.32875.140817082313
AUTHID : xxxxx HOSTNAME: zzzz
EDUID : 45492 EDUNAME: db2agent (yyy) 0
FUNCTION: DB2 UDB, sqldb, sqldb_createNewBlock, probe:217
RETCODE : ZRC=0x870400CC=-2029780788=SQLDB_PRGERR
"Block Management Services program error"
DIA8737C A block management services programming error
occurred.
2014-08-25-00.22.23.450325+120 I25944899A609 LEVEL:
Severe
PID : 3735836 TID : 45492 PROC :
db2sysc 0
INSTANCE: xxxx NODE : 000 DB : yyy
APPHDL : 0-100 APPID:
10.10.0.126.32875.140817082313
AUTHID : xxxxx HOSTNAME: zzzzz
EDUID : 45492 EDUNAME: db2agent (yyy) 0
FUNCTION: DB2 UDB, sqldb, sqldb_createNewBlock, probe:251
RETCODE : ZRC=0x870400CC=-2029780788=SQLDB_PRGERR
"Block Management Services program error"
DIA8737C A block management services programming error
occurred.
Stack trace for the failing INSERT looks like this:
0x09000000007CFF54 pthread_kill + 0xD4
0x0900000011CEEA98 sqloDumpEDU + 0x6C
0x09000000133E0918 sqleDoForceDBShutdownFODC + 0x27C
0x09000000121A52F0 ForceDBShutdown + 0x6EC
0x09000000102C90D0 sqldDumpContext + 0x9C0
0x090000001220B5D8 sqldb_createNewBlock + 0x3180
0x09000000124255FC sqldExtendTable + 0x2EF0
0x09000000146399C4 sqldb_allocateNewBlocki + 0xE4
0x090000001464DA84 sqldb_findNewBlock + 0x4DC
0x090000001464C138 sqldb_findNewBlockAndInsert + 0x4A0
0x090000001464ADB8 sqldb_insertRow + 0x694
0x0900000011672250 sqldRowInsert + 0x664
0x090000001144567C sqlrinsr + 0xAC
0x0900000011445464 sqlriisr + 0x164
0x09000000114BEBE8 sqlriSectInvoke + 0x30
...
The following additional conditions need to be true:
* A REORG RECLAIM EXTENTS needs to be active on the MDC table in
question
* The MDC table must have been migrated from DB2 V9.5 or earlier
to V10.x |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* All *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 Version 10.1 Fix Pack 5. *
**************************************************************** |
| Local Fix: |
|
| Solution |
First fixed in DB2 Version 10.1 Fix Pack 5. |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 04.09.2014
17.07.2015
17.07.2015 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.1.0.5
|
 |
