DB2 FOR LUW / DB2FORLUW / A50 - DB2

When a tablespace is created in flight which is dependent on a 
bufferpool, a drop command is able to successfully drop that 
bufferpool. This leaves the tablespace dependent on a 
non-existent bufferpool. 
 
The following queries will demonstrate the incorrect behaviour: 
 
Session 1: 
 
Create a bufferpool: 
 
$ db2 +c create bufferpool bp1 
DB20000I  The SQL command completed successfully. 
 
Session 2: 
 
Create a tablespace, dependent on the bufferpool created in 
session 1, this statement will wait: 
 
$ db2 +c create tablespace tbsp1 bufferpool bp1 
 
Session 3: 
 
Drop the bufferpool created in session 1, this statement will 
wait. 
 
$ db2 drop bufferpool bp1 
 
Session 1: 
 
Commit changes: 
 
$db2 commit 
 
 
Session # 1 
-------------- 
$ db2 "select bpname,bufferpoolid from syscat.bufferpools" 
 
BPNAME 
BUFFERPOOLID 
---------------------------------------------------------------- 
---------------------------------------------------------------- 
IBMDEFAULTBP 
1 
 
  1 record(s) selected. 
 
$ db2 "select tbspace,bufferpoolid from syscat.tablespaces where 
tbspace='TBSP1'" 
 
TBSPACE 
BUFFERPOOLID 
---------------------------------------------------------------- 
---------------------------------------------------------------- 
TBSP1 
2 
 
  1 record(s) selected. 
 
Sessions 2 and 3 will then report successful completion. In this 
case, session 3 demonstrates 
incorrect behaviour, as it should not be able to drop a 
bufferpool when a dependent tablespace 
creation is in-flight.

**************************************************************** 
* USERS AFFECTED:                                              * 
* All DB2 Server systems on all Linux, Unix and Windows for    * 
* all available versions                                       * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to latest fixpack                                    * 
****************************************************************

Drop the tablespace causing the problem.

The complete fix for this problem first appears in DB2 Version 
10.5 Fix Pack 8 and all the subsequent Fix Packs.

not known / see Local fix

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

12.05.2016
23.11.2016
23.11.2016