Latest versionsfixlist
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
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IC68643 Status: Closed

A LOAD WITH CLIENT KEYWORD THAT IS INTERRUPTED MAY TRAP IF CONNECT-RESET IS
INVOKED AFTERWARD.

product:
DB2 FOR LUW / DB2FORLUW / 910 - DB2
Problem description:
This problem affects V9.1fixpak8, V9.1fixpak9. 
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'.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* Users using client load.                                     * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error description field for more information.            * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to Version 9.1 FixPack 10.                           * 
****************************************************************
Local Fix:
available fix packs:
DB2 Version 9.1 Fix Pack 10  for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 11  for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 12  for Linux, UNIX and Windows

Solution
Problem was first fixed in DB2 UDB Version 9.1 FixPack 10.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
13.05.2010
16.06.2011
16.06.2011
Problem solved at the following versions (IBM BugInfos)
9.1.FP10
Problem solved according to the fixlist(s) of the following version(s)
9.1.0.10 FixList
This site uses cookies to make it easier for us to provide you with our services. By using our site you agree to the use of cookies.