DB2 FOR LUW / DB2FORLUW / 970 - DB2

After dropping a tablespace (or tablespaces), and dropping the 
underlying bufferpool, creating a new bufferpool will cause the 
same statistics for the old bufferpool to appear for the new 
bufferpool.  This can be reset with deactivation and activation 
of the database.  The problem is the bufferpool ID gets reused 
by DB2.  Here is a brief example: 
 
create bufferpool bps size 2000 
DB20000I  The SQL command completed successfully. 
 
create tablespace tbs bufferpool bps 
DB20000I  The SQL command completed successfully. 
 
create table tt(c1 char(200)) in tbs 
DB20000I  The SQL command completed successfully. 
 
insert into tt values '1', '2', '3', '4', '5', '6' 
DB20000I  The SQL command completed successfully. 
 
select substr(bp_name, 1, 25) as bpname, pool_data_l_reads, 
pool_data_p_reads from sysibmadm.snapbp 
 
BPNAME                    POOL_DATA_L_READS    POOL_DATA_P_READS 
------------------------- -------------------- 
-------------------- 
BPS                                         56 
 1 
 
drop tablespace tbs 
DB20000I  The SQL command completed successfully. 
 
drop bufferpool bps 
DB20000I  The SQL command completed successfully. 
 
create bufferpool bps_2 size 3000 
DB20000I  The SQL command completed successfully. 
 
select substr(bp_name, 1, 25) as bpname, pool_data_l_reads, 
pool_data_p_reads from sysibmadm.snapbp 
 
BPNAME                    POOL_DATA_L_READS    POOL_DATA_P_READS 
------------------------- -------------------- 
-------------------- 
BPS_2                                       56 
 1

**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 9.7 Fix Pack 6                        * 
****************************************************************

Deactivate and activate the database.

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
 

First fixed in DB2 Version 9.7 Fix Pack 6

keiner bekannt / siehe Local-Fix

Vorgänger  : APAR is sysrouted TO one or more of the following: IC78773 
Nachfolger : 

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

10.09.2011
10.12.2012
10.12.2012

9.7.FP6