Shulou(Shulou.com)06/01 Report--

Today, the customer encountered the following error message when importing data from imp

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

IMP-00008: unrecognized statement in the export file

The reasons for this error and the solutions can be found in the following official documents

Welcome to join the ORACLE Super Group: 17115662 solve all kinds of ORACLE problems free of charge. BLOG will migrate to http://www.htz.pw in the future.

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

Modification time: 2013-12-19

Type: ALERT

In this Document

Description

Occurrence

Symptoms

Workaround

History

References

APPLIES TO:

Oracle Database-Enterprise Edition-Version 11.2.0.1 and later

Information in this document applies to any platform.

DESCRIPTION

You performed 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 corrupt 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,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 0 rows exported

...

In the export output (or log file), then you obtain a corrupt 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

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.