DB2 FOR LUW / DB2FORLUW / 970 - DB2

When running db2_all in parallel mode (i.e. ';' option), db2_all 
sends the user's command to the target partitions, and spawns 
waiter processes in the partition where the command was run from 
(i.e. sender partition).  After the target partitions completes 
the user's command, they send a remote shell command back to the 
sender partition to inform that the command completed. 
 
Prior to the fix for this APAR, should this remote shell command 
fails for any reason, the sender partition exhibits a hang 
symptom, as it thinks that the user's command has not completed 
in the target partitions, when in fact it has. 
 
This is caused due to the lack of error handling of the failed 
remote shell command.  This APAR addresses the error handling. 
 
The cause of the remote shell command failure varies, but a 
common known cause is the excessive number of remote shell 
running at the same time.  For example, starting too many ssh at 
the same time may cause some of them to fail with the following 
error. 
 
ssh_exchange_identification: Connection closed by remote host 
 
Running too many rsh at the same time can fail with the 
following errors. 
 
socket: protocol failure in circuit setup. 
socket: All ports in use 
 
These types of capacity related failures may happen in a very 
large DPF environment.  e.g. several hundred partitions.

**************************************************************** 
* USERS AFFECTED:                                              * 
* Very large DPF environment                                   * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* When running db2_all in parallel mode (i.e. ';' option),     * 
* db2_all sends the user's command to the target partitions,   * 
* and spawns waiter processes in the partition where the       * 
* command was run from (i.e. sender partition).  After the     * 
* target partitions completes the user's command, they send a  * 
* remote shell command back to the sender partition to inform  * 
* that the command completed.                                  * 
*                                                              * 
* Prior to the fix for this APAR, should this remote shell     * 
* command fails for any reason, the sender partition exhibits  * 
* a hang symptom, as it thinks that the user's command has not * 
* completed in the target partitions, when in fact it has.     * 
*                                                              * 
* This is caused due to the lack of error handling of the      * 
* failed remote shell command.  This APAR addresses the error  * 
* handling.                                                    * 
*                                                              * 
* The cause of the remote shell command failure varies, but a  * 
* common known cause is the excessive number of remote shell   * 
* running at the same time.  For example, starting too many    * 
* ssh at the same time may cause some of them to fail with the * 
* following error.                                             * 
*                                                              * 
* ssh_exchange_identification: Connection closed by remote     * 
* host                                                         * 
*                                                              * 
* Running too many rsh at the same time can fail with the      * 
* following errors.                                            * 
*                                                              * 
* socket: protocol failure in circuit setup.                   * 
* socket: All ports in use                                     * 
*                                                              * 
* These types of capacity related failures may happen in a     * 
* very large DPF environment.  e.g. several hundred            * 
* partitions.                                                  * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 9.7 Fixpack 6.                                * 
****************************************************************

Running db2_all in serial mode (i.e. without ';') does not have 
this problem.

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
 

First fixed in DB2 9.7 Fixpack 6.

keiner bekannt / siehe Local-Fix

Vorgänger  : APAR is sysrouted TO one or more of the following: IC87826 
Nachfolger : 

Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:

10.02.2012
04.06.2012
04.06.2012

9.7.FP6