|
Hi,
Have a
look at the ixf file being created by the export command. I have found
that this command (at least in UDB7.1 FP2) seems truncates the export file
when the file if greater than 3 - 4 GB. My work around was to export the
table to multiple files (e.g. PK between 1 and 3,000,000 ; PK between 3,00,001
and 6,000,000 ; etc)
Howard
Wright
Cape
Town, South Africa
-----Original Message-----
From: LeGrand Decius [mailto:[EMAIL PROTECTED]] Sent: 20 August 2001 03:39 To: [EMAIL PROTECTED] Subject: DB2EUG: Problem with Export ixf format I'm having problems with exporting in IXF
format. When I export a file in IXF format and then load it as a table
using the import command, the export numbers and the import numbers do not
match.
========================================================
I export 16,000,000 rows from a table
in IXF format.
========================================================
connect to proddb user db2admin;
EXPORT TO c:\data\test\test0817.ixf OF IXF MESSAGES c:\data\test\test\test0817.log SELECT RECNUM, MEMNUM, MEMNAME, LAST_UPD_DATE
FROM PRD.MEMBER where LAST_UPD_DATE > '1999-12-31'; disconnect current; ========================================================
After exporting, I create a new
table using the following in command center:
========================================================
connect to TESTDB user db2admin;
import from f:\data\update\tst\test.ixf of IXF commitcount 1000 create into TST.MEMBER
disconnect current;
When create table is complete, I notice 7,435,000
rows were read and 7,435,000 rows were loaded.
Has anyone experienced this problem? What am I
doing wrong?
I'm open to all suggestions..
Thank you in advance.
|
- DB2EUG: Problem with Export ixf format LeGrand Decius
- Re: DB2EUG: Problem with Export ixf format Arnoud W. Morsink
- Re: DB2EUG: Problem with Export ixf format John Lantz
- Re: DB2EUG: Problem with Export ixf format Milorad_Cerovac
- Wright Howard
