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

DB2START AND DB2STOP ONLY HANDLES 200 NODES AT A TIME, STOPPING DB2 IS SLOW

Produkt:
DB2 FOR LUW / DB2FORLUW / 950 - DB2
Problembeschreibung:
In large enterprise data warehouse environments (>200 
partitions),  stopping the instance can take too long.  If ssh 
is being used as the remote command shell then db2stop could be 
faster by allowing all node stop commands to happen in parallel. 
In specific customer case, where the number of nodes is greater 
than 200, the nodes above 200 don't get the db2stop command in 
the first iteration. Therefore, they will continue to try to 
communicate to nodes 0 - 199. When those nodes stop, the nodes 
above 200 can't communicate and start node recovery. FCM 
communication failure and node recovery generate a lot of 
messages in the db2diag.log.  This means the entire stop process 
is delayed with all the communication failures and node 
recovery.
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* Users with ESE DPF environments where number of nodes is     * 
* greater than 200                                             * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* In large enterprise data warehouse environments (>200        * 
*                                                              * 
* partitions),  stopping the instance can take too long.       * 
* In specific customer case, where the number of nodes is      * 
* greater                                                      * 
* than 200, the nodes above 200 don't get the db2stop command  * 
* in                                                           * 
* the first iteration. Therefore, they will continue to try to * 
*                                                              * 
* communicate to nodes 0 - 199. When those nodes stop, the     * 
* nodes                                                        * 
* above 200 can't communicate and start node recovery. FCM     * 
*                                                              * 
* communication failure and node recovery generate a lot of    * 
*                                                              * 
* messages in the db2diag.log.  This means the entire stop     * 
* process                                                      * 
* is delayed with all the communication failures and node      * 
*                                                              * 
* recovery.                                                    * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 V9.5 FP6 or later.                            * 
****************************************************************
Local-Fix:
verfügbare FixPacks:
DB2 Version 9.5 Fix Pack 6a for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 8 for Linux, UNIX, and Windows
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
If ssh is being used as the remote command shell then db2stop 
should be 
faster by allowing all node stop commands to happen in parallel.
Workaround
keiner bekannt / siehe Local-Fix
Bug-Verfolgung
Vorgänger  : APAR is sysrouted TO one or more of the following: IC68360 IC68369 
Nachfolger : 
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
18.12.2009
25.05.2010
25.05.2010
Problem behoben ab folgender Versionen (IBM BugInfos)
9.5.FP6
Problem behoben lt. FixList in der Version