新手问题之-aix impdp nfs error

gtlions

一周的工作结束了，到了周末，在回顾这周的工作当中遇到的一些问题，本人刚刚转做运维，是在是新手，有很多问题还在学习中，希望各位大大指教：
问题1：aix5.3使用impdp nfs共享的问题
本来有个数据库迁移方案中，想使用expdp和impdp来转移数据的，源库的环境是rel5，oracle10g32bit，目标库是aix5.3，oracle10g64bit+rac。
在rel开启nfs共享后，在aix上也能够mount到共享的文件目录，在aix上mount的目录下oracle可以访问得到文件、创建文件，相关权限也给了，mount的文件夹是rel的oracle创建的，但是在aix上使用impdp的时候报错如下：
Import: Release 10.2.0.4.0 - 64bit Production on Tuesday, 08 November, 2011 16:43:16

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

Connected to: Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - 64bit Production
With the Partitioning, Real Application Clusters, OLAP, Data Mining
and Real Application Testing options
ORA-39001: invalid argument value
ORA-39000: bad dump file specification
ORA-31640: unable to open dump file "/oracle/impdpdir/exp99.dmp" for read
ORA-27054: NFS file system where the file is created or resides is not mounted with correct options
Additional information: 6

使用的mount命令如下：
由于一开始mount的时候报错：
vmount: Operation not permitted.
在查询到了ibm网站上的解决办法如下：
root执行nfso -p -o nfs_use_reserved_ports=1，然后执行mount：
第1次：mount 192.168.1.99:/opt/oradata/expdpdir /oracle/impdpdir
第2次：mount -o rw,bg,hard,rsize=32768,wsize=32768,vers=3,intr,timeo=600,proto=tcp 192.168.1.99:/opt/oradata/expdpdir /oracle/impdpdir
第3次：mount -o rw,bg,hard,nointr,rsize=32768,wsize=32768,vers=3,timeo=600,proto=tcp 192.168.1.99:/opt/oradata/expdpdir /oracle/impdpdir
这3种方式mount之后impdp均报上述错误，不知道何解。

[ 本帖最后由 gtlions 于 2011-11-12 11:20 编辑 ]

gtlions

ORA-39001: invalid argument value
这个错误后来加上转义已经解决了，但是后面的无法读取文件的问题依旧。

