home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Neueste VersionenFixList
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
Haben Sie Probleme? - Kontaktieren Sie uns.
Kostenlos registrieren anmeldung-x26
Kontaktformular kontakt-x26

DB2 - Problembeschreibung

Problem IT07091 Status: Geschlossen

PURESCALE ONLY; SQL1034C CAUSES MEMBER CRASH. PROCLEAF2DEL, PROBE:2;
"KEY NOT FOUND WITHIN NODE"; SQLISEARCHTREEUNDO

Produkt:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problembeschreibung:
This can occur on pureScale only and only with a unique index. 
An insert is being attempted which would result in a duplicate 
key in the index, and the  duplicate is detected which results 
in a rollback.  The rollback then fails because the key was 
inserted onto the wrong index page and cannot be found during 
the rollback.  This is a very rare scenario.  The insert 
statement fails with: 
 
SQL1034C  The database was damaged, so all applications 
processing the 
database were stopped.  SQLSTATE=58031 
 
The member will subsequently be brought down.  Applications on 
other members that do not access the table in error or do not 
require any of the locks held by the downed member will continue 
to run.  The database will be unable to be restarted on the 
downed member.  The database will have to be deactivated at all 
members and db2dart will have to be used to mark the affected 
index bad.  The database can then be restarted. 
 
If db2dart is run against the index in error the key that is not 
found will be found on the leaf page before the one that it 
should be on. 
 
*** DIAG0000/db2diag.log *** 
2014-10-09-14.24.09.296660-240 I78823691A534        LEVEL: 
Severe 
PID     : 13107442             TID : 87483          PROC : 
db2sysc 0 
INSTANCE: db2                NODE : 000           DB   : DB2DB 
APPHDL  : 0-19635              APPID: 
9.26.94.190.43590.141010233709 
AUTHID  : DB2USER                HOSTNAME: host 
EDUID   : 87483                EDUNAME: db2agent (DB2DB) 0 
FUNCTION: DB2 UDB, index manager, procLeaf2Del, probe:2 
DATA #1 : Hexdump, 4 bytes 
0x0A00000030FF4414 : 8709 002C 
..., 
 
.... 
 
2014-10-09-14.24.09.298696-240 I78825992A532        LEVEL: 
Severe 
PID     : 13107442             TID : 87483          PROC : 
db2sysc 0 
INSTANCE: db2                NODE : 000           DB   : DB2DB 
APPHDL  : 0-19635              APPID: 
9.26.94.190.43590.141010233709 
AUTHID  : DB2USER                HOSTNAME: host 
EDUID   : 87483                EDUNAME: db2agent (DB2DB) 0 
FUNCTION: DB2 UDB, index manager, sqlischd, probe:973 
DATA #1 : Hexdump, 4 bytes 
0x0A00000030FF4538 : 8709 002C 
..., 
 
2014-10-09-14.24.09.299147-240 I78826525A1574       LEVEL: 
Severe 
PID     : 13107442             TID : 87483          PROC : 
db2sysc 0 
INSTANCE: db2                NODE : 000           DB   : DB2DB 
APPHDL  : 0-19635              APPID: 
9.26.94.190.43590.141010233709 
AUTHID  : DBUSER                HOSTNAME: host 
EDUID   : 87483                EDUNAME: db2agent (DB2DB) 0 
FUNCTION: DB2 UDB, index manager, sqlischd, probe:973 
RETCODE : ZRC=0x8709002C=-2029453268=SQLI_NOKEY "Key not found 
within node" 
          DIA8541C The index key could not be found, the value 
was "". 
... 
 
