DB2 - Problem description
Problem IC63638 | Status: Closed |
DB2 Governor does not reset previous setlimit rule by using -1 | |
product: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
Problem description: | |
In the governor configuration file when a previous setlimit setting is reset using -1, the governor still follows the previous setting for cpu, locks and uowtime limts. e.g.: setlimit uowtime 1 action force; setlimit uowtime -1 ; The application is forced off in spite of the fact that "setlimit uowtime -1" was used which should override the previous rule. | |
Problem Summary: | |
DB2 Governor does not reset previous setlimit rule by using -1 | |
Local Fix: | |
available fix packs: | |
DB2 Version 9.7 Fix Pack 1 for Linux, UNIX, and Windows | |
Solution | |
First fixed in DB2 LUW v9.7 Fixpak 1 | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 08.10.2009 29.12.2009 29.12.2009 |
Problem solved at the following versions (IBM BugInfos) | |
9.7. | |
Problem solved according to the fixlist(s) of the following version(s) | |
9.7.0.1 |