ORA-27046: file size is not a multiple of logical block size
今天用数据泵搭建的同步环境同步失败了，报错信息如下：
ORA-39002: invalid operation
ORA-31694: master table "" failed to load/unload
ORA-31640: unable to open dump file "" for read
ORA-19505: failed to identify file ""
ORA-27046: file size is not a multiple of logical block size
ORA-31694: master table "
ORA-31640: unable to open dump file "
ORA-19505: failed to identify file "
ORA-27046: file size is not a multiple of logical block size
由于目标库和源库的db_block_size不一样，我还担心是不是这个原因呢，后来查了一下metalink，不是这个原因。后来我仔细想了想，也不会跟db_block_size有关系，不然怎么会还支持跨平台的数据导入导出呢。
解决办法是把dmp重新ftp一下，发现大小果真和之前有问题的dmp大小不一样，所以看来还是网络上造成传输时的数据丢失了。
IMPDP Fails With ORA-39002, ORA-31694, ORA-31640, ORA-19505, ORA-27046 [ID 785473.1]
--------------------------------------------------------------------------------
修改时间 10-DEC-2010 类型 PROBLEM 状态 PUBLISHED
修改时间 10-DEC-2010 类型 PROBLEM 状态 PUBLISHED
In this Document
Symptoms
Cause
Solution
References
Symptoms
Cause
Solution
References
--------------------------------------------------------------------------------
Applies to:
Oracle Server - Enterprise Edition - Version: 10.1.0.2 and later [Release: 10.1 and later ]
Information in this document applies to any platform.
Oracle Server - Enterprise Edition - Version: 10.1.0.2 and later [Release: 10.1 and later ]
Information in this document applies to any platform.
Symptoms
IMPDP fails with the following errors:
IMPDP fails with the following errors:
ORA-39002: invalid operation
ORA-31694: master table "
ORA-31640: unable to open dump file "
ORA-19505: failed to identify file "
ORA-27046: file size is not a multiple of logical block size
Cause
The exported dump file is corrupt.
Solution
If the dump file came from a different system, then check if a binary transfer has taken place to transfer it to the current system. Also check the file size and if possible the checksum of the dump file.
If the dump file came from a different system, then check if a binary transfer has taken place to transfer it to the current system. Also check the file size and if possible the checksum of the dump file.
If the problem persists:
•recreate the dump file by restarting the EXPDP process and make sure EXPDP completes without errors
•verify that the directory pointed to by the DIRECTORY parameter can be read from and written to without any problems. This can e.g. be done by performing an EXPDP and IMPDP operation or by using the UTL_FILE PL/SQL routine to read from and write to a file in this directory
•verify that the directory pointed to by the DIRECTORY parameter can be read from and written to without any problems. This can e.g. be done by performing an EXPDP and IMPDP operation or by using the UTL_FILE PL/SQL routine to read from and write to a file in this directory
References
NOTE:206272.1 - New Method of Using UTL_FILE in Oracle9i 9.2
NOTE:266875.1 - Export/Import DataPump Parameter DIRECTORY - How to Specify a Directory
NOTE:206272.1 - New Method of Using UTL_FILE in Oracle9i 9.2
NOTE:266875.1 - Export/Import DataPump Parameter DIRECTORY - How to Specify a Directory
来自 “ ITPUB博客 ” ，链接：https://blog.itpub.net/29119536/viewspace-1318520/ ，如需转载，请注明出处，否则将追究法律责任。
请登录后发表评论
登录
全部评论
最新文章
- Oracle 数据库启动 startup和startup force的区别
- ORA-1092 : opitsk aborting process问题解决
- ORA-00600: internal error code, arguments: [kcratr_scan_lastbwr]错误处理
- Just For Today (Sibyl F. Partridge)
- centos linux成功安装hadoop
- shmall参数设置不当引起数据库启动时报out of memory报错
- java多线程实例
- Windows下SVN命令行工具使用详解（附加TortoiseSVN）
- MySQL错误1042-Can't get hostname for your address
- 公众号的秘密，知道一个biz就够了
