|
Problem IT08116
|
Status: Closed |
INSTANCE CRASHED IN SETUPINDEXKEYFROMZVAL AFTER APPLYING FIX PACK |
| product: |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 |
| Problem description: |
The stored procedure accessing a column organized table may
cause the server instance crash after applying a Fix Pack.
This problem could happen when the base DB2 Fix Pack level is
Fix Pack 3 or earlier and the the newly applied Fix Pack level
is Fix Pack 4, Fix Pack 5 or Fix Pack 6.
The stack trace for segv like the following would be observed
for this problem.
DatabaseTableAccessor::setupIndexKeyFromZVal
DatabaseTableAccessor::indexKeyInsert
TableWriter::addKeyToIndexes
TableWriter::insertTupleBuffered
TableAccessor::insertRowInternal
TableAccessor::insertRow
cdeTableAccessorInterface::insertRow
cdeInterface::performInsert
sqlriCdeFastInsert
sqlriSectInvoke |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* User using BLU Acceleration on Server applied FP4 to FP6 on *
* FP3 or below. *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 version 10.5.0.7. *
**************************************************************** |
| Local Fix: |
Rebind the packages associated with the stored procedure to
avoid a segv
ex, db2 call SYSPROC.REBIND_ROUTINE_PACKAGE( 'P' , ROUTINENAME
, '' ) |
| Solution |
The problem is first fixed in DB2 version 10.5.0.7. |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 02.04.2015
22.12.2016
22.12.2016 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.5.0.7
|
 |
