【故障處理】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 laterInformation 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:
Or:
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:
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:
. . 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 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:
...
. . 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:
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
- 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 laterInformation 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:
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.
About Me
...............................................................................................................................
● 本文作者:小麥苗,只專注於資料庫的技術,更注重技術的運用
● 本文在itpub(http://blog.itpub.net/26736162)、部落格園(http://www.cnblogs.com/lhrbest)和個人微信公眾號(xiaomaimiaolhr)上有同步更新
● 本文itpub地址:http://blog.itpub.net/26736162/viewspace-2132064/
● 本文部落格園地址:http://www.cnblogs.com/lhrbest/p/6261446.html
● 本文pdf版及小麥苗雲盤地址:http://blog.itpub.net/26736162/viewspace-1624453/
● QQ群:230161599 微信群:私聊
● 聯絡我請加QQ好友(642808185),註明新增緣由
● 於 2017-01-05 09:00 ~ 2017-01-05 19:00 在農行完成
● 文章內容來源於小麥苗的學習筆記,部分整理自網路,若有侵權或不當之處還請諒解
● 版權所有,歡迎分享本文,轉載請保留出處
...............................................................................................................................
拿起手機使用微信客戶端掃描下邊的左邊圖片來關注小麥苗的微信公眾號:xiaomaimiaolhr,掃描右邊的二維碼加入小麥苗的QQ群,學習最實用的資料庫技術。
來自 “ ITPUB部落格 ” ,連結:http://blog.itpub.net/26736162/viewspace-2132064/,如需轉載,請註明出處,否則將追究法律責任。
相關文章
- 【故障處理】一次RAC故障處理過程
- MongoDB故障處理MongoDB
- 故障分析 | Greenplum Segment 故障處理
- GPON網路故障如何處理?GPON網路故障處理流程
- 【故障處理】ORA-600:[13013],[5001]故障處理
- 【故障處理】ORA- 2730*,status 12故障分析與處理
- linux故障處理Linux
- ora-故障處理
- 線上故障處理手冊
- MySQL show processlist故障處理MySql
- 微服務的故障處理微服務
- teams登入故障處理
- Oracle更新Opatch故障處理Oracle
- 如何快速處理線上故障
- Mysql故障處理2則MySql
- dataguard故障處理一則
- AIX系統故障處理AI
- 【Linux】 nfs 故障處理LinuxNFS
- 【故障處理】CRS-1153錯誤處理
- 【故障處理】ORA-19809錯誤處理
- undo表空間故障處理
- flash_recovery_area故障處理
- 一次dataguard故障處理
- 分散式事務故障處理分散式
- 【故障處理】ORA-12162 錯誤的處理
- Oracle 10g RAC故障處理Oracle 10g
- 如何處理HTTP 503故障問題?HTTP
- 【故障處理】ORA-01555
- ORA-600 [2662]故障處理
- 處理網路連結故障技巧
- otedisk OCR 檔案管理故障處理
- ora-3137故障處理
- OGG 故障處理一例
- 一次TM ENQ故障處理ENQ
- Data guard archive GAP 故障處理案例Hive
- ora-04301故障處理
- goldengate故障處理一例Go
- HSG80故障處理過程