DB2 FOR LUW / DB2FORLUW / 970 - DB2

LOAD operations with COPY YES option may timeout and fail, when 
there is no data to write to the LOAD COPY image for a 
120-second period.  This could happen if (for example): 
-- all the rows processed within 120 seconds are being rejected, 
or 
-- load's build phase (which does not write to LOAD COPY image) 
lasts longer than 120 seconds 
 
db2diag.log will have below entry for the LOAD 
 
----- 
2010-07-11-11.11.111.123456+123 E60128A423         LEVEL: Severe 
PID     : 181060               TID  : 20391       PROC : db2sysc 
0 
INSTANCE: db2inst1             NODE : 000 
EDUID   : 20391                EDUNAME: db2lmw0 0 
FUNCTION: DB2 UDB, database utilities, sqluMCContinueBackup, 
probe:830 
MESSAGE : ZRC=0x870F00B9=-2029059911=SQLO_SEM_TIMEOUT 
            "Return code from sqlowait when time out value has 
been reached" 
-----

**************************************************************** 
* USERS AFFECTED:                                              * 
* DB2 Version 9.7 FIX PACK 2, 3, 3a and 4                      * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error description field for more information.            * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 9.7 FixPack 5.                        * 
****************************************************************

a) Use COPY NO or NONRECOVERABLE, instead of COPY YES load 
option 
b) Reduce the invalid data of load, if failure occurs during 
load phase 
c) Use INDEXING MODE DEFERRED if possible, if failure occurs 
during build phase

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 8 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows
 

Problem was first fixed in DB2 Version 9.7 Fix Pack 5.

not known / see Local fix

forerunner  : APAR is sysrouted TO one or more of the following: IC73046 IC77930 
follow-up : 

Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :

22.07.2010
03.01.2012
08.03.2012

9.7.FP4,
9.7.FP5