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

ROLLBACK OF TRANSACTION MAY FAIL WITH SQLI_SMP_ERR "SMP PROBLEMS"
WHEN USING PARTITIONED INDEXES

Produkt:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problembeschreibung:
The problem affects partitioned tables with partitioned indexes. 
 
If there is a lock escalation on a partition for a unit of work 
and then deletes occur against against records in that 
partition, since the application holds an X lock on the 
partition, DB2 will perform physical deletes from the index 
instead of marking the keys as pseudo deleted.  DB2 will also 
free index pages instead of marking them as pending pseudo 
empty. 
 
If another transaction tries to create an index on the table, it 
will create an empty root page and get blocked trying to upgrade 
its lock from an IN to an S lock. 
 
If the first transaction rolls back the deletes, we may fail 
during the rollback with messages similar to the following: 
 
2011-02-01-16.09.33.969470+060 I75937578A514      LEVEL: Severe 
PID    : 909350              TID  : 36352      PROC : db2sysc 
2 
INSTANCE: db2inst1            NODE : 002        DB  : SAMPLE 
APPHDL  : 0-35847              APPID: 
172.16.99.62.34364.110201143801 
AUTHID  : ADMDW 
EDUID  : 36352                EDUNAME: db2agnta (SAMPLE) 2 
FUNCTION: DB2 UDB, index manager, sqliundo, probe:2310 
RETCODE : ZRC=0x87090052=-2029453230=SQLI_SMP_ERR "SMP problems" 
          DIA8573C An invalid space map page was found.
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* Users of partitioned tables with partitioned indexes.        * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Problem Description above.                               * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 9.7 Fix Pack 5.                       * 
****************************************************************
Local-Fix:
verfügbare FixPacks:
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
First Fixed in Version 9.7 Fix Pack 5.
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
03.02.2011
23.12.2011
23.12.2011
Problem behoben ab folgender Versionen (IBM BugInfos)
9.7.FP5
Problem behoben lt. FixList in der Version
9.7.0.5 FixList