| Latest versions | fixlist |
| 11.1.0.7 |
 |
| 10.5.0.9 |
|
| 10.1.0.6 |
|
| 9.8.0.5 |
|
| 9.7.0.11 |
|
| 9.5.0.10 |
|
| 9.1.0.12 |
|
| Have problems? - contact us. | |
| Register for free |
|
| Contact form |
|
DB2 - Problem description
| Problem IC78606 | Status: Closed |
BUFFERPOOL MONITOR STATISTICS MAY BE INCORRECT AFTER DROPPING AND RECREATING BUFFERPOOLS | |
| product: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
| Problem description: | |
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 | |
| Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * ALL * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 Version 9.7 Fix Pack 6 * **************************************************************** | |
| Local Fix: | |
Deactivate and activate the database. | |
| available fix packs: | |
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows | |
| Solution | |
First fixed in DB2 Version 9.7 Fix Pack 6 | |
| Workaround | |
not known / see Local fix | |
| BUG-Tracking | |
forerunner : APAR is sysrouted TO one or more of the following: IC78773 follow-up : | |
| Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 10.09.2011 10.12.2012 10.12.2012 |
| Problem solved at the following versions (IBM BugInfos) | |
9.7.FP6 | |
| Problem solved according to the fixlist(s) of the following version(s) | |
| 9.7.0.6 |
|