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

INDEX RECREATE FAILS WITH SQLRLRECREATEINDEXOBJECT, PROBE:30

Produkt:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problembeschreibung:
In heavy workload situations, a rare timing hole may cause index 
recreation to fail with a message in db2diag.log similar to the 
following: 
 
2010-10-21-01.46.11.845112+480 I2267924A490       LEVEL: Severe 
PID     : 574054               TID  : 18607       PROC : db2sysc 
34 
INSTANCE: db2inst1             NODE : 034         DB   : SAMPLE 
APPHDL  : 0-1574               APPID: 
10.238.100.51.25797.10102017410 
AUTHID  : ETL20 
EDUID   : 18607                EDUNAME: db2agntp (SAMPLE) 34 
FUNCTION: DB2 UDB, catalog services, sqlrlRecreateIndexObject, 
probe:30 
RETCODE : ZRC=0x8404007E=-2080112514=SQLD_IXNOEX "INDEX DOES NOT 
EXIST" 
 
In such situations, the database may be marked bad.
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* An issue with lock escalation during index recreate could    * 
* cause DB2 to trap and erroneously mark the database as bad.  * 
* In such cases, the data in the database is actually fine.    * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 V9.7 Fix Pack 4.                              * 
****************************************************************
Local-Fix:
verfügbare FixPacks:
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
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

Lösung
This problem was first fixed in DB2 V9.7 Fix Pack 4.
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
30.11.2010
29.04.2011
29.04.2011
Problem behoben ab folgender Versionen (IBM BugInfos)
9.7.FP4
Problem behoben lt. FixList in der Version
9.7.0.4 FixList