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

LOAD WITH COPY YES MIGHT CAUSE INDEX CORRUPTION DURING SUBSEQUEN T
ROLLFORWARD WHEN SPECIFYING MULTIPLE COPY TARGET SESSIONS

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
Load with copy yes writes the same index root page into load 
copy files twice when rebuilding indexes: one is empty index 
root page and the other is populated one with data. 
 
When specifying multiple copy target sessions, load might write 
the two versions (empty and populated ones) of the same index 
root page into different copy files when rebuilding indexes, so 
that subsequent rollforward issued by HADR standby or standalone 
rollforward recovery might overwrite the index root page with 
the empty one during restoring load copy files. 
 
This index corruption reported by db2redom by HADR standby or 
during the rollforward recovery in db2diag.log is as below: 
 
2012-04-26-11.35.37.549683-300 I11336584A658      LEVEL: Severe 
PID     : 22937764             TID  : 18328       PROC : db2sysc 
0 
INSTANCE: test              NODE : 000         DB   : TEST 
APPHDL  : 0-336                APPID: *LOCAL.DB2.120426144404 
EDUID   : 18328                EDUNAME: db2redom (TEST) 0 
FUNCTION: DB2 UDB, index manager, sqlidkn, probe:300 
MESSAGE : Error in sqlidkn 
DATA #1 : Hexdump, 40 bytes 
0x070000010EBF8E18 : 0000 0000 0000 0000 0000 0000 0000 0098 
................ 
0x070000010EBF8E28 : 0000 0000 0000 0208 0000 0000 0000 0004 
................ 
0x070000010EBF8E38 : FFFF FFFF FFFF FFFF 
........ 
 
2012-04-26-11.35.37.550009-300 I11337243A499      LEVEL: Severe 
PID     : 22937764             TID  : 18328       PROC : db2sysc 
0 
INSTANCE: test              NODE : 000         DB   : TEST 
APPHDL  : 0-336                APPID: *LOCAL.DB2.120426144404 
EDUID   : 18328                EDUNAME: db2redom (TEST) 0 
FUNCTION: DB2 UDB, index manager, sqlidkn, probe:1317 
RETCODE : ZRC=0x87090054=-2029453228=SQLI_PRG_ERR "Program 
error" 
          DIA8575C An index manager programming error occurred. 
 
or 
 
2012-05-23-01.17.45.743616-240 I28673E531          LEVEL: Severe 
PID     : 27495                TID  : 46912975661376PROC : 
db2sysc 
INSTANCE: test               NODE : 000          DB   : 
TEST 
APPHDL  : 0-2342               APPID: *LOCAL.test.120523051601 
AUTHID  : TEST 
EDUID   : 986                  EDUNAME: db2redom (TEST) 
FUNCTION: DB2 UDB, index manager, sqliCheckKey, probe:350 
RETCODE : ZRC=0x87090054=-2029453228=SQLI_PRG_ERR "Program 
error" 
          DIA8575C An index manager programming error occurred.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All Load users                                               * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 10.1 Fix Pack 2.                      * 
****************************************************************
Local Fix:
Specify a single copy target session.
available fix packs:
DB2 Version 10.1 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows

Solution
First fixed in DB2 Version 10.1 Fix Pack 2.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
27.11.2012
17.12.2012
17.12.2012
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.1.0.2 FixList
10.5.0.2 FixList