|
Problem IC98890
|
Status: Closed |
LOAD FROM REMOTE CURSOR (REMOTE FETCH LOAD) MAY HANG AFTER GETTING AN ERROR IN VERY EARLY PHASE |
| product: |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 |
| Problem description: |
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. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* Load from remote cursor. *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 Cancun Release 10.5.0.4 (also known as Fix *
* Pack 4) or higher. *
**************************************************************** |
| Local Fix: |
Not issuing LOAD from remote cursor. |
| available fix packs: |
DB2 Cancun Release 10.5.0.4 (also known as Fix Pack 4) for Linux, UNIX, and Windows
DB2 Version 10.5 Fix Pack 9 for Linux, UNIX, and Windows
|
| Solution |
Fixed in DB2 Cancun Release 10.5.0.4 (also known as Fix Pack 4) |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 22.01.2014
06.10.2014
06.10.2014 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.5.0.4
|
 |
