DB2 - Problembeschreibung
Problem IC94378 | Status: Geschlossen |
USING THE DB2CFIMP TO IMPORT CONNECTIVITY CONFIGURATION PARAMETE RS CAUSES AUTOMATIC VALUES TO BE RESET TO MINIMUM VALUES. | |
Produkt: | |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 | |
Problembeschreibung: | |
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-Zusammenfassung: | |
**************************************************************** * USERS AFFECTED: * * All users on Db2 V10.1 FixPack2 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: * * Upgrade to Db2 V10.1 FixPack 3 or above to fix the problem. * **************************************************************** | |
Local-Fix: | |
Avoid using "AUTOMATIC" as a value in such cases. or Change the dbm CFG manually after they are imported. | |
verfügbare FixPacks: | |
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows | |
Lösung | |
Problem first fixed in Db2 V10.1 FicPack 3. | |
Workaround | |
keiner bekannt / siehe Local-Fix | |
Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 25.07.2013 03.10.2013 03.10.2013 |
Problem behoben ab folgender Versionen (IBM BugInfos) | |
Problem behoben lt. FixList in der Version | |
10.1.0.3 | |
10.1.0.3 |