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

RECOVERY MAY FAIL IF A CRASH HAPPENS WHEN EXTENT MOVEMENT AND LOAD REPLACE
ARE RUN TOGETHER

Produkt:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problembeschreibung:
If a crash happens when extent movement and load replace, then 
there is a chance the subsequent crash recovery might fail.  The 
reason is because load does not obtain a lock required to 
serialize with extent movement, causing crash recovery to see 
wrong data. 
 
The crash recovery would fail with the following message: 
 
2012-01-24-01.24.55.460320-300 I13079761E677        LEVEL: Error 
PID    : 32561                TID : 47236570409280  KTID : 1306 
PROC    : db2sysc 2 
INSTANCE: db2inst             NODE : 002            DB  : SAMPLE 
APPHDL  : 2-52                APPID: *N2.eunicec4.120124062350 
AUTHID  : db2inst             HOSTNAME: host 
EDUID  : 134                  EDUNAME: db2agent (SAMPLE) 2 
FUNCTION: DB2 UDB, recovery manager, sqlpresr, probe:640 
MESSAGE : ZRC=0x8402001A=-2080243686=SQLB_EMP_MAP_INFO_END "EMP 
MAP INFO END" 
DATA #1 : <preformatted> 
Crash recovery failed! 
LowtranLSN 0000000000B7CBE9,  MinbuffLSN 0000000000BD3DA2, 
Recovery started on log file S0000343.LOG.
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All extent movement user                                     * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See error description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* upgrade to v97 fp 6, or avoid running extent movement with   * 
* load replace together.                                       * 
****************************************************************
Local-Fix:
Contact service if this happens.  Apply the fixpak containing 
this fix or avoid running extent movement and load replace 
together.
verfügbare FixPacks:
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows

Lösung
v97 fp 6 contains this fix
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
01.03.2012
05.06.2012
05.06.2012
Problem behoben ab folgender Versionen (IBM BugInfos)
9.7.FP6,
9.7.FP6
Problem behoben lt. FixList in der Version
9.7.0.6 FixList