Neueste VersionenFixList
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
Haben Sie Probleme? - Kontaktieren Sie uns.
Kostenlos registrieren anmeldung-x26
Kontaktformular kontakt-x26

DB2 - Problembeschreibung

Problem IC94077 Status: Geschlossen

In XA ENVIRONMENT, DB2 TRAPS WHEN PROCESSING THE JOIN WITH CURSOR CALL

Produkt:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problembeschreibung:
DB2 traps when processing the join with cursor call and DB2 
continues to return DIA8039C XA PROTO error since the call is 
incorrect 
 
DIA8039C  error in db2diag appears as follows: 
 
2013-06-14-10.46.02.035009+120 I30198A631           LEVEL: Error 
PID     : 16580630             TID : 3343           PROC : 
db2sysc 0 
INSTANCE: db2inst             NODE : 000           DB   : 
TEST 
APPHDL  : 0-22                 APPID: 
172.10.10.100.46955.130614084545 
AUTHID  : PIC                  HOSTNAME: abcde 
EDUID   : 3343                 EDUNAME: db2agent (TEST) 0 
FUNCTION: DB2 UDB, data protection services, sqlpxreg, 
probe:4520 
RETCODE : ZRC=0x80100027=-2146435033=SQLP_PROTO 
          "Transaction manager function called in wrong 
context." 
          DIA8039C XA error with request type of "". XA protocol 
error. 
 
 
Similar stack shown below might appear in the trap file: 
 
-------Frame------ ------Function + Offset------ 
0x0900000000BF37D0 pthread_kill + 0xB0 
0x0900000000BF3048 _p_raise + 0x48 
0x090000000002BD2C raise + 0x4C 
0x0900000000088604 abort + 0xC4 
0x090000001B7E6664 sqloExitEDU + 0x330 
0x090000001AB93FD0 sqle_panic__Fv + 0x42C 
0x090000001C5A13EC sqloSpinLockReleaseConflict + 0xB4 
0x090000001CD3CBD4 
@101@sqloxult_track__FCP11sqlo_xlatchC14SQLO_LT_VALUES + 0x90 
0x090000001B85E190 
sqlpxrbk__FP8sqeAgentP15SQLXA_CALL_INFOP9SQLP_GXIDPP11sqlo_xlatc 
h + 0x116C 
0x090000001B85B9C4 
sqlrrbck_dps__FP8sqlrr_cbiN22P15SQLXA_CALL_INFOP9SQLP_GXIDb + 
0x1C4 
0x090000001B85914C sqlrrbck__FP8sqlrr_cbiN32P15SQLXA_CALL_INFO + 
0x124C 
0x090000001B857934 sqlrr_rollback__FP14db2UCinterface + 0x230 
0x090000001B8573E8 
sqljsRollbackBeforeConnectReset__FP14db2UCconHandle + 0x1E4 
0x090000001B9FD2F4 
@73@sqljsCleanup__FP8sqeAgentP14db2UCconHandle + 0x18C 
0x090000001B9F38EC 
@73@sqljsDrdaAsInnerDriver__FP18SQLCC_INITSTRUCT_Tb + 0x4CC 
0x090000001B9F2BEC sqljsDrdaAsDriver__FP18SQLCC_INITSTRUCT_T + 
0x21C 
0x090000001B7DD76C RunEDU__8sqeAgentFv + 0x594 
0x090000001B7D73CC EDUDriver__9sqzEDUObjFv + 0x13C 
0x090000001B7D7254 sqlzRunEDU__FPcUi + 0x10 
0x090000001B7EA000 sqloEDUEntry + 0x264 
</StackTrace>
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* Customers using XA transactions                              * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Apply DB2 V10.1 Fixpack 4                                    * 
****************************************************************
Local-Fix:
verfügbare FixPacks:
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows

Lösung
Problem is first fixed in DB2 UDB version 10.1 Fix pack 4
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
12.07.2013
16.06.2014
16.06.2014
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version
10.1.0.4 FixList