home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Latest versionsfixlist
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
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IT11765 Status: Closed

DB2 MAY CRASH WITH SQLQGRFWDFEDPREP ON TOP OF CALL STACK WHEN REPLAYING
FEDERATED XA LOG RECORDS

product:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problem description:
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.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 10.5 Fix Pack 7                               * 
****************************************************************
Local Fix:


Solution


First Fixed in DB2 10.5 Fix Pack 7


Workaround


not known / see Local fix


Timestamps


Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :

14.10.2015
09.05.2017
09.05.2017


Problem solved at the following versions (IBM BugInfos)




Problem solved according to the fixlist(s) of the following version(s)


10.5.0.7

FixList