DB2 - Problembeschreibung
Problem IC97332 | Status: Geschlossen |
LOAD FROM REMOTE CURSOR (REMOTE FETCH LOAD) MAY HANG AFTER GETTING AN ERROR IN VERY EARLY PHASE | |
Produkt: | |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 | |
Problembeschreibung: | |
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-Zusammenfassung: | |
**************************************************************** * USERS AFFECTED: * * Users using LOAD from remote cursor. * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 Version 10.1 Fix Pack 4. * **************************************************************** | |
Local-Fix: | |
Not issuing LOAD from remote cursor. | |
verfügbare FixPacks: | |
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows | |
Lösung | |
First fixed in DB2 Version 10.1 Fix Pack 4. | |
Workaround | |
keiner bekannt / siehe Local-Fix | |
Bug-Verfolgung | |
Vorgänger : APAR is sysrouted TO one or more of the following: IC98890 Nachfolger : | |
Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 31.10.2013 07.07.2014 07.07.2014 |
Problem behoben ab folgender Versionen (IBM BugInfos) | |
Problem behoben lt. FixList in der Version | |
10.1.0.4 |