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

INSTANCE PANIC DURING UPDATE OF RANGE PARTITIONED TABLE WITH PARTITIONED
INDEXES

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
The instance panic starts with the following messages in the 
db2diag.log file: 
 
2011-02-11-11.48.31.465322-300 I3847425A484       LEVEL: Severe 
PID     : 1454202              TID  : 1812        PROC : db2sysc 
INSTANCE: xxxx              NODE : 000         DB   : WSDB 
APPHDL  : 0-23                 APPID: xxxxxxxxxxxxxxxxxx 
AUTHID  : yyyy 
EDUID   : 1812                 EDUNAME: db2agent (DB) 
FUNCTION: DB2 UDB, index manager, sqliRemViol, probe:20 
DATA #1 : Hexdump, 4 bytes 
0x070000000DFF5EE0 : 8709 0054 
...T 
 
2011-02-11-11.48.31.465664-300 I3847910A460       LEVEL: Severe 
PID     : 1454202              TID  : 1812        PROC : db2sysc 
INSTANCE: xxxx              NODE : 000         DB   : WSDB 
APPHDL  : 0-23                 APPID: xxxxxxxxxxxxxxxxxx 
AUTHID  : yyyyy 
EDUID   : 1812                 EDUNAME: db2agent (DB) 
FUNCTION: DB2 UDB, index manager, sqliRemViol, probe:2 
MESSAGE : dumpVio parms: SQLI_UVIOL ptr=0 pool=65530 obj=32768 
itoken=3 
 
Error SQLI_PGR_ERR is returned by sqliRemViol due to 
inconsistent index flags on a partitioned index. 
 
The problematic index flags are created by a ALTER TABLE ATTACH 
PARTITION when: 
* the destination range partitoned table has a PARTITIONED non 
unique index 
* the table attached has a unique index, which matches with the 
non unique index from the destination table
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See error description above.                                 * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 9.7 Fix Pack 5.                       * 
****************************************************************
Local Fix:
Take care, that the index definitions for the source and 
destination table are equal before execution of the ALTER TABLE 
ATTACH PARTITION statement.
available fix packs:
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
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
First fixed in DB2 Version 9.7 Fix Pack 5.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
16.02.2011
08.12.2011
08.12.2011
Problem solved at the following versions (IBM BugInfos)
9.7.FP5
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.5 FixList