Category Archives: IMP Database Error Messages

IMP-00051: Direct path exported dump file contains illegal column length

oracle

IMP-00051: Direct path exported dump file contains illegal column length
Cause: An invalid column length was encountered while processing column pieces.”
Action: Check to make sure the export file is not corrupted, or else report this to Oracle Worldwide Support as an Import/Export internal bug and submit the export file.

Back to previous menu

IMP-00050: Dump file and log file cannot be identical

oracle

IMP-00050: Dump file and log file cannot be identical
Cause: Identical names were given to the dump file and log file.
Action: Specify different names for the dump file and log file and retry the operation.

Back to previous menu

IMP-00049: Unknown language specified in CHARSET

oracle

IMP-00049: Unknown language specified in CHARSET
Cause: An unknown language was listed in the CHARSET option.
Action: Use a known character set.

Back to previous menu

IMP-00048: mismatched file header

oracle

IMP-00048: mismatched file header
Cause: During verification of the 2nd or subsequent file in a multi-file export, Import found header fields in the file that did not match values in the first file.
Action: Check the names of the files created by Export and verify that you specified them correctly for the import operation.

Back to previous menu

IMP-00047: unexpected file sequence number; expected number but found number

oracle

IMP-00047: unexpected file sequence number; expected number but found number
Cause: The header in the export file contains a sequence number that is used to track the order in which multiple export files are written. The first export file is assigned sequence number one, the second file is assigned sequence number two and so on. This message is displayed when a number other than the expected sequence number is found in the file header
Action: Execute the import command again, but specify the files in the order in which Export wrote them.

Back to previous menu

IMP-00046: using FILESIZE value from export file of string

oracle

IMP-00046: using FILESIZE value from export file of string
Cause: Either you did not specify the FILESIZE parameter in your IMPORT command, or you specified FILESIZE=0 and the export file was created with a non-zero value for FILESIZE. Import will use the value specified in the export file.
Action: None required.

Back to previous menu

IMP-00045: using VOLSIZE value from export file of string

oracle

IMP-00045: using VOLSIZE value from export file of string
Cause: Either you did not specify the VOLSIZE parameter in your IMPORT command, or you specified VOLSIZE=0 and the export was created with a non-zero value for VOLSIZE. Import will use the value specified in the export file.
Action: None required.

Back to previous menu

IMP-00044: unable to allocate enough memory for statement

oracle

IMP-00044: unable to allocate enough memory for statement
Cause: Import was unable to allocate sufficient memory to read in the specified statement and execute it.
Action: Increase the allocation for database buffers, restart the instance, and reexecute the Import command.

Back to previous menu

IMP-00043: export file character set inconsistent

oracle

IMP-00043: export file character set inconsistent
Cause: The character set of the export file and the environment character set (or the character set specified with the CHARSET keyword) are inconsistent. One character set is ASCII-based while the other is EBCDIC based.
Action: Specify the correct character set with the CHARSET keyword.

Back to previous menu

IMP-00042: CHARSET used, but the export file has specific character set

oracle

IMP-00042: CHARSET used, but the export file has specific character set
Cause: The user requested that a specific character set be used to process an export file that has a specific embedded character set ID. The ID in the export file is accurate and should be used.
Action: Remove the CHARSET keyword from the command line.

Back to previous menu