|
Problem IC63416
|
Status: Closed |
THE SETTING OF MAXCAGENTS CAN BE INVALIDATED BY FORCING APPLICATIONS THAT ARE WAITING TO EXECUTE. |
| product: |
DB2 FOR LUW / DB2FORLUW / 910 - DB2 |
| Problem description: |
The number of agents concurrently executing a database
transaction can be limited with the MAXCAGENTS database manager
configuration parameter. Internally, the MAXCAGENTS value is
represented by agent tokens where the number of tokens limits
the number of concurrent agents executing a transaction. If the
number of concurrently executing agents reaches the value of
MAXCAGENTS, then other agents will wait until an agent token is
freed by a active agent.
In the case that an agent waiting for a free token is forced,
the number of agent tokens will be incremented incorrectly.
As the result, the number of concurrently executing agents could
be higher than the value of MAXCAGENTS.
This effect will continue until the DB2 instance is recycled. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* Any user that has set MAXCAGENTS to a positive value to *
* limit the number of concurrently executing agents. *
****************************************************************
* PROBLEM DESCRIPTION: *
* If the database manager configuration parameter MAXCAGENTS *
* is set to a positive value and applications waiting to *
* execute are forced then the number of concurrently executing *
* agents could be higher than the value of MAXCAGENTS. *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 V9.1 FP9 or higher *
**************************************************************** |
| Local Fix: |
Not available |
| available fix packs: |
DB2 Version 9.1 Fix Pack 9 for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 10 for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 11 for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 12 for Linux, UNIX and Windows
|
| Solution |
The fix will correct the internal accounting of concurrently
executing agents so that the limit set by MAXCAGENTS is
respected even if applications are forced. |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 25.09.2009
28.04.2010
28.04.2010 |
| Problem solved at the following versions (IBM BugInfos) |
9.1.FP9
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.1.0.9
|
 |
