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

DETACH PARTITION MAY FAIL AND GET SQL0911N

Produkt:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problembeschreibung:
DETACH PARTITION may fail and get SQL0911N 
 
An example : 
 
CREATE TABLE TAB1 ( C1 INT, C2 INT, C3 INT, C4 INT, C5 
DECFLOAT(16) ) 
  IN TS0 INDEX IN TS0X 
 
  DISTRIBUTE BY HASH  (C1) 
 
  PARTITION  BY RANGE (C2) ( 
 
   STARTING (MINVALUE) 
 
            ENDING    0  , 
 
            ENDING  100  , 
 
            ENDING  200  , 
 
            ENDING  300  , 
 
            ENDING  400  , 
 
            ENDING  500  , 
 
            ENDING  600  , 
 
            ENDING  700  , 
 
            ENDING  800  , 
 
            ENDING  900  , 
 
            ENDING 1000  , 
 
   ENDING (MAXVALUE) 
 
) 
 
ORGANIZE   BY DIMENSIONS (C3,C4); 
 
create index TAB1_IX1 on TAB1(c1,c2); 
 
create index TAB1_IX2 on TAB1(c1,c2,c3 ) NOT PARTITIONED ; 
 
 
 
 
ALTER TABLE TAB1 DETACH PARTITION part3 INTO part3 
 
DB20000I  The SQL command completed successfully. 
 
 
commit 
 
DB20000I  The SQL command completed successfully. 
 
ALTER TABLE TAB1 DETACH PARTITION part4 INTO part4 
 
DB21034E  The command was processed as an SQL statement because 
it was not a valid Command Line Processor command. 
During SQL processing it returned: 
 
SQL0911N  The current transaction has been rolled back because 
of a deadlock or timeout. Reason code "2".  SQLSTATE=40001 
 
commit 
 
DB20000I  The SQL command completed successfully.
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* DB2 UDB Version 9.7                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error description field for more information.            * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to Version 9.7 FixPack 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
Problem was first fixed in DB2 UDB Version 9.7 FixPack 4.
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
17.01.2011
03.05.2011
03.05.2011
Problem behoben ab folgender Versionen (IBM BugInfos)
9.7.FP4
Problem behoben lt. FixList in der Version
9.7.0.4 FixList