DB2 FOR LUW / DB2FORLUW / 970 - DB2

This problem affects V9.7fixpak1, V9.7fixpak2. 
When a Load is invoked from a remotely connected client using 
the CLIENT option (also know as a 'remote client Load' or 
'remote Load'), if the Load is interrupted it will rollback and 
complete as expected.  However a subsequent connect-reset may 
cause a trap. 
 
The trap file will contain a signal #11 and a stack like this: 
<StackTrace> 
-------Frame------ 
sqluRemapReturnCode 
sqluvload 
call_sqluvload 
sqluLoadPartition 
sqlu_register_table_load 
sqluvtld_route_in 
sqluTermConnect 
sqleUCagentConnectReset 
 
In this case the connect-reset 'sqleUCagentConnectReset' is 
incorrectly invoking a Load-specific connect-reset callback 
function 'sqluTermConnect'.

**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* This problem affects V9.7fixpak1, V9.7fixpak2.When a Load is * 
* invoked from a remotely connected clientusingthe CLIENT      * 
* option (also know as a 'remote client Load' or'remote        * 
* Load'), if the Load is interrupted it will                   * 
* rollbackandcomplete as expected.  However a subsequent       * 
* connect-resetmaycause a trap.The trap file will contain a    * 
* signal #11 and a stack                                       * 
* likethis:<StackTrace>-------Frame------sqluRemapReturnCodesqlu 
* this case the connect-reset 'sqleUCagentConnectReset'        * 
* isincorrectly invoking a Load-specific connect-reset         * 
* callbackfunction 'sqluTermConnect'.                          * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to Version 9.7 FixPack 3 or later.                   * 
****************************************************************

Problem was first fixed in DB2 UDB Version 9.7 FixPack 3.

keiner bekannt / siehe Local-Fix

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

13.05.2010
15.11.2010
15.11.2010

9.7.FP3