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

DB2CFIMP <FILENAME> UPDATES DBM CFG PARAMETERS INCORRECTLY WHEN
VALUES SET TO AUTOMATIC; CLIENT CONNECTIONS WILL HANG

Produkt:
DB2 CONNECT / DB2CONNCT / 950 - DB2
Problembeschreibung:
If original db2 get dbm cfg shows 
 
MAX_CONNECTIONS = 100 AUTOMATIC 
MAX_COORDAGENTS = 200 AUTOMATIC 
NUM_POOLAGENTS = 200 AUTOMATIC 
 
when you export the configuration using 
 
db2cfexp filename backup 
the filename will contain: 
 
MAX_CONNECTIONS=AUTOMATIC 
MAX_COORDAGENTS=AUTOMATIC 
NUM_POOLAGENTS=AUTOMATIC 
 
When this file is then used with 
db2cfimp filename 
 
The result in the dbm cfg shows: 
MAX_CONNECTIONS = 0 AUTOMATIC 
MAX_COORDAGENTS = 0 AUTOMATIC 
NUM_POOLAGENTS = 1 AUTOMATIC 
 
Any connections to the database will hang waiting for an agent.
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* db2cfimp <filename> updates dbm cfg parameters incorrectly   * 
* when original values set to AUTOMATIC; client connections    * 
* will hang                                                    * 
* If original db2 get dbm cfg shows                            * 
*                                                              * 
* MAX_CONNECTIONS = 100 AUTOMATIC                              * 
* MAX_COORDAGENTS = 200 AUTOMATIC                              * 
* NUM_POOLAGENTS = 200 AUTOMATIC                               * 
*                                                              * 
* when you export the configuration using                      * 
*                                                              * 
* db2cfexp filename backup                                     * 
* the filename will contain:                                   * 
*                                                              * 
* MAX_CONNECTIONS=AUTOMATIC                                    * 
* MAX_COORDAGENTS=AUTOMATIC                                    * 
* NUM_POOLAGENTS=AUTOMATIC                                     * 
*                                                              * 
* When this file is then used with                             * 
* db2cfimp filename                                            * 
*                                                              * 
* The result in the dbm cfg shows:                             * 
* MAX_CONNECTIONS = 0 AUTOMATIC                                * 
* MAX_COORDAGENTS = 0 AUTOMATIC                                * 
* NUM_POOLAGENTS = 1 AUTOMATIC                                 * 
*                                                              * 
* Any connections to the database will hang waiting for an     * 
* agent.                                                       * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 UDB Version 9.5 Fix Pack 9                    * 
****************************************************************
Local-Fix:
Manually update the dbm cfg parameters back to the original 
values by running 
db2 update dbm cfg using num_poolagents -1 max_coordagents -1 
max_connections -1
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
Problem was first fixed in DB2 UDB Version 9.5 Fix Pack 9
Workaround
Update the MAX_CONNECTIONS, MAX_COORDAGENTS and NUM_POOLAGENTS 
manually via the update dbm cfg command
Bug-Verfolgung
Vorgänger  : APAR is sysrouted TO one or more of the following: IC79907 IC84150 
Nachfolger : 
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
25.05.2011
04.04.2012
04.04.2012
Problem behoben ab folgender Versionen (IBM BugInfos)
9.5.FP9
Problem behoben lt. FixList in der Version
9.5.0.9 FixList