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

UPDATING INDEX CAN FAIL WITH SQLI_NOKEY "KEY NOT FOUND WITHIN
NODE"

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
Abend occurs in rare situations where all of the following are 
present: 
 
Tables were created using NON_UNIQUE collating sequence 
Indexes are present and data contains multiple versions of the 
same key entry, ie "test" and "Test" 
 
In the db2diag.log, customer may see: 
2014-03-10-11.29.26.059313-240 I11811512A765      LEVEL: Error 
PID     : 6488336              TID  : 34593       PROC : db2sysc 
0 
INSTANCE: db2advqp             NODE : 000         DB   : 
SADVDBQP 
APPHDL  : 0-35622              APPID: 
*LOCAL.db2advqp.140310152728 
AUTHID  : SLBLDMGR 
EDUID   : 34593                EDUNAME: db2agent (SADVDBQP) 0 
FUNCTION: DB2 UDB, data management, sqldUpdateIndexes, probe:741 
MESSAGE : ZRC=0x8709002C=-2029453268=SQLI_NOKEY "Key not found 
within node" 
          DIA8541C The index key could not be found, the value 
was "". 
CALLED  : DB2 UDB, index manager, sqlidelk 
RETCODE : ZRC=0x82040001=-2113667071=SQLD_NONSEVERE_PRGERR 
          "non-severe dms programming error" 
          DIA8532C An internal processing error has occurred. 
 
Followed by: 
2014-03-10-11.29.26.059800-240 I11812278A687      LEVEL: Severe 
PID     : 6488336              TID  : 34593       PROC : db2sysc 
0 
INSTANCE: db2advqp             NODE : 000         DB   : 
SADVDBQP 
APPHDL  : 0-35622              APPID: 
*LOCAL.db2advqp.140310152728 
AUTHID  : SLBLDMGR 
EDUID   : 34593                EDUNAME: db2agent (SADVDBQP) 0 
FUNCTION: DB2 UDB, data management, sqldUpdateIndexes, 
probe:1138 
MESSAGE : ZRC=0x82040001=-2113667071=SQLD_NONSEVERE_PRGERR 
          "non-severe dms programming error" 
          DIA8532C An internal processing error has occurred. 
DATA #1 : String, 47 bytes 
Key data mismatch encountered during key update 
DATA #2 : String, 8 bytes 
sqldmupd
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to version 10.1 fix pack 6 or higher                 * 
****************************************************************
Local Fix:
NA
Solution
First fixed in version 10.1 fp 6
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
05.06.2014
22.07.2015
22.07.2015
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.1.0.5 FixList