Neueste VersionenFixList
11.1.0.7 FixList
10.5.0.9 FixList
10.1.0.6 FixList
9.8.0.5 FixList
9.7.0.11 FixList
9.5.0.10 FixList
9.1.0.12 FixList
Haben Sie Probleme? - Kontaktieren Sie uns.
Kostenlos registrieren anmeldung-x26
Kontaktformular kontakt-x26

DB2 - Problembeschreibung

Problem IT08116 Status: Geschlossen

INSTANCE CRASHED IN SETUPINDEXKEYFROMZVAL AFTER APPLYING FIX PACK

Produkt:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problembeschreibung:
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-Zusammenfassung:
**************************************************************** 
* 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 
, '' )
Lösung
The problem is first fixed in DB2 version 10.5.0.7.
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
02.04.2015
22.12.2016
22.12.2016
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version
10.5.0.7 FixList