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 IC75552 Status: Geschlossen

Hung in AppStopUsing -> ForwardStopRequest due to other coord-ag entnot
cleaning up its associated application value

Produkt:
DB2 FOR LUW / DB2FORLUW / 950 - DB2
Problembeschreibung:
If an application pooled sub-agent was chosen as coord-agent and 
failed prior connecting to db (e.g. can not find the database 
name/alias, or we found a more suitable agent to handle this 
request), it might not disassociate the application completely. 
 
And this could cause the later code path in 
AppStopUsing->ForwardStopRequest to hung, since coord-agent that 
goes back to pool should not have associated application value 
set. 
The following is the scenario: 
 
1.) if agent-X was started as sub-agent 
2.) did his work as sub-agent and finish 
3.) went back to its associated application sub-agent pool 
4.) moments later agent-X was chosen to serve a new connection 
5.) became a coord-agent 
6.) and failed prior connecting to db 
     e.g. can not find the database name/alias, 
            or we found a more suitable agent to handle 
            this request) 
 
7.) and then coord-agent X went back to a pool with its 
associated application value set. 
 
 
Note that: coordinator agents do NOT maintain an application 
association when in the pool. Hence the defect on the scenario 
above. 
 
This could cause database related operation 
(backup/quiesce/activate/deactivate/etc) would not return and 
wait forever until agent-X terminate, 
so that would be a potential risk of this problem.
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* If an application pooled sub-agent was chosen as coord-agent * 
* and                                                          * 
* failed prior connecting to db (e.g. can not find the         * 
* database                                                     * 
* name/alias, or we found a more suitable agent to handle this * 
* request), it might not disassociate the application          * 
* completely.                                                  * 
*                                                              * 
* And this could cause the later code path in                  * 
* AppStopUsing->ForwardStopRequest to hung, since coord-agent  * 
* that goes back to pool should not have associated            * 
* application value set.                                       * 
*                                                              * 
* The following is the scenario:                               * 
*                                                              * 
* 1.) if agent-X was started as sub-agent                      * 
* 2.) did his work as sub-agent and finish                     * 
* 3.) went back to its associated application sub-agent pool   * 
* 4.) moments later agent-X was chosen to serve a new          * 
* connection                                                   * 
* 5.) became a coord-agent                                     * 
* 6.) and failed prior connecting to db                        * 
* e.g. can not find the database name/alias,                   * 
* or we found a more suitable agent to handle                  * 
* this request)                                                * 
*                                                              * 
* 7.) and then coord-agent X went back to a pool with its      * 
* associated application value set.                            * 
*                                                              * 
*                                                              * 
* Note that: coordinator agents do NOT maintain an application * 
* association when in the pool. Hence the defect on the        * 
* scenario above.                                              * 
*                                                              * 
*                                                              * 
* This could cause database related operation                  * 
*                                                              * 
* (backup/quiesce/activate/deactivate/etc) would not return    * 
* and                                                          * 
* wait forever until agent-X terminate,                        * 
* so that would be a potential risk of this problem.           * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 v9.5 FP9                                      * 
****************************************************************
Local-Fix:
verfügbare FixPacks:
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
This defect will be fixed in v9.5 FP9
Workaround
keiner bekannt / siehe Local-Fix
Bug-Verfolgung
Vorgänger  : APAR is sysrouted TO one or more of the following: IC75993 
Nachfolger : 
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
04.04.2011
03.05.2011
30.05.2011
Problem behoben ab folgender Versionen (IBM BugInfos)
9.5.FP9
Problem behoben lt. FixList in der Version
9.5.0.9 FixList