Import Errors

Attached is an error message received during an import.

Import
Connected to: Oracle8i Enterprise Edition Release 8.1.6.2.0 - Production
With the Partitioning option
JServer Release 8.1.6.2.0 - Production

Export file created by EXPORT:V08.01.06 via direct path

Warning: the objects were exported by TESTP, not by you

import done in US7ASCII character set and US7ASCII NCHAR character set
. importing TESTP's objects into DBPROD
. . importing table "E6T_CAMPAIGN_ASSGN" 12953452 rows imported
. . importing table "E6T_SCORE" 10594395 rows imported
. . importing table "E6T_SCORE_DETAIL"
IMP-00009: abnormal end of export file
IMP-00018: partial import of previous table completed: 2111725 rows imported
Import terminated successfully with warnings.
Import Completed successfully with status 127

I looked up the error messages, but I hate to go back to the developer with such a vague explanation. Is there a better explanation for this error?

Thanks for your help.

Did you try with more buffer size and did you export the dmp with option consistent=y.

Did you ftp this dump file to your machine? The abnormal end of export file sounds like you didn't get the whole export dump file.

Could this not result from running out of space on the destination drive where the import is being performed?

Hi,
The problem in the FTP, do not upload BINARY files in ASCII mode and everything will be O'k!
Best wishes!

Quote:

---

Originally posted by kgb
Hi,
The problem in the FTP, do not upload BINARY files in ASCII mode and everything will be O'k!
Best wishes!

---

If the dump would have been ftp-ed in ASCII mode, the import would never even started loading from it. This is evidently not a case of ASCII transport mistake!

I had the same problem "unexpected end-fo-file" on 8.1.5 the reason was in ASCII mode, import utility started loading from this dump but never finished without that error. You may check it. Dump file is a binary file not ascii.


If the dump would have been ftp-ed in ASCII mode, the import would never even started loading from it. This is evidently not a case of ASCII transport mistake! [/B][/QUOTE]

Quote:

---

Originally posted by kgb
I had the same problem "unexpected end-fo-file" on 8.1.5 the reason was in ASCII mode, import utility started loading from this dump but never finished without that error.

---

[/B][/QUOTE]
Well, it depends on what you mean by "...import utility started loading ...". If you specified an ASCII file as a export dump, import utitility could only connect to the database. Then it tried to read from the dump file, but as it was an unknown format of the file header (ASCCI instead of binary) it aborted immediately with "unexpected end-fo-file". It couldn't possibly started to load data into tables if it was an ASCII file, no way. That is what I mean by "could never started loading from it".

In pthornburg's case the log file shows that import actually loaded a couple of tables succesfuly and then aborted. So obviously the dmp was ftp-ed in binary mode, but there must have been some other problems with it.

Thanks for the help!