DB2 - Problem description
Problem IC73928 | Status: Closed |
DETACH PARTITION MAY FAIL AND GET SQL0911N | |
product: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
Problem description: | |
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 Summary: | |
**************************************************************** * 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: | |
available fix packs: | |
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows | |
Solution | |
Problem was first fixed in DB2 UDB Version 9.7 FixPack 4. | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 17.01.2011 03.05.2011 03.05.2011 |
Problem solved at the following versions (IBM BugInfos) | |
9.7.FP4 | |
Problem solved according to the fixlist(s) of the following version(s) | |
9.7.0.4 |