home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
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 IC63318 Status: Closed

QUIESCE RESET NOT RESETTING THE INDEX TABLESPACE STATE FROM
QUIESCE:EXCLUSIVE TO NORMAL, WHEN DROP INDEX IS DONE.

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
The QUIESCE RESET command is not resetting the index tablespace 
state from QUIESCE:Exclusive to NORMAL, when drop index is done. 
The problem is that since we are allowing drop index to happen 
when the index tablespace was still quiesce under a certain 
object, this prevents the quiesce command to reset the 
tablespace state since the index object no longer exist.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All users                                                    * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* The QUIESCE RESET command is not resetting the index         * 
* tablespace state from QUIESCE:Exclusive to NORMAL, when drop * 
* index is done.  The problem is that since we are allowing    * 
* drop index to happen when the index tablespace was still     * 
* quiesce under a certain object, this prevents the quiesce    * 
* command to reset the tablespace state since the index object * 
* no longer exist.  The user will then get a "SQL0290N Table   * 
* space access is not allowed." error when trying to use the   * 
* tablespace.                                                  * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 UDB Version 9.7 fix pack 2.                   * 
****************************************************************
Local Fix:
available fix packs:
DB2 Version 9.7 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
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 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows

Solution
The problem was first fixed in DB2 UDB Version 9.7 fix pack 2.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
22.09.2009
30.06.2010
30.06.2010
Problem solved at the following versions (IBM BugInfos)
9.7.FP2
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.2 FixList