Latest versionsfixlist
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
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IC79701 Status: Closed

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

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
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 Summary:
**************************************************************** 
* 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.
available fix packs:
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

Solution
First fixed in DB2 Version 9.7 Fix Pack 6.
Workaround
not known / see Local fix
BUG-Tracking
forerunner  : APAR is sysrouted TO one or more of the following: IC84458 
follow-up : 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
09.11.2011
14.12.2012
14.12.2012
Problem solved at the following versions (IBM BugInfos)
9.7.FP6
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.6 FixList
This site uses cookies to make it easier for us to provide you with our services. By using our site you agree to the use of cookies.