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 IC87160 Status: Closed

EXPORT TO PIPE MAY FAIL WITH ERROR SQL3001C

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
Starting with DB2 version 10.1., export to named pipe fails with 
error: 
 
SQL3104N  The Export utility is beginning to export data to file 
"/tmp/fifo". 
SQL3001C  An I/O error (reason = "sqlofopn -2029060094") 
occurred while 
opening the output file. 
SQL3105N  The Export utility has finished exporting "0" rows. 
 
Steps to reproduce the error 
% mknod /tmp/f1 p 
% db2 connect to sample 
% cat </temp/f1 & db2 "export to /tmp/f1 of del select * from 
employee"
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL DB2 USERS ON AIX                                         * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Problem Description above.                               * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 version 10.1 Fix Pack 3.                      * 
****************************************************************
Local Fix:
N/A
available fix packs:
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

Solution
First fixed in DB2 version 10.1 Fix Pack 3.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
11.10.2012
23.10.2013
23.10.2013
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.1.0.3 FixList
10.1.0.3 FixList