DB2 FOR LUW / DB2FORLUW / A10 - DB2

Starting with DB2 V9.7 FixPack 5 you might get sporadic SQL2001N 
errors when executing DB2 commands from a script. 
E.g. we have seen this with REORG statement being executed in a 
script. 
 
The behavior is caused by a late interrupt that was meant for 
previous SQL request, which can be picked up by the next SQL 
request. 
 
The error you will get is: 
 
 SQL2001N  The utility was interrupted.  The output data may be 
incomplete. 
 SQLSTATE=57014 
 
 
Following steps will reproduce the issue on DB2 V9.7 FP5: 
 
1. create database objects: 
 
 db2 "connect to sample" 
 db2 "create table db2v975.tt (c char(20), c1 char(20))" 
 db2 "create unique index i2 on db2v975.tt (c, c1)" 
 db2 "alter index i2 compress yes" 
 
2. run following script 
 
 --- 
 #!/bin/ksh 
 db2diag -A 
 
 i=0 
 RC=0; while [[ $RC -eq 0 ]] ; do 
 
 i=$(( $i + 1 )) 
 
 xx=$( db2 connect to sample ) 
 
 db2 "select cast(case when CLUSTERRATIO = -1 then CLUSTERFACTOR 
* 100 else clusterratio end as integer) from syscat.indexes 
where indname = 'I2' and tabname = 'TT' and tabschema = 
'DB2V975'" | read x dummy 
 
 db2 -a "reorg table db2v975.TT index I2" 
 RC=$? 
 
 echo "i:$i  x $x RC $RC\n\n\n" 
 done 
 --- 
 
In the above example the SELECT statement causes a broken pipe 
(SIGPIPE) signal. This happens because the "| read x dummy" 
expects only 1 line output, where in this case it will be more 
lines.

**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 10.1 Fix Pack 1                       * 
****************************************************************

Executing the CLP with 'db2 -x' will output only one line and 
prevent the issue in the example above.

DB2 Version 10.1 Fix Pack 1 for Linux, UNIX, and Windows
 DB2 Version 10.1 Fix Pack 2 for Linux, UNIX, and Windows
 DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows
 DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
 DB2 Version 10.1 Fix Pack 3a for Linux, UNIX, and Windows
 DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows
 

First fixed in DB2 Version 10.1 Fix Pack 1

not known / see Local fix

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

14.06.2012
02.11.2012
02.11.2012