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 IT02693 Status: Geschlossen

DURING REMOTE CATCHUP DUE TO INCORRECT MAPPING OF LOG FILE HADR SETUP FAILS
on a 32 bit instance

Produkt:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problembeschreibung:
During Remote Catchup due to incorrect mapping of log file HADR 
setup fails 
 
remote catchup starts at 
 
2014-06-11-14.51.12.942000+330 I31637H433           LEVEL: Info 
FUNCTION: DB2 UDB, High Availability Disaster Recovery, 
hdrSPrepareLogWrite, probe:10260 
DATA #1 : <preformatted> 
RCUStartLso 51532868001 
 
sqlplfrExtentFromLSO incorrectly maps the LSO  to an incorrect 
log extent which causes HADR setup to fail 
 
FUNCTION: DB2 UDB, recovery manager, sqlplfrExtentFromLSO, 
probe:4175 
DATA #1 : <preformatted> 
LFR Scan Num            = 1 
LFR Scan Caller's EDUID = 6988 
Start guess and try for lso 4288227745
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* DB2 V10.5 FP4                                                * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB V10.5 FP5                                      * 
****************************************************************
Local-Fix:
Lösung
First fixed in DB2 V10.5 FP5
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
20.06.2014
24.07.2015
24.07.2015
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version
10.1.0.5 FixList