|
Problem IC84150
|
Status: Closed |
DB2CFIMP <FILENAME> UPDATES DBM CFG PARAMETERS INCORRECTLY WHEN VALUES SET TO AUTOMATIC; CLIENT CONNECTIONS WILL HANG |
| product: |
DB2 CONNECT / DB2CONNCT / A10 - DB2 |
| Problem description: |
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 Summary: |
****************************************************************
* 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. *
* *
* Problem Description: (describe the problem including *
* external symptoms as seen by the customer) *
* Problem wa *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 UDB Version 10 Fix Pack 1. *
**************************************************************** |
| 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 |
| available fix packs: |
DB2 Version 10.1 Fix Pack 1 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows
|
| Solution |
Problem was first fixed in DB2 UDB Version 10 Fix Pack 1 |
| Workaround |
Update the MAX_CONNECTIONS, MAX_COORDAGENTS and NUM_POOLAGENTS
manually via the update dbm cfg command |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 12.06.2012
10.12.2012
10.12.2012 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.1.0.1
|
 |
| 10.5.0.1
|
|
