DB2 - Problem description
Problem IC66130 | Status: Closed |
SQL3003C WHEN WORKING WITH NAMED PIPES | |
product: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
Problem description: | |
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. | |
Problem Summary: | |
USERS AFFECTED: All PROBLEM DESCRIPTION: see ERROR DESCRIPTION PROBLEM SUMMARY: see ERROR DESCRIPTION | |
Local Fix: | |
n/a | |
available fix packs: | |
DB2 Version 9.7 Fix Pack 2 for Linux, UNIX, and Windows | |
Solution | |
The complete fix for this problem first appears in DB2 UDB Version 9.7 FixPak 2. | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 09.02.2010 18.05.2010 18.05.2010 |
Problem solved at the following versions (IBM BugInfos) | |
9.7. | |
Problem solved according to the fixlist(s) of the following version(s) | |
9.7.0.2 |