|
Problem IC65196
|
Status: Closed |
DB2START AND DB2STOP ONLY HANDLES 200 NODES AT A TIME, STOPPING DB2 IS SLOW |
| product: |
DB2 FOR LUW / DB2FORLUW / 950 - DB2 |
| Problem description: |
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 Summary: |
****************************************************************
* 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: |
|
| available fix packs: |
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
|
| Solution |
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 |
not known / see Local fix |
| BUG-Tracking |
forerunner : APAR is sysrouted TO one or more of the following: IC68360 IC68369
follow-up : |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 18.12.2009
25.05.2010
25.05.2010 |
| Problem solved at the following versions (IBM BugInfos) |
9.5.FP6
|
| Problem solved according to the fixlist(s) of the following version(s) |
