|
Problem IC63390
|
Status: Closed |
CONCENTRATOR CAUSES PERFORMANCE HIT FOR READ LOG AGENT DUE TO NEW LOG RETRIEVAL NECESSARY WHEN AGENT SWITCHES OUT. |
| product: |
DB2 FOR LUW / DB2FORLUW / 950 - DB2 |
| Problem description: |
When DB2 needs to re-use an agent for a different connection, it
takes away the agent from an existing connection (in this case
the readLog agent). When we take away the agent and re-use it
for another connection, we are destorying the information about
which log file this agent was looking at (at this point we also
delete the retrieved extent). When the readLog connection is
active again, it is assigned a new agent, and since the previous
agent informtion was destroyed, a new log retrieve needs to be
done since we do not remember that we are using the same log
file as before. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* User of log read API and connection concentrator *
****************************************************************
* PROBLEM DESCRIPTION: *
* When DB2 needs to re-use an agent for a different *
* connection, *
* it takes away the agent from an existing connection (in *
* this case the readLog agent). When we take away the agent *
* and *
* re-use it for another connection, we are destroying the *
* information about which log file this agent was looking at *
* (at *
* this point we also delete the retrieved extent). When the *
* readLog connection is active again, it is assigned a new *
* agent, and since the previous agent information was *
* destroyed, *
* a new log retrieve needs to be done since we do not remember *
* that we are using the same logfile as before. *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 UDB version 9.5.6 *
**************************************************************** |
| Local Fix: |
|
| available fix packs: |
DB2 Version 9.5 Fix Pack 6a for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 10 for Linux, UNIX, and Windows
|
| Solution |
Log file will not be deleted and re-retrieved when the
connection is terminated when using DB2 UDB V9.5.6. |
| Workaround |
not known / see Local fix |
| BUG-Tracking |
forerunner : APAR is sysrouted TO one or more of the following: IC68611 IC68612
follow-up : |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 23.09.2009
22.06.2010
06.07.2010 |
| Problem solved at the following versions (IBM BugInfos) |
9.5.6
|
| Problem solved according to the fixlist(s) of the following version(s) |
