|
Problem IC71320
|
Status: Closed |
USING THE DB2CFIMP TO IMPORT CONNECTIVITY CONFIGURATION PARAMETE RS CAUSES AUTOMATIC VALUES TO BE RESET TO MINIMUM VALUES. |
| product: |
DB2 FOR LUW / DB2FORLUW / 910 - DB2 |
| Problem description: |
When the db2cfexp is used to export connectivity configuration
information to an export profile, automatic value are exported
as "AUTOMATIC" in dbm.cfg file.
However when these are imported using the "db2cfimp" command,
the values which were exported as "AUTOMATIC" are imported with
minimum value possible.
Test case :
------------------------
db2 reset dbm cfg
db2 get dbm cfg(Before exporting) :
==>
Agent pool size (NUM_POOLAGENTS) =
AUTOMATIC(100)
Initial number of agents in pool (NUM_INITAGENTS) = 0
Max number of coordinating agents (MAX_COORDAGENTS) =
AUTOMATIC(200)
Max number of client connections (MAX_CONNECTIONS) =
AUTOMATIC(MAX_COORDAGENTS)
db2cfexp dbm.cfg backup
db2start
db2cfimp dbm.cfg(After importing) :
==> automatic parameters have been changed
Size of instance shared memory (4KB) (INSTANCE_MEMORY) =
AUTOMATIC(1)
Priority of agents (AGENTPRI) = SYSTEM
Agent pool size (NUM_POOLAGENTS) =
AUTOMATIC(0)
Initial number of agents in pool (NUM_INITAGENTS) = 0
Max number of coordinating agents (MAX_COORDAGENTS) =
AUTOMATIC(0)
Max number of client connections (MAX_CONNECTIONS) =
AUTOMATIC(1)
After this if you try :
db2stop
db2start
db2 connect to dbname ==> will result in hang. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* All users on DB2 V 9.1 FixPack 9 and below *
****************************************************************
* PROBLEM DESCRIPTION: *
* When the db2cfexp is used to export connectivity *
* configuration *
* information to an export profile, automatic value are *
* exported *
* as "AUTOMATIC" in dbm.cfg file. *
* *
* However when these are imported using the "db2cfimp" *
* command, *
* the values which were exported as "AUTOMATIC" are imported *
* with *
* minimum value possible. *
* *
* *
* *
* Test case : *
* *
* *
* *
* ------------------------ *
* *
* *
* *
* db2 reset dbm cfg *
* *
* *
* *
* *
* *
* *
* *
* db2 get dbm cfg(Before exporting) : *
* *
* ==> *
* *
* *
* *
* Agent pool size (NUM_POOLAGENTS) = *
* *
* AUTOMATIC(100) *
* *
* Initial number of agents in pool (NUM_INITAGENTS) = 0 *
* *
* *
* *
* Max number of coordinating agents (MAX_COORDAGENTS) = *
* *
* AUTOMATIC(200) *
* *
* Max number of client connections (MAX_CONNECTIONS) = *
* *
* AUTOMATIC(MAX_COORDAGENTS) *
* *
* *
* *
* db2cfexp dbm.cfg backup *
* *
* *
* *
* db2start *
* *
* *
* *
* db2cfimp dbm.cfg(After importing) : *
* *
* *
* *
* ==> automatic parameters have been changed *
* *
* *
* *
* *
* *
* *
* *
* Size of instance shared memory (4KB) (INSTANCE_MEMORY) = *
* *
* AUTOMATIC(1) *
* *
* *
* *
* Priority of agents (AGENTPRI) = *
* SYSTEM *
* Agent pool size (NUM_POOLAGENTS) = *
* *
* AUTOMATIC(0) *
* *
* Initial number of agents in pool (NUM_INITAGENTS) = 0 *
* *
* *
* *
* Max number of coordinating agents (MAX_COORDAGENTS) = *
* *
* AUTOMATIC(0) *
* *
* Max number of client connections (MAX_CONNECTIONS) = *
* *
* AUTOMATIC(1) *
* *
* *
* *
* After this if you try : *
* *
* *
* *
* db2stop *
* *
* *
* *
* db2start *
* *
* *
* *
* *
* *
* db2 connect to dbname ==> will result in hang. *
****************************************************************
* RECOMMENDATION: *
* Upgarde to DB2 V9.1 FixPack 10 *
**************************************************************** |
| Local Fix: |
Avoid using "AUTOMATIC" as a value in such cases.
or
Change the dbm CFG manually after they are imported. |
| Solution |
Problem first fixed in DB2 V9.1 FixPack 10 |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 20.09.2010
17.06.2011
17.06.2011 |
| Problem solved at the following versions (IBM BugInfos) |
9.1.FP10
|
| Problem solved according to the fixlist(s) of the following version(s) |
