This content has been marked as final. Show 11 replies
Thanks for the reply.
I have checked the status again and all the entries seems present as mentioned in metalink note:
# nfsstat -m
/backup_prod from /backup_prod:172.26.20.100
All: srtt=0 (0ms), dev=0 (0ms), cur=0 (0ms)
Still not able to export data into this directory:
Any other idea please.
I have tried the same and still getting errors:
Connected to: Oracle Database 11g Enterprise Edition Release 184.108.40.206.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
ORA-39001: invalid argument value
ORA-39000: bad dump file specification
ORA-31641: unable to create dump file "/backup_prod/etl_schama_export_01.dmp"
ORA-27054: NFS file system where the file is created or resides is not mounted with correct options
Additional information: 6
The interesting thing is that the logfile is being created successfully. the problem is with the dump files.
I have resolved the issue by performing two tasks:
1. put the entries in /etc/filesystems file
dev = /backup
vfs = nfs
nodename = lhrhdcedwproddb01
mount = true
options = rw,bg,hard,nointr,rsize=32768,wsize=32768,tcp,vers=3,timeo=600,actimeo=0
account = false
2. mount the filesystem with these options
mount -o rw,bg,hard,nointr,rsize=32768,wsize=32768,proto=tcp,vers=3,timeo=600 172.26.20.100:/backup /backup_prod
Now I am able to export data into this NFS mount point
Thanks to all your support.
You can Set the following event in the init.ora, to disable the mount point parameter checking: event="10298 trace name context forever, level 32".
I had the same issue before and i tried this and it worked for me.
10gR2 "database backup" to nfs mounted dir results in ORA-27054 NFS error
Hope this Helps.
Yes I have read the metalink note which is giving the alternative by setting the event. But the constraint is that it will require instance restart. Since I am on my production server so can't afford restart at this time.
That's why i go with other option and was succeeded in resolving the issue without restarting.