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 IT03929 Status: Closed

DB2 MAY CRASH WHEN REPLAYING FEDERATED XA LOG RECORDS IF FEDERATED
TWO_PHASE COMMIT IS USED

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
DB2 version 10.1 fixpack 4 or later may crash when trying to 
replay 
federated XA log records produced on a different 10.1 fixpack. 
 
The stack seen will be: 
  memcpy 
  sqlqgRFwdFedPrep 
  sqlpRecDbRedo 
  ... 
 
When upgrading to a new fixpak or when rolling fixpak back, 
please, avoid using federated XA log records produced on a 
different fixpak. 
If this is unavoidable, please, request Special Build from DB2 
Support to replay old logs. 
After the issue is resolved, please, un-install Special Build 
and take a new backup to avoid any need to replay problematic 
log records again.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 10.1 Fix Pack 5                       * 
****************************************************************
Local Fix:
Solution
First fixed in DB2 Version 10.1 Fix Pack 5
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
21.08.2014
16.07.2015
07.04.2016
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.1.0.5 FixList