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

MAX_COORDAGENTS CANNOT BE SET TO 0 VALUE

Produkt:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problembeschreibung:
When we activate the database, the DB2 system need to start up 
couples  of system applications. 
 
 If MAX_COORDAGENTS is set to 0,the database will not able to 
activate  and it will hung. The code 
 
 that automatically  adjust the MAX_COORDAGENTS will not able to 
execute  because the database 
 
 system  have not come  up and running. 
 
 
 
 Hence  we  should not allow  this MAX_COORDAGENTS to set to 0 
and it  should throw an error in 
 
 case  it is tried to be set to  0 via some user or any defect 
inadvertently. 
 
 However due to  APAR   IC97753   is  inadvertently set to 
0,which  made the DB unusable and hung state.
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL DB2 USERS                                                * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* If MAX_COORDAGENTS is set to 0,the database will not able to * 
* activate  and it will hung.                                  * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Update  MAX_COORDAGENTS  vallue to any non zero value.       * 
****************************************************************
Local-Fix:
db2  update  dbm  cfg  using  MAX_CORDAGENTS  to any non zero 
value.
Lösung
Workaround
Update  MAX_COORDAGENTS  vallue to any non zero value
Kommentar
Will be fixed in future releases
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
18.04.2014
18.11.2014
18.11.2014
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version
9.7.0.10 FixList