Home » RDBMS Server » Server Utilities » IMP-00009: abnormal end of export file
IMP-00009: abnormal end of export file [message #201718] Mon, 06 November 2006 08:35 Go to next message
TLegend33
Messages: 203
Registered: March 2005
Senior Member
I'm testing upgrade methods that coincide with a server migration. I have a client operating 8.0.5 on a Unix server. This client has a nightly export run and zipped. The zipped file is then pushed out to a Windows PC. The zipped file has a .Z extension. I ftp'd this zipped dump file to my office and then opened it with Winzip. When executing the import into an 8.1.7 database on Win2K, I receive the following errors in the import log:

IMP-00009: abnormal end of export file
IMP-00028: partial import of previous table rolled back: 288838 rows rolled back
Import terminated successfully with warnings.

From what I've found, I see that the error may be in how I ftp'd the file. I dragged and dropped it onto our ftp server from the client's PC. I'm not sure, but I believe the default ftp format is ascii. Since the dump file was zipped, does it matter whether or not I ftp using binary or ascii?

Thanks.

Report message to a moderator

Re: IMP-00009: abnormal end of export file [message #201720 is a reply to message #201718] Mon, 06 November 2006 09:01 Go to previous messageGo to next message
Mahesh Rajendran
Messages: 10708
Registered: March 2002
Location: oracleDocoVille
Senior Member
Account Moderator
>>does it matter whether or not I ftp using binary or ascii?
It does.
Always FTP with bin option for exported dumps or import from the unix machine itself and save an FTP operation.
And a .z file is unix compressed file. You have'nt mentioned what kind of *nix you are dealing with. So better to uncompress in unix machine and ftp the file to windows.

Report message to a moderator

Re: IMP-00009: abnormal end of export file [message #201721 is a reply to message #201718] Mon, 06 November 2006 09:04 Go to previous messageGo to next message
ebrian
Messages: 2794
Registered: April 2006
Senior Member
May also want to specify RECORDLENGTH=65535.

Report message to a moderator

Re: IMP-00009: abnormal end of export file [message #201747 is a reply to message #201720] Mon, 06 November 2006 10:11 Go to previous messageGo to next message
TLegend33
Messages: 203
Registered: March 2005
Senior Member
The client is operating AIX 4.3.3.
I believe there will be an issue uncompressing the dump file on the unix machine as the dump file is over 2GB is size. My unix is raw, but I read that unix has a 2GB file size limit. I unfortunatly cannot import from the unix machine itself because it is at a remote site...unless of course, I attach through their vpn, then execute the export over the network, which could take awhile. If I try to ftp the .Z file again using bin, should that make a difference?

Thanks.

Report message to a moderator

Re: IMP-00009: abnormal end of export file [message #201749 is a reply to message #201721] Mon, 06 November 2006 10:13 Go to previous messageGo to next message
TLegend33
Messages: 203
Registered: March 2005
Senior Member
Will specifying RECORDLENGTH=65535 only speed up the import? How will it affect the errors I'm receiving?

Thanks.

Report message to a moderator

Re: IMP-00009: abnormal end of export file [message #201757 is a reply to message #201749] Mon, 06 November 2006 10:39 Go to previous message
ebrian
Messages: 2794
Registered: April 2006
Senior Member
As Mahesh indicated, you first want to ensure you FTP in binary mode. If that still doesn't resolve your problem, then try setting RECORDLENGTH. This parameter will resolve any issues if there is a difference in the system's buffer size between the two systems.

Report message to a moderator

Previous Topic: 10g to 8i
Next Topic: export schedule problem
Goto Forum:
  

[ Syndicate this forum (XML) ] [ RSS ]

Current Time: Mon Jan 13 07:06:01 CST 2025
.:: Forum Home :: Blogger Home :: Wiki Home :: Contact :: Privacy ::.