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

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

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
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 Summary:
**************************************************************** 
* 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.
available fix packs:
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

Solution
v97 fp 6 contains this fix
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
01.03.2012
05.06.2012
05.06.2012
Problem solved at the following versions (IBM BugInfos)
9.7.FP6,
9.7.FP6
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.6 FixList