home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Neueste VersionenFixList
11.1.0.7 FixList
10.5.0.9 FixList
10.1.0.6 FixList
9.8.0.5 FixList
9.7.0.11 FixList
9.5.0.10 FixList
9.1.0.12 FixList
Haben Sie Probleme? - Kontaktieren Sie uns.
Kostenlos registrieren anmeldung-x26
Kontaktformular kontakt-x26

DB2 - Problembeschreibung

Problem IC63390 Status: Geschlossen

CONCENTRATOR CAUSES PERFORMANCE HIT FOR READ LOG AGENT DUE TO NEW LOG
RETRIEVAL NECESSARY WHEN AGENT SWITCHES OUT.

Produkt:
DB2 FOR LUW / DB2FORLUW / 950 - DB2
Problembeschreibung:
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-Zusammenfassung:
**************************************************************** 
* 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:
verfügbare FixPacks:
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

Lösung
Log file will not be deleted and re-retrieved when the 
connection is terminated when using DB2 UDB  V9.5.6.
Workaround
keiner bekannt / siehe Local-Fix
Bug-Verfolgung
Vorgänger  : APAR is sysrouted TO one or more of the following: IC68611 IC68612 
Nachfolger : 
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
23.09.2009
22.06.2010
06.07.2010
Problem behoben ab folgender Versionen (IBM BugInfos)
9.5.6
Problem behoben lt. FixList in der Version