DB2 FOR LUW / DB2FORLUW / 910 - DB2

The problem occurs when using the QUIESCE TABLESPACES FOR TABLE 
command to quiesce a tablespace that has already been quiesced 
for a different table using a compatible mode.  Once in the 
state the "QUIESCE TABLESPACES FOR TABLE <TABLE_NAME> RESET", if 
run in a certain order, may return successfully without actually 
resetting the tablespace state.

**************************************************************** 
* USERS AFFECTED:                                              * 
* All users.                                                   * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* The problem occurs when using the QUIESCE TABLESPACES FOR    * 
* TABLE command to quiesce a tablespace that has already been  * 
* quiesced for a different table using a compatible mode.      * 
* Once in the state the "QUIESCE TABLESPACES FOR TABLE         * 
* <TABLE_NAME> RESET", if run in a certain order, may return   * 
* successfully without actually resetting the tablespace       * 
* state.                                                       * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 9.1.0.11.                                     * 
****************************************************************

1.  Issue the "GET SNAPSHOT FOR TABLESPACES ON <databaseName>" 
command and to determine the tablespace and object IDs of the 
tables for which the tablespace is quiesced along with the 
authorization ID used to quiesce the tablespace. 
 
Example output from "GET SNAPSHOT FOR TABLESPACES ON 
<databaseName>" 
 
... 
Tablespace name                            = TS1 
  Tablespace ID                            = 3 
  Tablespace Type                          = Database managed 
space 
  ... 
  Tablespace State                        = 0x'00000001' 
  Detailed explanation: 
    Quiesced: SHARE 
  ... 
  Number of quiescers                      = 2 
 
  Quiescer authorization ID                = ZTOTH 
      Quiescer agent ID                    = 7 
      Quiescer tablespace ID              = 3 
      Quiescer object ID                  = 4 
      Quiesce state                        = 1 
 
  Quiescer authorization ID                = ZTOTH 
      Quiescer agent ID                    = 7 
      Quiescer tablespace ID              = 3 
      Quiescer object ID                  = 5 
      Quiesce state                        = 1 
... 
 
 
2.  Query the SysCat.Tables catalogue table to determine the 
table names from the tablespace and object IDs. 
Examples: 
SELECT TabSchema,TabName FROM SysCat.Tables WHERE TbSpaceID=3 
AND TableID=4 
and 
SELECT TabSchema,TabName FROM SysCat.Tables WHERE TbSpaceID=3 
AND TableID=5 
Result:  The tables are ZTOTH.T1 and ZTOTH.T2. 
 
3.  Using the authorization ID in the "GET SNAPSHOT FOR 
TABLESPACES ON <databaseName>" output, connect to the database 
and issue "QUIESCE TABLESPACES FOR TABLE <TableName> RESET" for 
each of the tables. 
 
4.  Due to the bug this APAR is fixing, at least one of the 
"QUIESCE TABLESPACES FOR TABLE <TableName> RESET" will work, but 
possibly not all of them on the first try, so repeat steps 1 and 
3 until the tablespace is no longer quiesced, or simply repeat 
step 3 X times where X is the number of quiescers displayed in 
the "GET SNAPSHOT FOR TABLESPACES ON <databaseName>" output.

DB2 Version 9.1 Fix Pack 11  for Linux, UNIX and Windows
 DB2 Version 9.1 Fix Pack 12  for Linux, UNIX and Windows
 

The problem will be fixed in DB2 9.1.0.11

keiner bekannt / siehe Local-Fix

Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:

25.01.2011
20.12.2011
20.12.2011

9.1.0.11