DB2 FOR LUW / DB2FORLUW / 950 - DB2

The following error message can occur when working with 
named pipes: 
 
SQL3003C  An I/O error occurred while closing the output data 
file. 
 
Example: 
 
db2 connect to sample 
mkfifo np 
gzip -1 < np > EXPORT_FILE & 
db2 "export to np of ixf select * from org" 
 
The export works, but returns: 
 
SQL3104N  The Export utility is beginning to export data to file 
"np". 
SQL3003C  An I/O error occurred while closing the output data 
file. 
SQL3105N  The Export utility has finished exporting "8" rows. 
 
db2diag.log shows: 
 
2010-02-08-10.59.53.221907-300 E2174E471           LEVEL: Severe 
(OS) 
PID     : 15622                TID  : 182971811808 PROC : db2bp 
INSTANCE: dbxxxxxx             NODE : 000 
APPID   : *LOCAL.dbguest7.100208155917 
FUNCTION: DB2 UDB, oper system services, sqloclose, probe:10 
CALLED  : OS, -, fsync                            OSERR: EINVAL 
(22) 
DATA #1 : File handle, PD_TYPE_SQO_FILE_HDL, 8 bytes 
0x0000007FBFFFDB08 : 0400 0000 8000 0000 
........ 
 
The error is cosmetic and can be ignored.

USERS AFFECTED: All 
 
PROBLEM DESCRIPTION: 
 
see ERROR DESCRIPTION 
 
PROBLEM SUMMARY: 
 
see ERROR DESCRIPTION

n/a

DB2 Version 9.5 Fix Pack 6a for Linux, UNIX, and Windows
 DB2 Version 9.5 Fix Pack 7 for Linux, UNIX, and Windows
 DB2 Version 9.5 Fix Pack 8 for Linux, UNIX, and Windows
 DB2 Version 9.5 Fix Pack 9 for Linux, UNIX, and Windows
 DB2 Version 9.5 Fix Pack 10 for Linux, UNIX, and Windows
 

The complete fix for this problem first appears in DB2 UDB 
Version 9.5 FixPak 6.

keiner bekannt / siehe Local-Fix

Vorgänger  : APAR is sysrouted TO one or more of the following: IC66130 IC66277 
Nachfolger : 

Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:

09.02.2010
14.05.2010
14.05.2010

9.5.