DB2 - Problem description
Problem IC80671 | Status: Closed |
WRONG PREFETCH SIZE CALCULATION FOR AUTOMATIC STORAGE | |
product: | |
DB2 FOR LUW / DB2FORLUW / 950 - DB2 | |
Problem description: | |
In case you use PREFETCHSIZE AUTOMATIC with AUTOMATIC STORAGE, there could be a miscalculation of the PREFETCH SIZE used. The intention of this APAR is to fix the the prefetch size calculation. However, there is a more subtle and complex issue here. In our design, each table has a packed descriptor and the packed descriptor contains a bunch of information including the tablespace's prefetch size. When the tablespace's prefetch size changes, we need to update the packed descriptors of ALL the tables and indexes within this tablespace. This is a complex issue because the packed descriptors are stored in the system catalog. This is how it's done in the ALTER TABLESPACE PREFETCHSIZE codepath. However, the automatic storage codepath does not have the infrastructure to do all these. Fixing this is too risky to be done in an APAR fix. There is a simple workaround available: 1. ALTER TABLESPACE PREFETCHSIZE <some number> 2. ALTER TABLESPACE PREFETCHSIZE AUTOMATIC " | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * All * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description. * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 Version 9.5 Fix Pack 10. * **************************************************************** | |
Local Fix: | |
1. ALTER TABLESPACE PREFETCHSIZE <some number> 2. ALTER TABLESPACE PREFETCHSIZE AUTOMATIC " | |
Solution | |
First fixed in DB2 Version 9.5 Fix Pack 10. | |
Workaround | |
not known / see Local fix | |
BUG-Tracking | |
forerunner : APAR is sysrouted TO one or more of the following: IC80673 follow-up : | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 05.01.2012 28.08.2012 28.08.2012 |
Problem solved at the following versions (IBM BugInfos) | |
9.5.FP10 | |
Problem solved according to the fixlist(s) of the following version(s) | |
9.5.0.10 |