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

DATA LOST AFTER ROLLFORWARD THROUGH SUCCESSFUL LOAD ... ALLOW READ ACCESS
THAT WAS RUN IN V105 FIX PACK 4.

product:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problem description:
Problem affects only the following LOAD operations (if any of 
below conditions is false then the problem does NOT happen): 
- ALLOW READ ACCESS option specified 
- USE TABLESPACE option specified 
- COPY YES option specified 
- table has indexes 
- LOAD command was run on v105 fixpack 4 (any fix packs before 
that do NOT have the problem) 
 
During INDEX COPY phase LOAD writes incorrect information to 
HISTORY file as well as database logs. 
Follow up LIST HISTORY command may not list corresponding LOAD 
command, as well as ROLLFORWARD may skip replaying COPY image 
produced. 
 
This means LOADed data is lost after ROLLFORWARD.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* Any setup, but LOAD command is very specific - see Error     * 
* Description                                                  * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to product DB2 version 10.5 Fix Pack 5               * 
****************************************************************
Local Fix:
Solution
Fix provided in DB2 version 10.5 Fix Pack 5
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
20.10.2014
15.12.2014
15.12.2014
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.5.0.5 FixList