Today, when the view backs up two large tables in expdp mode to a mounted nfs disk, it encounters a ORA-27054: NFSfilesystemwherethefileiscr
Today, when the view backs up two large tables in expdp mode to a mounted nfs disk, it encounters a ORA-27054: NFS file system where the file is cr
Today, when the view backs up two large tables in expdp mode to a mounted nfs disk, it encounters a ORA-27054: NFS file system where the file is created or resides is not mounted with correct options.
I checked it online and found three solutions:
1. Patching: 5146667
2. Set parameters during mount: rw, bg, hard, nointr, rsize = 32768, wsize = 32768, tcp, vers = 3, timeo = 600, actimeo = 0
For example, mount-v nfs-o rw, bg, hard, rsize = 32768, wsize = 32768, vers = 3, nointr, timeo = 600, proto = tcp 192.168.10.49: /storage/rmanbak/home/Oracle/rmanbak
3. Execute SQL> Alter system set events '10298 trace name context forever, level 32' (SCOPE = SPFILE) in the database );
Note: The brackets indicate whether to write the changes to the spfile. If this keyword is added, the preceding settings will still be valid after restart.
I chose the third method. After execution, we can use the normal export. I tried the second method to re-mount the disk, but it was always unsuccessful. I don't know what the problem was. I won't say much here.
Related reading:
SPFILE error causing database startup failure (ORA-01565)
ORA-01172, ORA-01151 error handling
ORA-00600 [2662] troubleshooting
Troubleshooting for ORA-01078 and LRM-00109
Notes on ORA-00471 Processing Methods
ORA-00314, redolog corruption, or missing Handling Methods
Solution to ORA-00257 archive logs being too large to store