home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Latest versionsfixlist
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
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IC64018 Status: Closed

LOAD UTILITY MAY STUCK IN DEADLOOP AND COULDN'T BE FORCED.

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
Load utility may stuck in deadloop and couldn't be forced. 
 
This happened because of the return code from sqluCrossFetchInto 
Buffer is overwritten by other functions, so that the loop in 
Load is not able to detect the error. 
 
One of the possible db2diag.log would looks like: 
YYYY-MM-DD-10.HH.MM.ss.nnnnnn         LEVEL:Severe 
PID     :<pid>                TID  : 1           PROC : 
db2agent (<db>) 0 
INSTANCE: <instance>           NODE : 000         DB   : <db> 
APPHDL  : <apphdl>             APPID: <appid> 
AUTHID  : <authid> 
FUNCTION: DB2 UDB, relation data serv, sqlrrbck, probe:25 
MESSAGE : SQLEU_STATE2_LOAD_ROLLBACK_PENDING state is set 
 
YYYY-MM-DD-HH.MM.ss.nnnnnn                        LEVEL: Error 
PID     : <pid>                TID  : 1           PROC : 
db2agent (<DB>) 0 
INSTANCE: <instance>           NODE : 000         DB   : <db> 
APPHDL  : <apphdl>             APPID: <appid> 
AUTHID  : <authid> 
FUNCTION: DB2 UDB, database utilities, DIAG_ERROR, probe:0 DATA 
#1 : String, 121 bytes 
LOADID: 442630.2009-02-28-01.40.11.507255.0 (5;4)  , -1224, 
ffffffff8012006d, Detected in file:sqlulxld_fetch.C, Line:982 
 
YYYY-MM-DD-HH.MM.ss.nnnnnn                        LEVEL: Error 
PID     : <pid>                TID  : 1           PROC : 
db2agent (<DB>) 0 
INSTANCE: <instance>           NODE : 000         DB   : <db> 
APPHDL  : <apphdl>             APPID: <appid> 
AUTHID  : <authid> 
FUNCTION: DB2 UDB, database utilities, DIAG_ERROR, probe:0 DATA 
#1 : String, 113 bytes 
LOADID: 442630.2009-02-28-01.40.11.507255.0 (5;4)  , 
-2145779603, 0, Detected in file:sqlulxld_fetch.C, Line:1653 
 
YYYY-MM-DD-HH.MM.ss.nnnnnn                        LEVEL: Error 
PID     : <pid>                TID  : 1           PROC : 
db2agent (<DB>) 0 
INSTANCE: <instance>           NODE : 000         DB   : <db> 
APPHDL  : <apphdl>             APPID: <appid> 
AUTHID  : <authid> 
FUNCTION: DB2 UDB, database utilities, DIAG_ERROR, probe:0 DATA 
#1 : String, 113 bytes 
LOADID: 442630.2009-02-28-01.40.11.507255.0 (5;4)  , 
-2145779603, 0, Detected in file:sqlulxld_fetch.C, Line:1752 
 
YYYY-MM-DD-HH.MM.ss.nnnnnn                        LEVEL: Error 
PID     : <pid>                TID  : 1           PROC : 
db2agent (<DB>) 0 
INSTANCE: <instance>           NODE : 000         DB   : <db> 
APPHDL  : <apphdl>             APPID: <appid> 
AUTHID  : <authid> 
FUNCTION: DB2 UDB, database utilities, DIAG_ERROR, probe:0 DATA 
#1 : String, 147 bytes 
LOADID: 442630.2009-02-28-01.40.11.507255.0 (5;4) 
sqluFetchCursor: called while sqlcode -ve , -1224, 0, Detected 
in file:sqlulxld_fetch.C, Line:941
Problem Summary:
USERS AFFECTED:  ALL 
 
PROBLEM DESCRIPTION:  see ERROR DESCRIPTION 
 
PROBLEM SUMMARY:  see ERROR DESCRIPTION
Local Fix:
Recycle the instance to clear the Load job
available fix packs:
DB2 Version 9.7 Fix Pack 1 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows

Solution
Problem first fixed in Version v9.7 Fix Pack 1
Workaround
see LOCAL FIX
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
22.10.2009
11.03.2010
11.03.2010
Problem solved at the following versions (IBM BugInfos)
9.7.FP1
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.1 FixList