|
Problem IT05075
|
Status: Closed |
MEMBER CRASH RECOVERY MAY CONTINUOUSLY FAIL WITH SQLB_EMP_MAP_INFO_NOT_FOUND ERROR |
| product: |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 |
| Problem description: |
In a pureScale environment, if one member has crashed while
performing an update on a table, and another member performs a
REORG INDEX RECLAIM EXTENTS operation on that same table while
the first member is unavailable, the crash recovery of the first
member may fail with the following error:
2014-10-01-14.39.06.487160-240 I230947131E5077 LEVEL:
Severe
PID : 6711 TID : 47190072355136 KTID : 6790
PROC : db2sysc 0
INSTANCE: db2user NODE : 000 DB :
SAMPLE
APPHDL : 0-53 APPID: *N0.DB2.141001183449
HOSTNAME: db2server
EDUID : 34 EDUNAME: db2agnti (SAMPLE ) 0
FUNCTION: DB2 UDB, buffer pool services, sqlbDMScheckObjAlloc,
probe:826
MESSAGE : ZRC=0x8402001B=-2080243685=SQLB_EMP_MAP_INFO_NOT_FOUND
"EMP MAP INFO NOT FOUND"
The crash recovery is attempting to undo a log record that
affects an extent that has been reclaimed by the index reorg,
and as a result, cannot complete.
Other errors are possible as a result of this defect, including
but not limited
to possible incorrect results, or severe error messages in the
db2diag.log
reporting SQLI_PRG_ERR from probe 206 from one of the following
functions:
sqliUndoAddKey
sqliUndoDelKey
sqliUndoMarkKey
sqliUndoUpdKey
sqliUndoPrefixImprovement
sqliUndoSetSMOD
sqliundo |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* pureScale *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to the latest fix pack *
**************************************************************** |
| Local Fix: |
To allow the member crash recovery to complete, you will need to
issue db2stop, mark the index as invalid with db2dart, and then
restart DB2. |
| Solution |
Problem is first fixed in DB2 UDB version 10.1 fix pack 5 |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 21.10.2014
13.07.2015
13.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
|
 |
