| Latest versions | fixlist |
| 11.1.0.7 |
 |
| 10.5.0.9 |
|
| 10.1.0.6 |
|
| 9.8.0.5 |
|
| 9.7.0.11 |
|
| 9.5.0.10 |
|
| 9.1.0.12 |
|
| Have problems? - contact us. | |
| Register for free |
|
| Contact form |
|
DB2 - Problem description
| Problem IC84445 | Status: Closed |
IMPORT FROM A REMOTE CLIENT WHERE THE IMPORT FILE IS PROCESSED ON THE SAME CLIENT FAILS WHEN THE FILE HAS EMPTY STRINGS. | |
| product: | |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 | |
| Problem description: | |
When you try to import data from a remote client with the import file on the same client, it fails to read the input file if the file has empty strings. If you use the same import file on the DB2 server, it completes successfully. For example, Import from a remote client, with the input file locally on C:\temp. import from C:\temp\staffexp.txt of DEL insert into db2v97.stff; SQL3196N The input file was not found. If you use the same file on the server: When the location of the file on the server(/home/db2v97) is given, it correctly imports the data; import from /home/db2v97/staffexp.txt of DEL insert into db2v97.stff; Total number of rows read : 35 Total number of rows skipped : 0 Total number of rows inserted : 35 Total number of rows updated : 0 Total number of rows rejected : 0 Total number of rows committed : 35 DB250000I: The command completed successfully. The reason for error is the blank value in the delimited data to be imported. 20,"Pernal",20,"Sales",,+78171.25,+00612.45 <- 5th column value is blank 10,"Sanders",20,"Mgr ",7,+98357.50,, <- last column value is blank | |
| Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * DB2 on LUW V10 users. * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 V10 Fixpack 1. * **************************************************************** | |
| Local Fix: | |
Use input file on the DB2 server. | |
| available fix packs: | |
DB2 Version 10.1 Fix Pack 1 for Linux, UNIX, and Windows | |
| Solution | |
The issue is fixed in DB2 on LUW V10 Fixpack 1. | |
| Workaround | |
not known / see Local fix | |
| Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 14.06.2012 29.01.2013 29.01.2013 |
| Problem solved at the following versions (IBM BugInfos) | |
| Problem solved according to the fixlist(s) of the following version(s) | |
| 10.1.0.1 |
|
| 10.5.0.1 |
|