DB2 - Problem description
Problem IC64337 | Status: Closed |
MON_LW_THRESH CAN'T BE SET LARGER THAN 5000000 | |
product: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
Problem description: | |
Setting the monitoring lock wait threshold configuration parameter to a value greater than 5000000 microseconds results in the following error: db2 update db cfg using mon_lw_thresh using 6000000 SQL5130N The value specified for the configuration parameter "mon_lw_thresh" is not in the valid range of "1000" to "5000000". The documented upper limit for this configuration parameter is MAX_INT. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * any * **************************************************************** * PROBLEM DESCRIPTION: * * users wont be able to set MON_LW_THRESH larger than 5000000 * **************************************************************** * RECOMMENDATION: * * upgrade to latest fixpac * **************************************************************** | |
Local Fix: | |
available fix packs: | |
DB2 Version 9.7 Fix Pack 1 for Linux, UNIX, and Windows | |
Solution | |
MON_LW_THRESH can be set larger than 5000000 | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 04.11.2009 29.04.2010 29.04.2010 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) | |
9.7.0.1 |