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 IT08562 Status: Geschlossen

WHEN MANY LOAD REMOTE FETCH OPERATIONS RUN AGAINST DIFFERENT TABLES
CONCURRENTLY, ONE OR MORE OF THEM MIGHT RARELY HANG.

Produkt:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problembeschreibung:
You may see the following error message in db2diag.log when the 
hanging problem occurs: 
 
2015-04-03-06.14.15.021000-240 I393824F734          LEVEL: Error 
PID     : 3472                 TID : 4524           PROC : 
db2syscs.exe 
INSTANCE: DB2                  NODE : 000           DB   : 
SAMPLE 
APPHDL  : 0-273                APPID: *LOCAL.DB2CE.150403100851 
AUTHID  : DB2                  HOSTNAME: sample 
EDUID   : 4524                 EDUNAME: db2agent (SAMPLE) 
FUNCTION: DB2 UDB, database utilities, 
sqluWaitForUserExitIfExists, probe:2967 
MESSAGE : ZRC=0x870F00B9=-2029059911=SQLO_SEM_TIMEOUT 
          "Return code from sqlowait when time out value has 
been reached" 
DATA #1 : LOADID, PD_TYPE_LOADID, 47 bytes 
LOADID: 4524.2015-04-03-06.14.01.715000.0 (4;4) 
DATA #2 : File name, 17 bytes 
sqlusUserExitSA.C 
 
2015-04-03-06.14.15.021000-240 I394560F599          LEVEL: Error 
PID     : 3472                 TID : 4524           PROC : 
db2syscs.exe 
INSTANCE: DB2                  NODE : 000           DB   : 
SAMPLE 
APPHDL  : 0-273                APPID: *LOCAL.DB2CE.150403100851 
AUTHID  : DB2                  HOSTNAME: sample 
EDUID   : 4524                 EDUNAME: db2agent (SAMPLE) 
FUNCTION: DB2 UDB, database utilities, sqluReportErrToDiag, 
probe:0 
DATA #1 : String, 119 bytes 
LOADID: 4524.2015-04-03-06.14.01.715000.0 (4;4) 
 , -2029059911, 0000000000000000, Detected in file:sqluvld.C, 
Line:6663 
 
2015-04-03-06.14.15.021000-240 I395161F1063         LEVEL: Error 
PID     : 3472                 TID : 4524           PROC : 
db2syscs.exe 
INSTANCE: DB2                  NODE : 000           DB   : 
SAMPLE 
APPHDL  : 0-273                APPID: *LOCAL.DB2CE.150403100851 
AUTHID  : DB2                  HOSTNAME: sample 
EDUID   : 4524                 EDUNAME: db2agent (SAMPLE) 
FUNCTION: DB2 UDB, database utilities, sqlulMRResponse, 
probe:6668 
MESSAGE : ZRC=0x8015006D=-2146107283=SQLU_CA_BUILT 
          "SQLCA has already been built" 
DATA #1 : LOADID, PD_TYPE_LOADID, 47 bytes 
LOADID: 4524.2015-04-03-06.14.01.715000.0 (4;4) 
DATA #2 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes 
 sqlcaid : SQLCA     sqlcabc: 136   sqlcode: -3005   sqlerrml: 0 
 sqlerrmc: 
 sqlerrp : SQLUVLD 
 sqlerrd : (1) 0x8015006D      (2) 0x00000000      (3) 
0x00000000 
           (4) 0x00000000      (5) 0x00000000      (6) 
0x00000000 
 sqlwarn : (1)      (2)      (3)      (4)        (5)       (6) 
 
           (7)      (8)      (9)      (10)        (11) 
 sqlstate:
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* Users using load from remote cursor                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 10.5 Fix Pack 7.                      * 
****************************************************************
Local-Fix:
Interrupt the hanging Load and then re-run it if possible.
Lösung
First fixed in DB2 Version 10.5 Fix Pack 7.
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
27.04.2015
29.01.2016
29.01.2016
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version
10.5.0.7 FixList