*** 
DIAG0000/FODC_IndexError_2014-10-09-14.24.09.300692_13107442_874 
83_000/13107442.87483.000.stack.txt *** 
<Trap> 
<Header> 
DB2 build information: DB2 v10.5.0.5 s141006 SQL10055 
timestamp: 2014-10-09-14.24.09.813768 
instance name: db2.000 
EDU name     : db2agent (DB2DB) 0 [-] 
EDU ID       : 87483 
Signal #31 
uname: S:AIX R:1 V:7 M:000915ABD400 N:pscaleflex25 
process id: 13107442 
parent process id: 10878976 
thread id : 87483 (0x155BB) 
kthread id : 18612309 
</Header> 
<SignalDetails> 
<Siginfo_t length="64"> 
0000001F 00000000 00000009 00000000 
00000000 00000000 00000000 00000000 
00000000 00000000 00000000 00000000 
00000000 00000000 00000000 00000000 
</Siginfo_t> 
Signal #31 (SIGUSR2); si_code: 9 (SI_EMPTY:siginfo_t contains no 
useful information.) 
</SignalDetails> 
<StackTrace> 
-------Frame------ ------Function + Offset------ 
0x0900000000534F94 pthread_kill + 0xD4 
0x09000000069B72F0 sqloDumpEDU + 0xC4 
0x0900000006FE62B4 
@160@sqlischdDumpData__FP7SQLI_CBP11SQLI_SDGLOBi + 0x2D0 
0x0900000008504CE0 sqlischd__FP7SQLI_CBP11SQLI_SDGLOBUsUi + 
0x1570 
0x0900000008519CD4 sqlischd__FP7SQLI_CBP11SQLI_SDGLOBUsUi + 
0x99C 
0x0900000006C7ED5C 
@160@sqliSearchTreeUndo__FP7SQLI_CBUcT2P8SQLD_KEYP12SQLI_KEYDATA 
Ul + 0x500 
0x09000000085010F8 
@160@sqliUndoAddKey__FP7SQLI_CBUcUiP9SQLP_LSN8P12SQLI_KEYDATAT5P 
13SQLI_SLOT_LOGP9SQLI_SLOTPUcP8SQLD_KEYiUlPUl + 0x52C 
0x0900000008510DBC 
@160@sqliUndoAddKey__FP7SQLI_CBUcUiP9SQLP_LSN8P12SQLI_KEYDATAT5P 
13SQLI_SLOT_LOGP9SQLI_SLOTPUcP8SQLD_KEYiUlPUl + 0x11F8 
0x0900000008E11950 sqliundo__FP8sqeAgentP8SQLD_TCBPcP9SQLP_LSN8 
+ 0x798 
0x0900000008E10DA8 
sqldmund__FP8sqeAgentP8SQLP_LRHPcP15SQLD_RECOV_INFO + 0x2F4 
0x0900000008E1C014 
sqldmund__FP8sqeAgentP8SQLP_LRHPcP15SQLD_RECOV_INFO + 0x210 
0x0900000008E1BA00 
sqlptudo__FP8sqeAgentC12sqlpUndoTypePUlP15SQLD_RECOV_INFOP11SQLP 
_TENTRYP8SQLP_LRHPc + 0x1C8 
0x0900000008E1B698 sqlptud1__FP8sqeAgentUl + 0x38 
0x090000000831F96C sqlpSpRb__FP8sqeAgentC11SQLP_SPTYPEUl + 0x29C 
0x09000000083237E8 
sqlrr_stmt_rbk_svpt__FP8sqlrr_cbP19sqlr_savepoint_infoi + 0xE0 
0x0900000008718C4C sqlreesp__FP8sqlrr_cbP19sqlr_savepoint_infoi 
+ 0x124 
0x09000000086CD1B8 sqlreesp__FP8sqlrr_cbP19sqlr_savepoint_infoi 
+ 0xE4 
0x0900000008B222A0 
sqlr_end_savept__FP8sqlrr_cbiT2UiP19sqlr_savepoint_infoT4T2 + 
0x204 
0x09000000082EC788 
sqlrr_execimmd__FP14db2UCinterfaceP16db2UCprepareInfo + 0x2918 
0x09000000082E9F5C 
sqlrr_execimmd__FP14db2UCinterfaceP16db2UCprepareInfo + 0xEC 
0x0900000008BF9F20 
sqljsParseRdbAccessed__FP13sqljsDrdaAsCbP13sqljDDMObjectP14db2UC 
interface + 0x161C 
0x0900000008B7CF90 
sqljsParseRdbAccessed__FP13sqljsDrdaAsCbP13sqljDDMObjectP14db2UC 
interface + 0x170 
0x09000000092107DC 
sqljsParse__FP13sqljsDrdaAsCbP14db2UCinterfaceP8sqeAgentb@OL@242 
90 + 0x638 
0x0900000008C2C1F4 @72@sqljsSqlam__FP14db2UCinterfaceP8sqeAgentb 
+ 0x2C 
0x0900000008BB78C0 @72@sqljsSqlam__FP14db2UCinterfaceP8sqeAgentb 
+ 0x368 
0x09000000099C6144 
@72@sqljsDriveRequests__FP8sqeAgentP14db2UCconHandle + 0x1E0 
0x09000000099C6B18 
@72@sqljsDrdaAsInnerDriver__FP18SQLCC_INITSTRUCT_Tb + 0x5F4 
0x0900000009560C28 RunEDU__8sqeAgentFv + 0x40FB0 
0x09000000095B3718 RunEDU__8sqeAgentFv + 0x120 
0x0900000007EA9560 EDUDriver__9sqzEDUObjFv + 0x128 
0x0900000009589DDC sqloEDUEntry + 0x398 
</StackTrace>
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* pureScale users                                              * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to the latest fix pack.                              * 
*                                                              * 
* A temporary workaround is to use db2dart to mark the         * 
* affected index bad and restart the database.                 * 
****************************************************************
Local-Fix:
Deactivate the database on all members.  Use db2dart to mark the 
affected index bad and restart the database.
Lösung
Problem was first fixed in DB2 UDB Version 10.5 fix pack 7.
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
11.02.2015
19.01.2016
28.04.2016
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version
10.5.0.7 FixList