DB2 FOR LUW / DB2FORLUW / A50 - DB2

DB2 user might hit DB2 crash with similar callstacks like below 
(taking Windows platform as example): 
 
__intel_new_memcpy 
sqlqgRFwdFedPrep 
sqlpRecDbRedo 
sqlprProcDPSrec 
sqlpPRecReadLog 
sqlpParallelRecovery 
sqleSubCoordProcessRequest 
sqeAgent::RunEDU 
sqlzRunEDU 
sqloEDUEntry 
 
 
Situations where this could arise includes explicit rollforward 
after a restore or when performing a rolling upgrade to an HADR 
pair(referred to as "database rollforward operation" below) at 
different fixpack level than the database backup is taken. 
Known situations of exposure includes: 
 
a) the database backup is taken at GA, Fixpack 1, Fixpack 2, 
Fixpack 3 or Fixpack 3a, but database rollforward operation is 
executed on later fix packs, or 
b) the database backup is taken at Fixpack 4, but database 
rollforward operation is executed on any other fix packs, or 
c) the database backup is taken at Fixpack 5 or Fixpack 6, but 
database rollforward operation is executed on any previous fix 
packs.

**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 10.5 Fix Pack 7                               * 
****************************************************************

First Fixed in DB2 10.5 Fix Pack 7

keiner bekannt / siehe Local-Fix

Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:

14.10.2015
09.05.2017
09.05.2017