DB2 FOR LUW / DB2FORLUW / A10 - DB2

When doing LOAD from remote cursor (also known as "remote fetch" 
load), db2lueff process is spawned.  If the LOAD gets an error, 
db2lueff is killed by the main load agent. However, if the error 
occurs in very early phase, db2lueff may not be started at that 
time. In this case the application performing the LOAD will hang 
and cannot be forced. 
 
This can only occur in single-node (i.e. non-DPF) systems. 
 
Any errors that cause LOAD error very early, can potentially hit 
this timing hole issue.  If a LOAD fails in BUILD phase or 
DELETE phase, this problem cannot occur.

**************************************************************** 
* USERS AFFECTED:                                              * 
* Users using LOAD from remote cursor.                         * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 10.1 Fix Pack 4.                      * 
****************************************************************

Not issuing LOAD from remote cursor.

DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
 DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows
 

First fixed in DB2 Version 10.1 Fix Pack 4.

not known / see Local fix

forerunner  : APAR is sysrouted TO one or more of the following: IC98890 
follow-up : 

Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :

31.10.2013
07.07.2014
07.07.2014