DB2 - Problem description
Problem IC68611 | 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 / 970 - 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: * * al using connection concentrator * **************************************************************** * PROBLEM DESCRIPTION: * * Readlog API agent performs slowly. * **************************************************************** * RECOMMENDATION: * * Apply DB2 UDB V9.7 Fixpack 3. * **************************************************************** | |
Local Fix: | |
available fix packs: | |
DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows | |
Solution | |
Apply DB2 UDB V9.7 Fixpack 3. | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 12.05.2010 27.09.2010 27.09.2010 |
Problem solved at the following versions (IBM BugInfos) | |
9.7.FP3 | |
Problem solved according to the fixlist(s) of the following version(s) | |
9.7.0.3 | |
9.7.0.3 |