DB2 - Problembeschreibung
Problem IT03166 | Status: Geschlossen |
'AUTOCONFIGURE' COMMAND DOES NOT DISPLAY KEYWORD 'AUTOMATIC' FOR SELF TUNED AUTOMATIC PARAMETERS. | |
Produkt: | |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 | |
Problembeschreibung: | |
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-Zusammenfassung: | |
**************************************************************** * 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. | |
Lösung | |
Problem is first fixed in DB2 v10.5 FP5. | |
Workaround | |
keiner bekannt / siehe Local-Fix | |
Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 14.07.2014 13.03.2015 13.03.2015 |
Problem behoben ab folgender Versionen (IBM BugInfos) | |
Problem behoben lt. FixList in der Version | |
10.5.0.5 |