DB2 - Problem description
Problem IC71318 | 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 / 950 - 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 of DB2 V9.5 below FixPack 7 * **************************************************************** * PROBLEM DESCRIPTION: * * When the db2cfexp is used to export * * connectivityconfigurationinformation to an export profile, * * automatic value areexportedas "AUTOMATIC" in dbm.cfg * * file.However when these are imported using the * * "db2cfimp"command,the values which were exported as * * "AUTOMATIC" are importedwithminimum value possible.Test case * * :------------------------db2 reset dbm cfgdb2 get dbm * * cfg(Before exporting) :==>Agent pool size * * (NUM_POOLAGENTS) =AUTOMATIC(100)Initial number of agents * * in pool (NUM_INITAGENTS) = 0Max number of coordinating * * agents (MAX_COORDAGENTS) =AUTOMATIC(200)Max number of * * client connections (MAX_CONNECTIONS) * * =AUTOMATIC(MAX_COORDAGENTS)db2cfexp dbm.cfg * * backupdb2startdb2cfimp dbm.cfg(After importing) :==> * * automatic parameters have been changedSize of instance * * shared memory (4KB) (INSTANCE_MEMORY) =AUTOMATIC(1)Priority * * of agents (AGENTPRI) =SYSTEMAgent * * pool size (NUM_POOLAGENTS) * * =AUTOMATIC(0)Initial number of agents in pool * * (NUM_INITAGENTS) = 0Max number of coordinating agents * * (MAX_COORDAGENTS) =AUTOMATIC(0)Max number of client * * connections (MAX_CONNECTIONS) =AUTOMATIC(1)After this * * if you try :db2stopdb2startdb2 connect to dbname ==> will * * result in hang. * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 V9.5 FixPack 7. * **************************************************************** | |
Local Fix: | |
Avoid using "AUTOMATIC" as a value in such cases. or Change the dbm CFG manually after they are imported. | |
available fix packs: | |
DB2 Version 9.5 Fix Pack 7 for Linux, UNIX, and Windows | |
Solution | |
Problem First Fixed in DB2 V9.5 FixPack 7. | |
Workaround | |
not known / see Local fix | |
BUG-Tracking | |
forerunner : APAR is sysrouted TO one or more of the following: IC71320 IC71346 IC71347 follow-up : | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 20.09.2010 21.12.2010 21.12.2010 |
Problem solved at the following versions (IBM BugInfos) | |
9.5.FP7 | |
Problem solved according to the fixlist(s) of the following version(s) | |
9.1.0.7 | |
9.5.0.7 |