In addition to Weibo, there is also WeChat
Please pay attention
WeChat public account
Shulou
2025-04-03 Update From: SLTechnology News&Howtos shulou NAV: SLTechnology News&Howtos > Database >
Share
Shulou(Shulou.com)06/01 Report--
By querying metalink id: 387700.1
The document says that there are several possible problems:
A) The mount table (eg; / etc/mnttab) can be read to check the mount options
B) The NFS mount is mounted with the "hard" option
C) The mount options include rsize > = 32768 and wsize > = 32768
D) For RAC environments, where NFS disks are supported, the "noac" mount option is used.
The documentation indicates that it can be avoided by setting the event 10298 event, but setting event 10298 requires a database restart to take effect.
Check the configuration of NFS and find that there is no entry for mount nfs file system in / etc/filesystems of the client.
After adding the following entry, re-mount, solve.
# vi / etc/filesystems
/ exp:
Dev = / exp
Vfs = nfs
Nodename = 192.168.1.20
Mount = true
Options = rw,bg,hard,intr,proto=tcp,vers=3,rsize=65536,wsize=65536,timeo=600
Account = false
# umount / oraexp
# mount / oraexp
It is recommended that you encounter similar problems in the future, first check the / etc/filesystems file, this problem is caused by everyone likes to use the following way mount nfs.
LINUX uses the following methods:
Mount-o rw,bg,hard,intr,proto=tcp,vers=3,rsize=65536,wsize=65536,timeo=600 192.168.1.20:/exp / exp
Aix uses the following methods:
Mount-o hard,bg,proto=tcp,suid,rsize=32768,wsize=32768,noac 192.168.1.20:/backup / backup
Aix reference articles
ORA-19504 ORA-27054 Errors mounting NFS file system (Doc ID 370513.1)
/ / the relevant metalink documents are as follows:
ORA-19504 ORA-27054 Errors mounting NFS file system [ID 370513.1]
RMAN Backup Fails With RMAN-03009 ORA-19504 ORA-27054 NFS file system where the file is created or resides is not mounted with correct options [ID 1472448.1]
ORA-27054: NFS file system where the file is created or resides is not mounted with correct options [ID 781349.1]
/ / the process of setting another 10298 is as follows:
1) set the Event 10298 in the init file
Event= "10298 trace name context forever, level 32"
If you are using the spfile then the following can be done
SQL > alter system set event='10298 trace name context forever, level 32 scope= spfile
Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.
Views: 0
*The comments in the above article only represent the author's personal views and do not represent the views and positions of this website. If you have more insights, please feel free to contribute and share.
Continue with the installation of the previous hadoop.First, install zookooper1. Decompress zookoope
"Every 5-10 years, there's a rare product, a really special, very unusual product that's the most un
© 2024 shulou.com SLNews company. All rights reserved.