|
Problem IC68360
|
Status: Geschlossen |
DB2START AND DB2STOP ONLY HANDLES 200 NODES AT A TIME, STOPPING DB2 IS SLOW |
| Produkt: |
DB2 FOR LUW / DB2FORLUW / 970 - 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 *
* isgreater than 200 *
****************************************************************
* PROBLEM DESCRIPTION: *
* In large enterprise data warehouse environments *
* (>200partitions), stopping the instance can take too *
* long.In specific customer case, where the number of nodes *
* isgreaterthan 200, the nodes above 200 don't get the db2stop *
* commandinthe first iteration. Therefore, they will continue *
* to try tocommunicate to nodes 0 - 199. When those nodes *
* stop, thenodesabove 200 can't communicate and start node *
* recovery. FCMcommunication failure and node recovery *
* generate a lot ofmessages in the db2diag.log. This means *
* the entire stopprocessis delayed with all the communication *
* failures and noderecovery. *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 9.7 FP3 or higher *
**************************************************************** |
| Local-Fix: |
|
| verfügbare FixPacks: |
DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 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 |
| Weitere Daten |
Datum - Problem gemeldet :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
| 05.05.2010
19.10.2010
19.10.2010 |
| Problem behoben ab folgender Versionen (IBM BugInfos) |
9.7.FP3
|
| Problem behoben lt. FixList in der Version |
| 9.7.0.3
|
 |
| 9.7.0.3
|
|
