|
Problem IC68626
|
Status: Geschlossen |
A LOAD WITH CLIENT KEYWORD THAT IS INTERRUPTED MAY TRAP IF CONNECT-RESET IS INVOKED AFTERWARD. |
| Produkt: |
DB2 FOR LUW / DB2FORLUW / 950 - DB2 |
| Problembeschreibung: |
This problem affects v9.5fixpak5.
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-Zusammenfassung: |
****************************************************************
* USERS AFFECTED: *
* DB2 UDB Version 9.5 FixPack5 *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error description field for more information. *
****************************************************************
* RECOMMENDATION: *
* Upgrade to Version 9.5 FixPack 6. *
**************************************************************** |
| Local-Fix: |
|
| verfügbare FixPacks: |
DB2 Version 9.5 Fix Pack 6a for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 10 for Linux, UNIX, and Windows
|
| Lösung |
Problem was first fixed in DB2 UDB Version 9.5 FixPack 6. |
| Workaround |
keiner bekannt / siehe Local-Fix |
| Bug-Verfolgung |
Vorgänger : APAR is sysrouted TO one or more of the following: IC68643 IC68644 IC68725
Nachfolger : |
| Weitere Daten |
Datum - Problem gemeldet :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
| 13.05.2010
31.05.2010
31.05.2010 |
| Problem behoben ab folgender Versionen (IBM BugInfos) |
9.5.FP6
|
| Problem behoben lt. FixList in der Version |