Maclean Liu(刘相兵

尝试用以下选项mount

1. cio,rw,bg,hard,nointr,rsize=32768,wsize=32768,proto=tcp,noac,vers=3,timeo=600
   
2. 
   
3. or
   
4. 
   
5. rw,bg,hard,nointr,rsize=32768,wsize=32768,proto=tcp, vers=3,timeo=600

复制代码

gtlions

谢谢，下周上班了再测试下。只是现在方案已经定下来了用exp imp，唉！

kevinlin.ora

试下
ORA-27054: NFS file system where the file is created or resides is not mounted with correct options [ID 781349.1]
          修改时间 05-OCT-2011     类型 PROBLEM     状态 PUBLISHED          

In this Document
  Symptoms
  Cause
  Solution
  References

Applies to:
Oracle Server - Enterprise Edition - Version: 10.1.0.2 to 11.1.0.7 - Release: 10.1 to 11.1
Information in this document applies to any platform.
***Checked for relevance on 21-Jan-2011***
Symptoms

You are transferring your database/installation to a NetApps NFS mount point.

The following error occurs on database startup:

ORA-01503: CREATE CONTROLFILE failed
ORA-01565: error in identifying file '/nfs_d04/oasisxx/data/oasis_system.dbf'
ORA-27054: NFS file system where the file is created or resides is not mounted with correct options

The current mount point is mounted as:

rw,bg,rsize=32768,wsize=32768,hard,vers=3,nointr,timeo=600,proto=tcp,suid 0 0
Cause

The correct mount point options are being used but they are not in the correct order per oracle docs on correctly mounting NFS mounts for oracle software.

The correct setting should be:

rw,bg,hard,rsize=32768,wsize=32768,vers=3,nointr,timeo=600,proto=tcp,suid

NOTE:  the location of the parameter 'hard'

NOTE:  As per Bug 11812928, the 'intr' & 'nointr' are deprecated in UEK kernels, as well as Oracle Linux 6. It is harmless to still include it, you will get a notice..

NFS: ignoring mount option: nointr.
Solution

Mount the NFS mount point with the recommended options in the exact order specified in oracle documentation.

For example:
# mount -F nfs -o rw,bg,hard,rsize=32768,wsize=32768,vers=3,forcedirectio,nointr,proto=tcp,suid host:/folder1/to1 /folder2/to2

Additional Resources

Community Discussions: Storage Management

Still have questions? Use the above community to search for similar discussions or start a new discussion on this subject.
References
NOTE:359515.1 - Mount Options for Oracle files when used with NAS devices

gtlions

好的 我等会试试 谢谢诶

gtlions

mount -F nfs -o rw,bg,hard,rsize=32768,wsize=32768,vers=3,forcedirectio,nointr,proto=tcp,suid host:/folder1/to1 /folder2/to2
测试了，不正确的参数
mount -F nfs -o rw,bg,hard,rsize=32768,wsize=32768,vers=3,forcedirectio,nointr,proto=tcp,suid 192.168.1.99:/opt/oradata/expdpdir /oracle/impdpdir
mount: Not a recognized flag: F
Usage: mount [-fipr] [-n Node] [-o Options] [-t Type] [-{v|V} Vfs]
        [-a | all | [[Node:]Device] [Directory]]

kevinlin.ora

ORA-39000 ORA-31640 And ORA-27054 Erorrs On Invoking DataPump Import [ID 739570.1]
          修改时间 14-OCT-2011     类型 PROBLEM     状态 PUBLISHED          

In this Document
  Symptoms
  Cause
  Solution
  References

Applies to:
Oracle Server - Enterprise Edition - Version: 10.2.0.3 and later   [Release: 10.2 and later ]
Information in this document applies to any platform.
*** Checked for relevance on 14-OCT-2011 ***
Symptoms
Invoking the DataPump import you may get the following errors:

ORA-39001: invalid argument value
ORA-39000: bad dump file specification
ORA-31640: unable to open dump file "<Dump file path>" for read
ORA-27054: NFS file system where the file is created or resides is not mounted with correct options
Additional information: 3

Cause

The problem is due to a configuration issue trying to write the dumpfile using a directory on a NFS mount point.
This issue has been discussed in unpublished Bug 4297851.

Solution

Here are the mount options that need to be used for NFS volumes on Linux are:

rsize=32k, wsize=32k, hard, actimeo=0

Along with the error there are warning messages printed in the alert log with the mount options to be used.Sometimes you may need to do the following to allow datapump to work with NFS mounted files:

Set the event in the init.ora, to disable the mount point parameter checking:

event="10298 trace name context forever, level 32"
         
Note that the event 10298 skips all mount checks.  Setting this event has to be done with care. Verify settings with your System Administrator to ensure no datafiles are corrupted.

gtlions

已经测试过多种组合，心灰意冷

laobu

462652.1CauseFrom IBM AIX documentation, it is clear that all mount point information is supposed to be present in the '/etc/filesystems' file located on the system. When mount information is not present in '/etc/filesystems' file it can lead to abnormalities.SolutionThe following steps helps in eliminating the above error during import:1. Ensure the filesystem is mounted with the required mount options ie, rsize=32k, wsize=32k, hard, actimeo=02. Set the following event in the init.ora, so that disable the mount point parameter checking:event="10298 trace name context forever, level 32"试没试过在filesystems中设置option参数,而不是在命令行

[ 本帖最后由 laobu 于 2011-11-19 01:00 编辑 ]

laobu

格式乱了搞不定:victory:
补充如下
1、试没试过在filesystems中设置option参数,而不是在命令行
2、还有event

gtlions

还没有，现在环境在跑着，要测试也不方便。