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

CAN DROP A RANGE PARTITIONED TABLE WITH AN ACTIVE QUIESCE TABLESPACE LOCK,
SHOULD RETURN SQL0290N INSTEAD

Produkt:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problembeschreibung:
DB2 will allow to DROP a range partitioned table, which has an 
active QUIESCE TABLESPACE lock. This leaves the tablespaces in 
quiesce state, without the ability to do a QUIESCE RESET. While 
the QUIESCE is active, DROP should return SQL0290N, which is the 
case for a table without range partitioning. 
 
Example for a range partitioned table: 
CREATE TABLE "DB2V974 "."T1"  ( 
                  "C1" INTEGER NOT NULL , 
                  "C2" CHAR(10) ) 
                 PARTITION BY RANGE("C1") ( 
                 PART "PART0" STARTING(1) ENDING(10) IN "TS1", 
                 PART "PART1" STARTING(11) ENDING(20) IN "TS2", 
                 PART "PART2" STARTING(21) ENDING(30) IN "TS3" 
                 ); 
 
After QUIESCE TABLESPACES FOR TABLE T1 EXCLUSIVE, LIST 
TABLESPACES SHOW DETAIL will show the following information for 
tablespaces TS1, TS2 and TS3: 
... 
 Tablespace ID                        = 3 
 Name                                 = TS1 
... 
 Number of quiescers                  = 1 
   Quiescer 1: 
     Tablespace ID                    = 65530 
     Object ID                        = 32768 
 
Please note, that the GLOBAL Tablespace ID and Object ID are 
shown in the tablespace quiesce information, which differes from 
the real Tablespace ID, as shown above. All tablespaces used by 
the range partitioned table will show the same quiesce 
information.
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 9.7 Fix Pack 6.                       * 
****************************************************************
Local-Fix:
Do a QUIESCE TABLESPACES RESET before DROP TABLE.
verfügbare FixPacks:
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 DB2 Version 9.7 Fix Pack 6.
Workaround
keiner bekannt / siehe Local-Fix
Bug-Verfolgung
Vorgänger  : APAR is sysrouted TO one or more of the following: IC84458 
Nachfolger : 
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
09.11.2011
14.12.2012
14.12.2012
Problem behoben ab folgender Versionen (IBM BugInfos)
9.7.FP6
Problem behoben lt. FixList in der Version
9.7.0.6 FixList