In Oracle 11g r2 environment, imp-00051 and IMP-00008 errors are reported during IMP import.

The following error message is reported when the customer imports data from imp.

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

IMP-00008: unrecognized statement in the export file

For the cause and solution of this error, see the following official documents.

 

 

 

ALERT: Direct Path Export (EXP) Partition upts The Dump If An Empty Table Partition Exists (Document ID 1604983.1)

 

Modification time:

Type: ALERT

 

In this Document

 

Description

Occurrence

Symptoms

Workaround

History

References

 

Applies:

Oracle Database-Enterprise Edition-Version 11.2.0.1 and later

Information in this document applies to any platform.

DESCRIPTION

You have med a direct path export (table, schema or full) using the traditional export utility (EXP ). if the exported objects include an empty table partition, then the export dump is already upt and cannot be imported.

OCCURRENCE

Only exp versions> = 11.2.0.1 are affected. The traditional export utility is de-supported beginning with the version 11g and is no more maintained.

SYMPTOMS

During import you may see one of the following issues:

IMP-00009: abnormal end of export file Or: IMP-00051: Direct path exported dump file contains illegal column length IMP-00008: unrecognized statement in the export file Or: Import silently skips a part of the dump, tables are missing and later constraints cannot be created.

This is below demonstrated with a simple test:

Connect test Create table part001 ( Col001 number, Col002 varchar2 (100) ) Partition by range (col001) ( Partition p001 values less than (10 ), Partition p002 values less than (100 ), Partition p003 values less than (1000) );   Insert into part001 values (5, 'text 5 '); Insert into part001 values (500, 'text 500 '); Commit;

#> Exp test/password file = part001.dmp tables = part001 direct = y This will show: About to export specified tables via Direct Path... .. Exporting table PART001 .. Exporting partition P001 1 rows exported .. Exporting partition P002 0 rows exported .. Exporting partition P003 1 rows exported Export terminated successfully without warnings. But the import breaks with error: . Importing TEST's objects into TEST .. Importing partition "PART001": "P001" 1 rows imported .. Importing partition "PART001": "P002" IMP-00009: abnormal end of export file Import terminated successfully with warnings.

WORKAROUND

 

If you perform direct path exports using a version greater or equal 11.2.0.1 and you see the messages:

About to export specified tables via Direct Path...

... .. Exporting partition <partition_name> 0 rows exported ...

In the export output (or log file), then you obtain a previous upt dump. You can verify the dump with the commands:

#> Imp user/passw full = y Or: #> Imp user/passw full = y show = y

Which will show you one of the behaviors listed above.

 

To workaround this please use:

-Conventional path export (exp direct = n) Or: -Materialize the empty partitions before running direct path exports: Connect/as sysdba Exec dbms_space_admin.materialize_deferred_segments (schema_name => 'test', table_name => 'part001', partition_name => 'p002 '); Or: -DataPump export (expdp)

HISTORY

[03-DEC-2013]-Document created

REFERENCES

BUG: 13880226-import fail with imp-00051 and imp-00008

Detailed illustration of the entire process of VMware + Linux + Oracle 10G RAC

Install Oracle 11gR2 (x64) in CentOS 6.4)

Steps for installing Oracle 11gR2 in vmwarevm

Install Oracle 11g XE R2 In Debian

Steps for installing Oracle 11gR2 in vmwarevm