home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
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 IT03929 Status: Geschlossen

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

Produkt:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problembeschreibung:
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-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 10.1 Fix Pack 5                       * 
****************************************************************
Local-Fix:
Lösung
First fixed in DB2 Version 10.1 Fix Pack 5
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
21.08.2014
16.07.2015
07.04.2016
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version
10.1.0.5 FixList