DB2 - Problem description
Problem IC66873 | Status: Closed |
CONTROL CENTER UNRESPONSIVE WHEN UPDATING text based DBM CFG parameter | |
product: | |
DB2 FOR LUW / DB2FORLUW / 980 - DB2 | |
Problem description: | |
The Control Center in DB2 v9.7 has a problem updating DBM CFG parameters. Specifically the ones that take a text string, like SVCENAME. You can update SVCENAME to a number, but not to a name. After updating SVCENAME, and pressing 'OK', nothing happens. The 'Change DBM Configuration Parameter' window remains until you click 'Cancel'. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * Users of the DB2 v9.7 Control Center * **************************************************************** * PROBLEM DESCRIPTION: * * The Control Center can be used to update the Database * * Manager Configuration by right-clicking on the Instance and * * select 'Configure Parameters'. If you attempt to update a * * parameter that takes a Text string value, like SVCENAME, * * nothing will happen after you click on 'OK'. You have to * * click on 'Cancel' to proceed, and that means the update will * * not be applied. * * * * This problem only applies to text entries, so in this * * example, you would be able to change SVCENAME to a numerical * * value. * **************************************************************** * RECOMMENDATION: * * None, you must update the Database Manager configuration * * from the CLP using the UPDATE DBM CFG command. * **************************************************************** | |
Local Fix: | |
None. Work-around is to manually update the dbm cfg from the CLP | |
available fix packs: | |
DB2 Version 9.8 Fix Pack 3 for Linux, UNIX, and Windows | |
Solution | |
Problem first fixed in DB2 v9.7 FP3 | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 04.03.2010 08.11.2012 08.11.2012 |
Problem solved at the following versions (IBM BugInfos) | |
9.7.FP3 | |
Problem solved according to the fixlist(s) of the following version(s) | |
9.8.0.3 |