=>db2 import from filename.ixf of ixf messages tablename.txt insert into SCHEMA.TABNAME; Import using Load which is faster (doesn't check constraints) and NONRECOVERABLE doesn't log anything. =>db2 load from filename.ixf of ixf insert into SCHEMA.TABNAME nonrecoverable; Build a file to set integrity on all tables that are in set integrity pending state. Import of a PC/IXF file into a new table is specified by the CREATE or the REPLACE_CREATE keywords in the IMPORT command. If a PC/IXF column of an invalid data type is selected for import into a new table, the import utility terminates. The entire PC/IXF file is rejected, no table is created, and no data is imported.
'While importing ixf file I'm facing the below issue SQL3153N The T record in the PC/IXF file has name '/workarea2/extractdata/CLM2102tGRSJ803B.ixf', qualifier ', and source ' '. SQL3109N The utility is beginning to load data from file 'CLM2102tGRSJ803B.ixf'. SQL3088N The source column specified to be loaded into database column 'CLMNBR' is not compatible with the database column, but the database column is not nullable.
SQL3110N The utility has completed processing. '0' rows were read from the input file.'
![How To Import Ixf Files Into Db2 Commands How To Import Ixf Files Into Db2 Commands](/uploads/1/2/5/6/125618595/804362804.gif)
![How To Import Ixf Files Into Db2 Commands How To Import Ixf Files Into Db2 Commands](http://dev.toadfordb2.com/releasenotes/ToadDB2V401/RelNotesImages4.0/DB2DependenciesTab.png)
What is the data type of the column CLMNBR you are importing into? What is the data type of the source you are importing FROM, and can it be missing (null)? This error indicates a number of possibilities: 1) The target column is defined as numeric or date (usually one of these two) and the data you are trying to insert does not meet that criteria (either not a number or not a valid date, depending) 2) The target column can not be null, but there's no data for that column in a row of the input source. Also, please indicate what version of DB2 on what operating system. Doug Agnew DB2 LUW DBA.
Hi Tom, Agreed. The 'quick fix' to get past the error is simply to increase the size of the log file. (I suspect that the database parameters are mostly the installation defaults so tuning is probably in order.) Committing every 1,000 rows or so will let it run, too. But just increasing the size of the log files doesn't improve performance of this import. It simply lets it run to completion.
And an import/load of 15M rows shouldn't take very long, though it will be considerably faster if logging is disabled. Let's see if he's had a chance to try either of the suggestion above. I'm curious.:) Kent.