|
Problem IC64547
|
Status: Closed |
ERROR IN SERVICE CLASS AGENT PRIORITY AND OUTBOUND CORRELATOR CONFIGURATION |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
Setting of service class agent priority and outbound correlator
is designed to be mutually exclusive. The user either uses
agent priority to control the CPU usage of a service class or
they use OS WLM (AIX WLM or Linux WLM) using outbound correlator
tag.
A bug was discovered that allows a user to set the outbound
correlator for a service superclass and set agent priority for
a service subclass. This configuration may lead to problems
withproportioning CPU shares between this service subclass and
other service subclasses under the service superclass. A
change has been made to prevent this setup in the
CREATE/ALTER SERVICE CLASS DDL. This problem was introduced in
V9.5.
What happens if we don't fix this problem?
If a user creates the scenario described
above, the CPU usage behaviour may be
unpredictable. The workaround is
for the user to fix their service class attributes so that
they either use agent priority or outbound correlator with OS
WLM.
The fix will stop this scenario from ever being able to happen.
The fix is a low risk fix. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* WLM users using service class agent priority and/or OS WLM *
* integration *
****************************************************************
* PROBLEM DESCRIPTION: *
* The service class agent priority attribute and outbound *
* correlator attribute are designed to be mutually exclusive. *
* The user either specifies the agent priority to control the *
* CPU usage of a service class or they specify the outbound *
* correlator to use OS WLM. A bug was discovered that allows *
* a user to set the outbound correlator for a service *
* superclass and the agent priority for a service subclass. *
* This configuration may lead to problems with proportioning *
* CPU shares between this service subclass and other service *
* subclasses under the service superclass. A change has been *
* made to prevent this setup in the CREATE/ALTER SERVICECLASS *
* DDL. *
****************************************************************
* RECOMMENDATION: *
* Update service class configuration to ensure there are no *
* cases with *
* - agent priority set at the service superclass and outbound *
* correlator set at one of the service superclass' subclasses *
* *
* - outbound correlator set at the service superclass and *
* agent priority set at one of the service superclass' *
* subclasses *
**************************************************************** |
| Local Fix: |
Update service class configuration to ensure there are no cases
with
- agent priority set at the service superclass and outbound
correlator set at one of the service superclass' subclasses
- outbound correlator set at the service superclass and agent
priority set at one of the service superclass' subclasses |
| available fix packs: |
DB2 Version 9.7 Fix Pack 1 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows
|
| Solution |
The fix is to prevent a user from setting agent priority for a
service superclass and outbound correlator for one of its
service subclasses (and vice versa). The fix will be available
in V9.7 FP1. |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 13.11.2009
27.04.2010
27.04.2010 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.FP1
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.1
|
 |
