|
Problem IC91810
|
Status: Closed |
WLM THREADS LOSING THEIR ELEVATED PRIORITY WHEN USING DB2_RESOURCE_POLICY FILE WITH SCHEDULING_POLICY ELEMENT |
| product: |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 |
| Problem description: |
When you are using a DB2_RESOURCE_POLICY file with the
SCHEDULING_POLICY element you might encounter that the WLM
threads are losing their elevated priority. The thread prioriy
from the policy file overrides the WLM EDU priority.
This behavior is not expected and will impact you if you are
using WLM functionality with DB2. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* All *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 Version 10.1 FixPack 3 *
**************************************************************** |
| Local Fix: |
In order to restore the proper defaults, you can add these two
stanzas to your resource policy configuration.
<EDU_PRIORITY>
<EDU_NAME>db2wlmt</EDU_NAME>
<PRIORITY_VALUE>41</PRIORITY_VALUE>
</EDU_PRIORITY>
<EDU_PRIORITY>
<EDU_NAME>db2wlmtm</EDU_NAME>
<PRIORITY_VALUE>41</PRIORITY_VALUE>
</EDU_PRIORITY> |
| available fix packs: |
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows
|
| Solution |
First fixed in DB2 Version 10.1 FixPack 3 |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 22.04.2013
31.10.2013
31.10.2013 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.1.0.3
|
 |
| 10.1.0.3
|
|
