|
Problem IT03166
|
Status: Closed |
'AUTOCONFIGURE' COMMAND DOES NOT DISPLAY KEYWORD 'AUTOMATIC' FOR SELF TUNED AUTOMATIC PARAMETERS. |
| product: |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 |
| Problem description: |
The AUTOCONFIGURE command for certain parameters (DBHEAP,
NUM_IOCLEANERS, NUM_IOSERVERS) is misleading regarding AUTOMATIC
settings.
For eg. If DBHEAP is set as following in the db cfg:
Database heap (4KB) (DBHEAP) = AUTOMATIC(2344)
AUTOMATIC(2344)
then the AUTOCONFIGURE output shows the following:
Description Parameter
Current Value Recommended Value
----------------------------------------------------------------
---------------------------------
Database heap (4KB) (DBHEAP) = 2344
7421
Currently it is not indicating if you need to set it as
AUTOMATIC with 7421 as starting value.
This behavior is observed only when getting recommendations only
from AUTOCONFIGURE command. If you select to apply the
recommendations by 'AUTOCONFIGURE', db2 applies the parameters
values correctly. It will apply AUTOMOTIC setting as expected. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* All users using DB2 prior v10.5 FP5. *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Please upgrade DB2 to v10.5 FP5. *
**************************************************************** |
| Local Fix: |
Please confirm the initial AUTOMATIC setting from 'DB CFG' or
'DBM CFG' before updating parameters suggested by
'AUTOCONFIGURE' command. If parameters is set to AUTOMATIC, then
keep the same settings with starting value recommended by
'AUTOCONFIGURE' command. |
| Solution |
Problem is first fixed in DB2 v10.5 FP5. |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 14.07.2014
13.03.2015
13.03.2015 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.5.0.5
|
 |
