【故障处理】imp-00051,imp-00008
【故障处理】imp-00051,imp-00008
1.1 BLOG文档结构图
1.2 故障分析及解决过程
imp导入报错：
IMP-00051: Direct path exported dump file contains illegal column length
IMP-00008: unrecognized statement in the export file
IMP-00009: abnormal end of export file
[oracle@lhrdb ~]$ oerr imp 51
00051, 00000, "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.
由于使用了direct=y的方式导出，所以导入的时候报错。MOS上是针对分区表的某一个空的分区导入的时候会报该错，但是客户这边的表不是分区表，dmp文件太大，不能做具体原因分析。给出的解决方案为：针对报错的表单独导出，并采用parfile参数。
[ZFZHLHRDB1:oracle]:/oracle>more /tmp/scottfile.par
tables=scott.emp,scott.dept
exp \'/ AS SYSDBA\' file=/tmp/test_query_lhr_scott_01.dmp parfile=/tmp/scottfile.par log=/tmp/test_query_lhr_scott_01.log
参考的MOS文档：
Traditional Import (IMP) Raises Error IMP-51 Direct Path Exported Dump File Contains Illegal Column Length (文档 ID 1403865.1)
ALERT Direct Path Export (EXP) Corrupts The Dump If An Empty Table Partition Exists (文档 ID 1604983.1)
The traditional export utility is de-supported beginning with the version 11g and is no more maintained.
exp和imp从11g开始不再维护。
1.3 MOS
1.3.1 ALERT Direct Path Export (EXP) Corrupts The Dump If An Empty Table Partition Exists (文档 ID 1604983.1)
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.
***Checked for relevance on 31-Oct-2016***
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, '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 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
1.3.2 Traditional Import (IMP) Raises Error IMP-51 Direct Path Exported Dump File Contains Illegal Column Length (文档 ID 1403865.1)
In this Document
| Symptoms |
| Cause |
| Solution |
APPLIES TO:
Oracle Server - Enterprise Edition - Version 11.2.0.2 and later
Information in this document applies to any platform.
SYMPTOMS
An original import of an export dump file created from an 11.2.0.2 database with DIRECT=Y fails with:
IMP-00051: Direct path exported dump file contains illegal column length
CAUSE
The exact cause is undetermined in this case.
SOLUTION
Instead of using the traditional export/import, use the DataPump export/import as a workaround.
©著作权归作者所有：来自51CTO博客作者小麦苗DB宝的原创作品，如需转载，请注明出处，否则将追究法律责任
更多相关文章
- Android官方入门文档[1]创建一个Android项目
- Android读取Word文档
- [Android] ACTION_GET_CONTENT与ACTION_PICK的区别
- Android(安卓)DOC文档分析——Dialog
- Android(安卓)Fresco图片处理库用法API英文原文文档2-1（Facebook
- Android官方技术文档翻译—— Eclilpse项目迁移
- android解析xml文件的方式
- 【Android(安卓)Developers Training】 53. 打印HTML文档
- Android(安卓)Kernel Porting 的简单总结文档