DB2 FOR LUW / DB2FORLUW / A10 - DB2

In pureScale environment, there is an error in the way the 
database quiesce state is re-initialized after the instance 
is recycled. 
 
The issue happens with an instance level quiesce, where all 
databases are by default quiesced. When the instance is 
quiesced at the instance level, the databases are NOT 
marked as quiesced at the database level. In a 
non-pureScale env, when the instance is brought down with 
db2stop, the quiesce state is wiped out; i.e instance is 
automatically unquiesced. 
 
However, the behavior has changed in pureScale such that 
even on an instance recycle, the instance is still quiesced. 
There is no automatic unquiesce. 
 
The bug happens to be when we try to connect to the 
database and bring up the db for the first time. We call 
a function that attempts to read the database quiesce 
lock file for the quiesce state. In this case, this file does 
not exist because it is only created when the database is 
explicitly quiesced with the QUIESCE DATABASE command, 
not the QUIESCE INSTANCE command. If this file doesn't 
exist, the instance level quiesce state is used. This will 
return INST_QUIESCED. Later this quiesce state is used 
to mark the database at the database level, which is 
incorrect. This is the reason why even when the instance 
is later unquiesced, the db is still showing as quiesced. 
 
The database level quiesce state should not be set to 
quiesced since this is an instance level quiesce and not 
an explicit database level qiuesce. The database level 
quiesce state should only be set when the database is 
explicitly quiesced via QUIESCE DATABASE command.

**************************************************************** 
* USERS AFFECTED:                                              * 
* pureScale only                                               * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 version 10 fixpack 4.                         * 
****************************************************************

Recycle the instance to remove the qiuesce state of the 
database.

DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
 DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows
 

Fix contained in db2 version 10 fixpack 4.

not known / see Local fix

forerunner  : APAR is sysrouted TO one or more of the following: IC99933 
follow-up : 

Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :

07.03.2014
02.06.2014
02.06.2014