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 IC62333 Status: Geschlossen

DB2 crashes - SQLICVTUNIQ, PROBE:1030

Produkt:
DB2 FOR LUW / DB2FORLUW / 950 - DB2
Problembeschreibung:
Crash recovery seems to be failing on about 20 nodes while 
trying to change the indextype of an index. Here's the messages 
from the diag log: 
 
2009-08-02-01.34.39.468813+330 I97288A498         LEVEL: Severe 
 
PID     : 169756               TID  : 21429       PROC : db2sysc 
20 
 
INSTANCE: db2inst1             NODE : 020         DB   : 
PRODLTRA 
 
APPHDL  : 0-452                APPID: *N0.db2inst1.090801200422 
 
AUTHID  : DB2INST1 
 
EDUID   : 21429                EDUNAME: db2redom (PRODLTRA) 20 
 
FUNCTION: DB2 UDB, index manager, sqliCvtUniq, probe:1030 
 
DATA #1 : Hexdump, 4 bytes 
 
0x07000001AB7FB610 : 8709 0054 
...T 
 
 
 
 
 
2009-08-02-01.34.39.469048+330 I97787A526         LEVEL: Severe 
 
PID     : 169756               TID  : 21429       PROC : db2sysc 
20 
 
INSTANCE: db2inst1             NODE : 020         DB   : 
PRODLTRA 
 
APPHDL  : 0-452                APPID: *N0.db2inst1.090801200422 
 
AUTHID  : DB2INST1 
 
EDUID   : 21429                EDUNAME: db2redom (PRODLTRA) 20 
 
FUNCTION: DB2 UDB, index manager, sqliRedo, probe:0 
 
RETCODE : ZRC=0x87090054=-2029453228=SQLI_PRG_ERR "Program 
error" 
 
DIA8575C An index manager programming error occurred. 
 
 
 
2009-08-02-01.34.39.469413+330 I98314A546         LEVEL: Severe 
 
PID     : 169756               TID  : 21429       PROC : db2sysc 
20 
 
INSTANCE: db2inst1             NODE : 020         DB   : 
PRODLTRA 
 
APPHDL  : 0-452                APPID: *N0.db2inst1.090801200422 
 
AUTHID  : DB2INST1 
 
EDUID   : 21429                EDUNAME: db2redom (PRODLTRA) 20 
 
FUNCTION: DB2 UDB, trace services, sqlt_logerr_data (secondary 
logging func, probe:0 
 
MESSAGE : SQLP_LSN 
 
DATA #1 : Hexdump, 6 bytes 
 
0x070000022B0047DA : 00C2 FCA1 37C6
Problem-Zusammenfassung:
Users Affected: All 
 
Problem description: 
Crash recovery fails on nodes while trying to change the 
indextype of an index. Here's the messages from the diag log: 
 
 
2009-08-02-01.34.39.468813+330 I97288A498         LEVEL: Severe 
 
PID     : 169756               TID  : 21429       PROC : db2sys 
20 
 
INSTANCE: db2inst1             NODE : 020         DB   : 
PRODLTRA 
 
APPHDL  : 0-452                APPID: *N0.db2inst1.090801200422 
 
AUTHID  : DB2INST1 
 
EDUID   : 21429                EDUNAME: db2redom (PRODLTRA) 20 
 
FUNCTION: DB2 UDB, index manager, sqliCvtUniq, probe:1030 
 
DATA #1 : Hexdump, 4 bytes 
 
0x07000001AB7FB610 : 8709 0054 
...T 
 
 
 
 
 
2009-08-02-01.34.39.469048+330 I97787A526         LEVEL: Severe 
 
PID     : 169756               TID  : 21429       PROC : db2sys 
20 
 
INSTANCE: db2inst1             NODE : 020         DB   : 
PRODLTRA 
 
APPHDL  : 0-452                APPID: *N0.db2inst1.090801200422 
 
AUTHID  : DB2INST1 
 
EDUID   : 21429                EDUNAME: db2redom (PRODLTRA) 20 
 
FUNCTION: DB2 UDB, index manager, sqliRedo, probe:0 
 
RETCODE : ZRC=0x87090054=-2029453228=SQLI_PRG_ERR "Program 
error" 
 
DIA8575C An index manager programming error occurred. 
 
 
 
2009-08-02-01.34.39.469413+330 I98314A546         LEVEL: Severe 
 
PID     : 169756               TID  : 21429       PROC : db2sys 
20 
 
INSTANCE: db2inst1             NODE : 020         DB   : 
PRODLTRA 
 
APPHDL  : 0-452                APPID: *N0.db2inst1.090801200422 
 
AUTHID  : DB2INST1 
 
EDUID   : 21429                EDUNAME: db2redom (PRODLTRA) 20 
 
FUNCTION: DB2 UDB, trace services, sqlt_logerr_data (secondary 
logging func, probe:0 
 
MESSAGE : SQLP_LSN 
 
DATA #1 : Hexdump, 6 bytes 
 
0x070000022B0047DA : 00C2 FCA1 37C6 
 
LOCAL FIX: 
None
Local-Fix:
verfügbare FixPacks:
DB2 Version 9.5 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 6a for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 10 for Linux, UNIX, and Windows

Lösung
First fixed in V95 FP 5 
 
 
 
 
 
 
c 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
c 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
c
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
03.08.2009
17.12.2009
17.12.2009
Problem behoben ab folgender Versionen (IBM BugInfos)
9.5.FP5
Problem behoben lt. FixList in der Version
9.5.0.5 FixList