My Oracle Support Banner

Errors IMP-9 IMP-30 Or IMP-37 When Trying to Import (IMP) A Transferred Export Dump File (Doc ID 1012189.6)

Last updated on JANUARY 30, 2022

Applies to:

Oracle Database - Enterprise Edition - Version 7.3.3.0 and later
Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Information in this document applies to any platform.

Symptoms

An export is performed on machine A. The export file is transferred (via FTP, for example) to machine B in character (ASCII) mode rather than (BIN) binary mode. An import of the file is done on machine B.

One of the following errors can result:

IMP-9 abnormal end of export file
// *Cause: This is usually caused by an export file generated by an aborted
// export session.
// *Action: If the export file was generated by an aborted export session,
// retry the export followed by the import. Else, report this
// as a bug and submit the export file that causes this error.

IMP-30 failed to create file %s for write
// *Cause: Import was unable to create the specified file with write enabled
// *Action: Check the file name and file system for the source of the error

IMP-37 Character set marker unknown
// *Cause: export file is corrupted.
// *Action: Try to obtain an uncorrupted version of the export file.

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.