oracle 31640,【案例】Oracle报错ORA-39000 ORA-31640 ORA-27037的解决办法

【案例】Oracle报错ORA-39000 ORA-31640 ORA-27037的解决办法

时间:2016-10-25 21:27   来源:Oracle研究中心   作者:HTZ   点击:

次

天萃荷净

Oracle研究中心案例分析：运维DBA反映在巡检Oracle数据库时发现alert日志文件中出现ORA-39000 ORA-31640 ORA-27037报错，结合MOS官方文档总结解决办法。

How to Prevent ORA-39000 ORA-31640 ORA-27037 Errors When Performing DataPump Export/Import (文档 ID 784566.1)

In this Document

Goal

Solution

References

APPLIES TO:

Oracle Database – Enterprise Edition – Version 10.2.0.1 and later

Information in this document applies to any platform.

***Checked for relevance on 22-Oct-2013***

GOAL

This article documents a resolution for errors ORA-39000, ORA-31640 and ORA-27037 when performing DataPump export/import.

DataPump Import can fail with the following errors:

Import: Release 10.2.0.1.0 – Production on Friday, 30 January, 2009 15:10:33

Copyright (c) 2003, 2005, Oracle. All rights reserved.

;;;

Connected to: Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 – Production

With the Partitioning, OLAP and Data Mining options

ORA-39000: bad dump file specification

ORA-31640: unable to open dump file "/oracle/u01/app/oracle/oracle/product/10.2.0/db_2/admin/dpdump/expdat.dmp" for read

ORA-27037: unable to obtain file status

Linux Error: 2: No such file or directory

Additional information: 3

SOLUTION

The parameter DIRECTORY specifies the location to which the DataPump Export or Import is not properly created or having permission issues.

Drop and re-create a new oracle directory object and change the expdp/impdp command to point to the new directory to resolve this issue. You must have the DBA Privilege to create a Directory.

For example to create a directory object named expdp_dir located at /u01/backup/exports enter the