DB2 - Problem description
Problem IT37559 | Status: Closed |
CONFIGURATION ADVISOR SHOWS INADEQUATE RECOMMANDED VALUE FOR NUM_IOSERVERS/NUM_IOCLEANERS/DFT_PREFETCH_SZ | |
product: | |
DB2 FOR LUW / DB2FORLUW / B10 - DB2 | |
Problem description: | |
The Configuration Advisor may show AUTOMATIC(n) as Recommended Value for NUM_IOSERVERS/NUM_IOCLEANERS/DFT_PREFETCH_SZ as follows, but they should be AUTOMATIC, not AUTOMATIC(n). $ db2 autoconfigure apply none Current and Recommended Values for Database Configuration Description Parameter Current Value Recommended Value ---------------------------------------------------------------- --------------------------------- ... Default prefetch size (pages) (DFT_PREFETCH_SZ) = AUTOMATIC(32) AUTOMATIC(32) Number of asynchronous page cleaners (NUM_IOCLEANERS) = AUTOMATIC(4) AUTOMATIC(5) Number of I/O servers (NUM_IOSERVERS) = AUTOMATIC(16) AUTOMATIC(13) | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * Users using Configuration Advisor * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * pgrade to Db2 11.1m4fp5 or higher * **************************************************************** | |
Local Fix: | |
Ignore AUTOMATIC(n) but set AUTOMATIC. | |
Solution | |
Workaround | |
**************************************************************** * USERS AFFECTED: * * Users using Configuration Advisor * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * pgrade to Db2 11.1m4fp5 or higher * **************************************************************** | |
Comment | |
First fixed in Db2 11.1m4fp5 | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 09.07.2021 09.07.2021 09.07.2021 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) |